Hi Abhishek,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.11-rc8 next-20170428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Varadarajan-Narayanan/Add-minimal
Hi Abhishek,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.11-rc8 next-20170428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Varadarajan-Narayanan/Add-minimal
drivers/clk/qcom/gcc-ipq8074.c:1014:3-8: No need to set .owner here. The core
will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Abhishek Sahu
Signed-off-by: Fengguang Wu
drivers/clk/qcom/gcc-ipq8074.c:1014:3-8: No need to set .owner here. The core
will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Abhishek Sahu
Signed-off-by: Fengguang Wu
---
gcc-ipq8074.c |
On Fri, Apr 28, 2017 at 01:44:45PM -0700, Julius Werner wrote:
> > -8<
>
> That needs to go below the --- line, not above it.
>
>
> Really? git am --scissors seems to do the right thing for me this way...
Ah, never
On Fri, Apr 28, 2017 at 01:42:24PM -0700, Julius Werner wrote:
> Recent improvements in coreboot's memory console allow it to contain
> logs from more than one boot as long as the information persists in
> memory. Since trying to persist a memory buffer across reboots often
> doesn't quite work
On Fri, Apr 28, 2017 at 01:44:45PM -0700, Julius Werner wrote:
> > -8<
>
> That needs to go below the --- line, not above it.
>
>
> Really? git am --scissors seems to do the right thing for me this way...
Ah, never
On Fri, Apr 28, 2017 at 01:42:24PM -0700, Julius Werner wrote:
> Recent improvements in coreboot's memory console allow it to contain
> logs from more than one boot as long as the information persists in
> memory. Since trying to persist a memory buffer across reboots often
> doesn't quite work
On Sat, Apr 29, 2017 at 01:07:34AM +0200, Shiva Kerdel wrote:
> This patch fixes the following checkpatch.pl warning
> - EXPORT_SYMBOL(foo); should immediately follow its function/variable
>
> Signed-off-by: Shiva Kerdel
> ---
> drivers/staging/fbtft/fbtft-core.c | 25
On Sat, Apr 29, 2017 at 01:07:34AM +0200, Shiva Kerdel wrote:
> This patch fixes the following checkpatch.pl warning
> - EXPORT_SYMBOL(foo); should immediately follow its function/variable
>
> Signed-off-by: Shiva Kerdel
> ---
> drivers/staging/fbtft/fbtft-core.c | 25 +++--
On Fri, Apr 28, 2017 at 06:53:32PM -0700, Joe Perches wrote:
> On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote:
> > Use memdup_user() helper instead of open-coding to simplify the code.
>
> While I doubt this is a problem, this loses
> the multiplication overflow check for
> sizeof(*insns)
On Fri, Apr 28, 2017 at 06:53:32PM -0700, Joe Perches wrote:
> On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote:
> > Use memdup_user() helper instead of open-coding to simplify the code.
>
> While I doubt this is a problem, this loses
> the multiplication overflow check for
> sizeof(*insns)
On Fri, Apr 28, 2017 at 12:19:05PM +0900, AKASHI Takahiro wrote:
> > > > + ret = _request_firmware(_data, name, , device);
> > > > + if (ret && driver_data_param_optional(req_params))
> > > > + ret = driver_data_sync_opt_call_cb(req_params);
> > > > + else
> > > > +
On Fri, Apr 28, 2017 at 12:19:05PM +0900, AKASHI Takahiro wrote:
> > > > + ret = _request_firmware(_data, name, , device);
> > > > + if (ret && driver_data_param_optional(req_params))
> > > > + ret = driver_data_sync_opt_call_cb(req_params);
> > > > + else
> > > > +
Root in a non-initial user ns cannot be trusted to write a traditional
security.capability xattr. If it were allowed to do so, then any
unprivileged user on the host could map his own uid to root in a private
namespace, write the xattr, and execute the file with privilege on the
host.
However
Root in a non-initial user ns cannot be trusted to write a traditional
security.capability xattr. If it were allowed to do so, then any
unprivileged user on the host could map his own uid to root in a private
namespace, write the xattr, and execute the file with privilege on the
host.
However
Hi Mark/Pawel,
I think this patch series has been missed.
On 17-02-14 09:48 AM, Mark Rutland wrote:
On Fri, Feb 10, 2017 at 12:42:47PM -0800, Velibor Markovski wrote:
Add CCN-502 to the list of supported devices by ARM CCN PMU driver.
Signed-off-by: Velibor Markovski
Hi Mark/Pawel,
I think this patch series has been missed.
On 17-02-14 09:48 AM, Mark Rutland wrote:
On Fri, Feb 10, 2017 at 12:42:47PM -0800, Velibor Markovski wrote:
Add CCN-502 to the list of supported devices by ARM CCN PMU driver.
Signed-off-by: Velibor Markovski
Acked-by: Mark
Acked-by: Len Brown
On Sun, Apr 23, 2017 at 2:06 AM, David E. Box
wrote:
> From: "Box, David E"
>
> Gemini Lake uses the same C-states as Broxton and also uses the
> IRTL MSR's to determine maximum C-state latency.
>
>
Acked-by: Len Brown
On Sun, Apr 23, 2017 at 2:06 AM, David E. Box
wrote:
> From: "Box, David E"
>
> Gemini Lake uses the same C-states as Broxton and also uses the
> IRTL MSR's to determine maximum C-state latency.
>
> Signed-off-by: David E. Box
> ---
> drivers/idle/intel_idle.c | 2 ++
> 1
On Fri, Apr 28, 2017 at 09:58:47PM -0400, Dave Jones wrote:
> On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote:
> > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote:
> > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote:
> > > > currently running
On Fri, Apr 28, 2017 at 09:58:47PM -0400, Dave Jones wrote:
> On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote:
> > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote:
> > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote:
> > > > currently running
On Sat, Apr 29, 2017 at 10:38:48AM +0800, Ding Tianhong wrote:
> The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve
> ->msg_iter on error) will revert the iov buffer if copy to iter
> failed, but it didn't copy any datagram if the skb_checksum_complete
> error, so no need to
On Sat, Apr 29, 2017 at 10:38:48AM +0800, Ding Tianhong wrote:
> The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve
> ->msg_iter on error) will revert the iov buffer if copy to iter
> failed, but it didn't copy any datagram if the skb_checksum_complete
> error, so no need to
The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve
->msg_iter on error) will revert the iov buffer if copy to iter
failed, but it didn't copy any datagram if the skb_checksum_complete
error, so no need to revert any data at this place.
v2: Sabrina notice that return -EFAULT when
The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve
->msg_iter on error) will revert the iov buffer if copy to iter
failed, but it didn't copy any datagram if the skb_checksum_complete
error, so no need to revert any data at this place.
v2: Sabrina notice that return -EFAULT when
In general, if kthread_unpark() and kthread_parkme() execute together,
the kthread is supposed to be in an unparked state. This is because
kthread_unpark() either wakes up the thread if it already got parked,
or it cancels a prior kthread_park() call and hence renders the
kthread_parkme() moot.
In general, if kthread_unpark() and kthread_parkme() execute together,
the kthread is supposed to be in an unparked state. This is because
kthread_unpark() either wakes up the thread if it already got parked,
or it cancels a prior kthread_park() call and hence renders the
kthread_parkme() moot.
On 2017/4/28 21:16, Sabrina Dubroca wrote:
> 2017-04-28, 20:48:45 +0800, Ding Tianhong wrote:
>> The patch 3278682 (make skb_copy_datagram_msg() et.al. preserve
>> ->msg_iter on error) will revert the iov buffer if copy to iter
>> failed, but it looks no need to revert for csum error, so fix it.
Takashi Iwai writes:
> proc_create_mount_point() forgot to increase the parent's nlink, and
> it resulted in unbalanced hard link numbers, e.g. /proc/fs shows one
> less than expected.
Applied. Thanks.
>
> Fixes: eb6d38d5427b ("proc: Allow creating permanently empty
On 2017/4/28 21:16, Sabrina Dubroca wrote:
> 2017-04-28, 20:48:45 +0800, Ding Tianhong wrote:
>> The patch 3278682 (make skb_copy_datagram_msg() et.al. preserve
>> ->msg_iter on error) will revert the iov buffer if copy to iter
>> failed, but it looks no need to revert for csum error, so fix it.
Takashi Iwai writes:
> proc_create_mount_point() forgot to increase the parent's nlink, and
> it resulted in unbalanced hard link numbers, e.g. /proc/fs shows one
> less than expected.
Applied. Thanks.
>
> Fixes: eb6d38d5427b ("proc: Allow creating permanently empty directories...")
> Cc:
On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote:
> On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote:
> > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote:
> > > currently running v4.11-rc8-75-gf83246089ca0
> > >
> > > sunrpc bit is for the other unrelated problem I'm
On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote:
> On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote:
> > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote:
> > > currently running v4.11-rc8-75-gf83246089ca0
> > >
> > > sunrpc bit is for the other unrelated problem I'm
On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote:
> Use memdup_user() helper instead of open-coding to simplify the code.
While I doubt this is a problem, this loses
the multiplication overflow check for
sizeof(*insns) * insnlist.n_isns
> diff --git a/drivers/staging/comedi/comedi_fops.c
>
On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote:
> Use memdup_user() helper instead of open-coding to simplify the code.
While I doubt this is a problem, this loses
the multiplication overflow check for
sizeof(*insns) * insnlist.n_isns
> diff --git a/drivers/staging/comedi/comedi_fops.c
>
Use memdup_user_nul() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
arch/powerpc/platforms/pseries/reconfig.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/reconfig.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/block/skd_main.c | 16 +---
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c
index
Use memdup_user_nul() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
arch/powerpc/platforms/pseries/reconfig.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/reconfig.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/block/skd_main.c | 16 +---
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c
index 27833e4..6b3cdd2 100644
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/staging/comedi/comedi_fops.c | 22 +++---
1 file changed, 7 insertions(+), 15 deletions(-)
diff --git a/drivers/staging/comedi/comedi_fops.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
fs/pstore/platform.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c
index 43b3ca5..903e0fe
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
arch/powerpc/platforms/powernv/opal-prd.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal-prd.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/staging/comedi/comedi_fops.c | 22 +++---
1 file changed, 7 insertions(+), 15 deletions(-)
diff --git a/drivers/staging/comedi/comedi_fops.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
fs/pstore/platform.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c
index 43b3ca5..903e0fe 100644
---
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
arch/powerpc/platforms/powernv/opal-prd.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal-prd.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/block/floppy.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c
index 60d4c76..167426c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/block/floppy.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c
index 60d4c76..167426c 100644
---
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
arch/powerpc/kernel/nvram_64.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kernel/nvram_64.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
arch/powerpc/kernel/nvram_64.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kernel/nvram_64.c b/arch/powerpc/kernel/nvram_64.c
index
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/block/cciss.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
index
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/block/cciss.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
index cd37550..40ee715 100644
---
Drop useless kfree when memdup_user() failed, since we have already
called kfree in memdup_user().
Signed-off-by: Geliang Tang
---
drivers/firmware/efi/test/efi_test.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
Drop useless kfree when memdup_user() failed, since we have already
called kfree in memdup_user().
Signed-off-by: Geliang Tang
---
drivers/firmware/efi/test/efi_test.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/firmware/efi/test/efi_test.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/firmware/efi/test/efi_test.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/firmware/efi/test/efi_test.c
Use memdup_user() helper instead of open-coding to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/firmware/efi/test/efi_test.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/firmware/efi/test/efi_test.c
b/drivers/firmware/efi/test/efi_test.c
Use offset_in_page() macro instead of open-coding.
Signed-off-by: Geliang Tang
---
Changes in v2:
- include mm.h
---
drivers/tty/serial/atmel_serial.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/atmel_serial.c
Use offset_in_page() macro instead of open-coding.
Signed-off-by: Geliang Tang
---
Changes in v2:
- include mm.h
---
drivers/tty/serial/atmel_serial.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/atmel_serial.c
b/drivers/tty/serial/atmel_serial.c
Use setup_timer() instead of init_timer() to simplify the code.
Signed-off-by: Geliang Tang
---
Changes in v2:
- use setup_timer() in i40iw_terminate_start_timer().
---
drivers/infiniband/hw/i40iw/i40iw_cm.c| 5 ++---
drivers/infiniband/hw/i40iw/i40iw_utils.c | 10
Use setup_timer() instead of init_timer() to simplify the code.
Signed-off-by: Geliang Tang
---
Changes in v2:
- use setup_timer() in i40iw_terminate_start_timer().
---
drivers/infiniband/hw/i40iw/i40iw_cm.c| 5 ++---
drivers/infiniband/hw/i40iw/i40iw_utils.c | 10 --
2 files
Mr.Gutman
Thanks to the opinion.
I thought that PC applications can flexibly set button and axis settings.
However, there are many applications that can not be set.
To briefly explain the operation of the PSX pad,
1. When analog button is off, PSX gamepad send "digital" responses.
2. When
Mr.Gutman
Thanks to the opinion.
I thought that PC applications can flexibly set button and axis settings.
However, there are many applications that can not be set.
To briefly explain the operation of the PSX pad,
1. When analog button is off, PSX gamepad send "digital" responses.
2. When
Greg Kroah-Hartman writes:
> This patch doesn't apply to my tree at all, what tree/branch did you
> make it against?
>From the 'T:' line in MAINTAINER at STAGING SUBSYSTEM, I thought that I
should base changes on:
Greg Kroah-Hartman writes:
> This patch doesn't apply to my tree at all, what tree/branch did you
> make it against?
>From the 'T:' line in MAINTAINER at STAGING SUBSYSTEM, I thought that I
should base changes on:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
Since there
On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote:
> On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams
> wrote:
>> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>>> Badblocks are tracked at both region and device
On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote:
> On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams
> wrote:
>> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>>> Badblocks are tracked at both region and device levels.
>>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
This patch fixes the following checkpatch.pl warning
- EXPORT_SYMBOL(foo); should immediately follow its function/variable
Signed-off-by: Shiva Kerdel
---
drivers/staging/fbtft/fbtft-core.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff
This patch fixes the following checkpatch.pl warning
- EXPORT_SYMBOL(foo); should immediately follow its function/variable
Signed-off-by: Shiva Kerdel
---
drivers/staging/fbtft/fbtft-core.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git
On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote:
> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>> Badblocks are tracked at both region and device levels.
>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
>> and then
On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote:
> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
>> Badblocks are tracked at both region and device levels.
>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
>> and then badblocks_clear() to clear badblocks at the
On Fri, Apr 28, 2017 at 05:51:15PM -0400, Nicolas Pitre wrote:
> On Fri, 28 Apr 2017, Paul E. McKenney wrote:
>
> > Hello, Nicolas!
> >
> > Saw the TTY write up LWN and figured I should send this your way.
> > It should be worth about 2K compared to current -next, which gave
> > up the 2K
On Fri, Apr 28, 2017 at 05:51:15PM -0400, Nicolas Pitre wrote:
> On Fri, 28 Apr 2017, Paul E. McKenney wrote:
>
> > Hello, Nicolas!
> >
> > Saw the TTY write up LWN and figured I should send this your way.
> > It should be worth about 2K compared to current -next, which gave
> > up the 2K
On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
> Badblocks are tracked at both region and device levels.
> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
> and then badblocks_clear() to clear badblocks at the device level.
> However, it does not update
On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote:
> Badblocks are tracked at both region and device levels.
> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()
> and then badblocks_clear() to clear badblocks at the device level.
> However, it does not update badblocks at the
Some regulators have different settling times for voltage increases and
decreases. To avoid a time penalty on the faster transition extend the
settling time property to allow for different settings for upward and
downward transitions.
Signed-off-by: Matthias Kaehlcke
---
Some regulators have different settling times for voltage increases and
decreases. To avoid a time penalty on the faster transition extend the
settling time property to allow for different settings for upward and
downward transitions.
Signed-off-by: Matthias Kaehlcke
---
Dependencies (from
Inevitably when one actually needs to debug a DSM issue it's on a
distribution kernel that has CONFIG_ACPI_NFIT_DEBUG=n. The config symbol
was only there to avoid the compile error due to the missing fallback for
print_hex_dump_debug in the CONFIG_DYNAMIC_DEBUG=n case. That was fixed
with commit
Inevitably when one actually needs to debug a DSM issue it's on a
distribution kernel that has CONFIG_ACPI_NFIT_DEBUG=n. The config symbol
was only there to avoid the compile error due to the missing fallback for
print_hex_dump_debug in the CONFIG_DYNAMIC_DEBUG=n case. That was fixed
with commit
The following changes since commit e7590308d17e578e47f298cc3fec359108341cb6:
Merge tag 'sunxi-clk-fixes-for-4.11-2-bis' of
https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into clk-fixes
(2017-04-17 11:04:12 -0700)
are available in the git repository at:
The following changes since commit e7590308d17e578e47f298cc3fec359108341cb6:
Merge tag 'sunxi-clk-fixes-for-4.11-2-bis' of
https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into clk-fixes
(2017-04-17 11:04:12 -0700)
are available in the git repository at:
On Thu 27 Apr 01:22 PDT 2017, Johannes Berg wrote:
>
> > @@ -371,7 +371,7 @@ static void reap_tx_dxes(struct wcn36xx *wcn,
> > struct wcn36xx_dxe_ch *ch)
> > info = IEEE80211_SKB_CB(ctl->skb);
> > if (!(info->flags &
> > IEEE80211_TX_CTL_REQ_TX_STATUS)) {
On Thu 27 Apr 01:22 PDT 2017, Johannes Berg wrote:
>
> > @@ -371,7 +371,7 @@ static void reap_tx_dxes(struct wcn36xx *wcn,
> > struct wcn36xx_dxe_ch *ch)
> > info = IEEE80211_SKB_CB(ctl->skb);
> > if (!(info->flags &
> > IEEE80211_TX_CTL_REQ_TX_STATUS)) {
On 04/28/2017 10:53 AM, Peter Zijlstra wrote:
> On Fri, Apr 28, 2017 at 03:19:58PM +0200, Peter Zijlstra wrote:
>> Hi,
>>
>> These patches are based upon the hard work of Lauro. He put in the time and
>> effort to understand and debug the code.
>>
>> So while I didn't take many of his actual
On 04/28/2017 10:53 AM, Peter Zijlstra wrote:
> On Fri, Apr 28, 2017 at 03:19:58PM +0200, Peter Zijlstra wrote:
>> Hi,
>>
>> These patches are based upon the hard work of Lauro. He put in the time and
>> effort to understand and debug the code.
>>
>> So while I didn't take many of his actual
On Fri, Apr 28, 2017 at 4:04 PM, Joe Perches wrote:
> On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote:
>> ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e.
>> that the hexdump happens in the KERN_DEBUG case
>
> I think you are confusing KERN_DEBUG, a
On Fri, Apr 28, 2017 at 4:04 PM, Joe Perches wrote:
> On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote:
>> ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e.
>> that the hexdump happens in the KERN_DEBUG case
>
> I think you are confusing KERN_DEBUG, a logging level, with a
On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote:
> ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e.
> that the hexdump happens in the KERN_DEBUG case
I think you are confusing KERN_DEBUG, a logging level, with a
preprocessor #define of DEBUG.
> which I don't want. I
>
On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote:
> ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e.
> that the hexdump happens in the KERN_DEBUG case
I think you are confusing KERN_DEBUG, a logging level, with a
preprocessor #define of DEBUG.
> which I don't want. I
>
On 04/27/17 at 03:57pm, YASUAKI ISHIMATSU wrote:
> Hi Baoquan,
>
>
> On 04/26/2017 06:16 AM, Baoquan He wrote:
> > People reported kernel panic occurs during system boots up with mem boot
> > option.
> > After checking code, several problems are found about memmap= and mem= in
> > boot stage
>
Hi Joerg,
[auto build test ERROR on s390/features]
[also build test ERROR on v4.11-rc8 next-20170428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-s390-Fix-iommu-groups
On 04/27/17 at 03:57pm, YASUAKI ISHIMATSU wrote:
> Hi Baoquan,
>
>
> On 04/26/2017 06:16 AM, Baoquan He wrote:
> > People reported kernel panic occurs during system boots up with mem boot
> > option.
> > After checking code, several problems are found about memmap= and mem= in
> > boot stage
>
Hi Joerg,
[auto build test ERROR on s390/features]
[also build test ERROR on v4.11-rc8 next-20170428]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-s390-Fix-iommu-groups
On Fri, Apr 28, 2017 at 3:31 PM, Joe Perches wrote:
> On Fri, 2017-04-28 at 15:19 -0700, Dan Williams wrote:
>> On Fri, Apr 28, 2017 at 3:14 PM, Dan Williams
>> wrote:
>> > On Fri, Apr 28, 2017 at 3:07 PM, Joe Perches wrote:
>> > >
On Fri, Apr 28, 2017 at 3:31 PM, Joe Perches wrote:
> On Fri, 2017-04-28 at 15:19 -0700, Dan Williams wrote:
>> On Fri, Apr 28, 2017 at 3:14 PM, Dan Williams
>> wrote:
>> > On Fri, Apr 28, 2017 at 3:07 PM, Joe Perches wrote:
>> > > On Fri, 2017-04-28 at 14:52 -0700, Dan Williams wrote:
>> > >
Hi Sabrina,
On Fri, Apr 28, 2017 at 6:18 PM, Sabrina Dubroca wrote:
> One small thing here: since you're touching this comment, could you
> move it next to skb_to_sgvec, since that's the function it's supposed
> to document?
Done. I'll wait until next week to resubmit, to
Hi Sabrina,
On Fri, Apr 28, 2017 at 6:18 PM, Sabrina Dubroca wrote:
> One small thing here: since you're touching this comment, could you
> move it next to skb_to_sgvec, since that's the function it's supposed
> to document?
Done. I'll wait until next week to resubmit, to give some more time
For the Raspberry Pi's bindings, the power domain also implicitly
turns on the clock and deasserts reset, but for the new Cygnus port we
start representing the clock in the devicetree.
v2: Document the clock-names property, check for -ENOENT for no clock
in DT.
v3: Drop NULL checks around clk
For the Raspberry Pi's bindings, the power domain also implicitly
turns on the clock and deasserts reset, but for the new Cygnus port we
start representing the clock in the devicetree.
v2: Document the clock-names property, check for -ENOENT for no clock
in DT.
v3: Drop NULL checks around clk
The FBDEV initialization would throw an error in dmesg, when we just
want to silently not initialize fbdev on a V3D-only VC4 instance.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_kms.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
The FBDEV initialization would throw an error in dmesg, when we just
want to silently not initialize fbdev on a V3D-only VC4 instance.
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_kms.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
1 - 100 of 1460 matches
Mail list logo