Re: Linux 4.8-rc1 Cirrus QEMU crashes on boot.

- Original Message - > From: "Linus Torvalds" > To: "Eric W. Biederman" , "Boris Brezillon" > , "Daniel > Vetter" > Cc: "Linux Kernel Mailing List"

Re: Linux 4.8-rc1 Cirrus QEMU crashes on boot.

- Original Message - > From: "Linus Torvalds" > To: "Eric W. Biederman" , "Boris Brezillon" > , "Daniel > Vetter" > Cc: "Linux Kernel Mailing List" , "Dave Airlie" > , "David Airlie" > , "DRI" > Sent: Tuesday, 9 August, 2016 7:19:23 AM > Subject: Re: Linux 4.8-rc1 Cirrus QEMU

Re: [PATCH] net: make net namespace sysctls belong to container's owner

On Mon, Aug 8, 2016 at 2:08 PM, Eric W. Biederman wrote: > Dmitry Torokhov writes: > >> If net namespace is attached to a user namespace let's make container's >> root owner of sysctls affecting said network namespace instead of global >> root.

Re: [PATCH] net: make net namespace sysctls belong to container's owner

On Mon, Aug 8, 2016 at 2:08 PM, Eric W. Biederman wrote: > Dmitry Torokhov writes: > >> If net namespace is attached to a user namespace let's make container's >> root owner of sysctls affecting said network namespace instead of global >> root. >> >> This also allows us to clean up

Re: [RFC PATCH 2/3] Add generation of Module.ksymb file in streamline_config.pl

On Mon, Aug 08, 2016 at 10:32:46PM +0200, Julia Lawall wrote: > > > On Mon, 8 Aug 2016, Luis R. Rodriguez wrote: > > > On Sun, Jul 31, 2016 at 05:33:51PM +0200, Cristina Moraru wrote: > > > Add generation of ./scripts/mod/Module.ksymb file containing > > > associations of driver file names and

Re: [RFC PATCH 2/3] Add generation of Module.ksymb file in streamline_config.pl

On Mon, Aug 08, 2016 at 10:32:46PM +0200, Julia Lawall wrote: > > > On Mon, 8 Aug 2016, Luis R. Rodriguez wrote: > > > On Sun, Jul 31, 2016 at 05:33:51PM +0200, Cristina Moraru wrote: > > > Add generation of ./scripts/mod/Module.ksymb file containing > > > associations of driver file names and

Re: linux-next: build failure after merge of Linus' tree

Hi Doug, On Mon, 8 Aug 2016 11:37:33 -0400 Doug Ledford wrote: > > On 8/7/2016 9:58 PM, Stephen Rothwell wrote: > > > > With Linus' tree, today's linux-next build (powerpc allyesconfig) failed > > like this: > > > > drivers/infiniband/sw/built-in.o:(.opd+0x1698): multiple

Re: linux-next: build failure after merge of Linus' tree

Hi Doug, On Mon, 8 Aug 2016 11:37:33 -0400 Doug Ledford wrote: > > On 8/7/2016 9:58 PM, Stephen Rothwell wrote: > > > > With Linus' tree, today's linux-next build (powerpc allyesconfig) failed > > like this: > > > > drivers/infiniband/sw/built-in.o:(.opd+0x1698): multiple definition of > >

Re: [PATCH] staging: vt6655: power.c: Fix checkpatch warning

On Mon, 2016-08-08 at 17:35 -0400, Anson Jacob wrote: > Fix checkpatch.pl warning for trailing */ on a separate line > Remove '+' postfix and '-' prefix from the start and end of block comments Those /*+ uses should probably be converted to /** for kernel-doc > Signed-off-by: Anson Jacob

Re: [PATCH] staging: vt6655: power.c: Fix checkpatch warning

On Mon, 2016-08-08 at 17:35 -0400, Anson Jacob wrote: > Fix checkpatch.pl warning for trailing */ on a separate line > Remove '+' postfix and '-' prefix from the start and end of block comments Those /*+ uses should probably be converted to /** for kernel-doc > Signed-off-by: Anson Jacob > ---

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Mon, Aug 8, 2016 at 11:04 AM, Jon Hunter wrote: > I am wondering if it is related to ... > > [1.678160] apq8064-pinctrl 80.pinctrl: pin GPIO_16 already requested > by 1654.serial; cannot claim for 1658.i2c > [1.678207] apq8064-pinctrl 80.pinctrl:

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Mon, Aug 8, 2016 at 11:04 AM, Jon Hunter wrote: > I am wondering if it is related to ... > > [1.678160] apq8064-pinctrl 80.pinctrl: pin GPIO_16 already requested > by 1654.serial; cannot claim for 1658.i2c > [1.678207] apq8064-pinctrl 80.pinctrl: pin-16 (1658.i2c)

RE: [PATCH v2 1/3] ntb: Add asynchronous devices support to NTB-bus interface

From: Serge Semin > Hello Allen. > > Thanks for your careful review. Going through this mailing thread I hope > we'll come up > with solutions, which improve the driver code as well as extend the Linux > kernel support > of new devices like IDT PCIe-swtiches. > > Before getting to the inline

Re: [PATCH] device probe: add self triggered delayed work request

On 08/08/2016 01:44 PM, Frank Rowand wrote: On 07/29/16 22:39, Qing Huang wrote: In normal condition, the device probe requests kept in deferred queue would only be triggered for re-probing when another new device probe is finished successfully. This change will set up a delayed trigger work

RE: [PATCH v2 1/3] ntb: Add asynchronous devices support to NTB-bus interface

From: Serge Semin > Hello Allen. > > Thanks for your careful review. Going through this mailing thread I hope > we'll come up > with solutions, which improve the driver code as well as extend the Linux > kernel support > of new devices like IDT PCIe-swtiches. > > Before getting to the inline

Re: [PATCH] device probe: add self triggered delayed work request

On 08/08/2016 01:44 PM, Frank Rowand wrote: On 07/29/16 22:39, Qing Huang wrote: In normal condition, the device probe requests kept in deferred queue would only be triggered for re-probing when another new device probe is finished successfully. This change will set up a delayed trigger work

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Sat, Aug 6, 2016 at 1:45 AM, John Stultz wrote: > @@ -614,7 +615,11 @@ unsigned int irq_create_fwspec_mapping(struct > irq_fwspec *fwspec) > * it now and return the interrupt number. > */ > if

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Sat, Aug 6, 2016 at 1:45 AM, John Stultz wrote: > @@ -614,7 +615,11 @@ unsigned int irq_create_fwspec_mapping(struct > irq_fwspec *fwspec) > * it now and return the interrupt number. > */ > if (irq_get_trigger_type(virq) == IRQ_TYPE_NONE) { >

Re: [PATCH] keyrings: Allow searching the user session keyring

On Tue, Jun 14, 2016 at 2:46 AM, David Howells wrote: > Gwendal Grignou wrote: > >> Currently, if a session keyring exists, we are not searching in the >> user session or user keyrings. > > That is correct. New session keyrings are given a link to the

Re: [PATCH] keyrings: Allow searching the user session keyring

On Tue, Jun 14, 2016 at 2:46 AM, David Howells wrote: > Gwendal Grignou wrote: > >> Currently, if a session keyring exists, we are not searching in the >> user session or user keyrings. > > That is correct. New session keyrings are given a link to the user session if > created by pam_keyinit.

Re: Why do we need reset_control_get_optional() ?

On Monday, August 8, 2016 6:39:36 PM CEST Philipp Zabel wrote: > > Now I'm also confused about what we really need > > reset_control_get_optional() for, and which error codes the callers > > are supposed to check. > > > > This is the matrix I think you mean for _get_optional: > > > [...] > >

Re: Why do we need reset_control_get_optional() ?

On Monday, August 8, 2016 6:39:36 PM CEST Philipp Zabel wrote: > > Now I'm also confused about what we really need > > reset_control_get_optional() for, and which error codes the callers > > are supposed to check. > > > > This is the matrix I think you mean for _get_optional: > > > [...] > >

RE: [PATCH] ACPICA: Remove unnecessary '\n' in the end of ACPI_INFO output

I put that \n in there to break up the output from AcpiExec. This comes up every year or so, I think I'll give up -- without really seeing the harm in an extra \n. > -Original Message- > From: Zheng, Lv > Sent: Sunday, August 7, 2016 5:56 PM > To: Alexander Kuleshov

RE: [PATCH] ACPICA: Remove unnecessary '\n' in the end of ACPI_INFO output

I put that \n in there to break up the output from AcpiExec. This comes up every year or so, I think I'll give up -- without really seeing the harm in an extra \n. > -Original Message- > From: Zheng, Lv > Sent: Sunday, August 7, 2016 5:56 PM > To: Alexander Kuleshov ; Moore, Robert >

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Sat, Jul 30, 2016 at 10:07 AM, Thomas Gleixner wrote: > On Fri, 29 Jul 2016, John Stultz wrote: >> Hey Jon, >> So after rebasing my nexus7 patch stack onto pre-4.8-rc1 tree, I >> noticed the power/volume buttons stopped working. >> >> I did a manual rebased bisection and

Re: [Regression] "irqdomain: Don't set type when mapping an IRQ" breaks nexus7 gpio buttons

On Sat, Jul 30, 2016 at 10:07 AM, Thomas Gleixner wrote: > On Fri, 29 Jul 2016, John Stultz wrote: >> Hey Jon, >> So after rebasing my nexus7 patch stack onto pre-4.8-rc1 tree, I >> noticed the power/volume buttons stopped working. >> >> I did a manual rebased bisection and chased it down to

[PATCH] staging: vt6655: power.c: Fix checkpatch warning

Fix checkpatch.pl warning for trailing */ on a separate line Remove '+' postfix and '-' prefix from the start and end of block comments Signed-off-by: Anson Jacob --- drivers/staging/vt6655/power.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff

[PATCH] staging: vt6655: power.c: Fix checkpatch warning

Fix checkpatch.pl warning for trailing */ on a separate line Remove '+' postfix and '-' prefix from the start and end of block comments Signed-off-by: Anson Jacob --- drivers/staging/vt6655/power.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

Re: [PATCH] Revert "Revert "doc/sphinx: Enable keep_warnings""

On Mon, 8 Aug 2016 18:23:11 +0200 Daniel Vetter wrote: > Even with Markus fixes to the importer I still get warnigns from > sphinx which are entirely bogus :( > > /home/daniel/linux/src/Documentation/gpu/drm-kms.rst:13: WARNING: Could not > lex literal_block as "C".

Re: [PATCH] Revert "Revert "doc/sphinx: Enable keep_warnings""

On Mon, 8 Aug 2016 18:23:11 +0200 Daniel Vetter wrote: > Even with Markus fixes to the importer I still get warnigns from > sphinx which are entirely bogus :( > > /home/daniel/linux/src/Documentation/gpu/drm-kms.rst:13: WARNING: Could not > lex literal_block as "C". Highlighting skipped. >

[PATCH] staging: vt6655: device_main.c: Fix checkpatch warning

Fix warning by checkpatch.pl Add * for block comments on subsequent lines Signed-off-by: Anson Jacob --- drivers/staging/vt6655/device_main.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/vt6655/device_main.c

[PATCH] staging: vt6655: device_main.c: Fix checkpatch warning

Fix warning by checkpatch.pl Add * for block comments on subsequent lines Signed-off-by: Anson Jacob --- drivers/staging/vt6655/device_main.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/vt6655/device_main.c b/drivers/staging/vt6655/device_main.c

Re: [PATCH] exynos-drm: Fix unsupported GEM memory type error message to be clear

On 08/08/2016 10:56 AM, Krzysztof Kozlowski wrote: > On Fri, Aug 05, 2016 at 07:50:06PM -0600, Shuah Khan wrote: >> Fix unsupported GEM memory type error message to include the memory type >> information. >> >> Signed-off-by: Shuah Khan >> --- >>

Re: [PATCH] exynos-drm: Fix unsupported GEM memory type error message to be clear

On 08/08/2016 10:56 AM, Krzysztof Kozlowski wrote: > On Fri, Aug 05, 2016 at 07:50:06PM -0600, Shuah Khan wrote: >> Fix unsupported GEM memory type error message to include the memory type >> information. >> >> Signed-off-by: Shuah Khan >> --- >> drivers/gpu/drm/exynos/exynos_drm_fb.c | 4 ++--

Re: [PATCH v2 00/10] userns: sysctl limits for namespaces

I won't have any more time for this until I return from vacation at the end of the month but after a little bit of thought I think I have fixed all of the bugs (except arguably the return value). I have further tweaked these and made the limits per user. Because it occured to me that if the

Re: [PATCH v2 00/10] userns: sysctl limits for namespaces

I won't have any more time for this until I return from vacation at the end of the month but after a little bit of thought I think I have fixed all of the bugs (except arguably the return value). I have further tweaked these and made the limits per user. Because it occured to me that if the

Re: problem with 731c7d3, "main drm pull request for 4.8"

On 7 August 2016 at 07:59, Mike Marshall wrote: > Hello everyone... > > I was out of the office yesterday, so I came in today to do the bisect... Okay it appears cirrus doesn't set it's mode config functions until after it sets up modesetting, which causes this to fail.

Re: problem with 731c7d3, "main drm pull request for 4.8"

On 7 August 2016 at 07:59, Mike Marshall wrote: > Hello everyone... > > I was out of the office yesterday, so I came in today to do the bisect... Okay it appears cirrus doesn't set it's mode config functions until after it sets up modesetting, which causes this to fail. Probably need to audit

Клиентские базы bawupecoda-3...@courriel.fr.nf Skype: prodawez389 Подробности узнайте сейчас!

Соберем для Вас по интернет базу данных потенциальных клиентов для Вашего Бизнеса! В базе будут все контактные данные необходимые для массовой продажи Ваших товаров и услуг. По Вашему запросу пришлем пример и подробную информацию. Если интересно запросите подробности сейчас Email:

Клиентские базы bawupecoda-3...@courriel.fr.nf Skype: prodawez389 Подробности узнайте сейчас!

Соберем для Вас по интернет базу данных потенциальных клиентов для Вашего Бизнеса! В базе будут все контактные данные необходимые для массовой продажи Ваших товаров и услуг. По Вашему запросу пришлем пример и подробную информацию. Если интересно запросите подробности сейчас Email:

[BUG] 4.8-rc1: wlcore: NULL pointer dereference in wlcore_op_get_expected_throughput

Here is what I see in 4.8-rc1 on Pyra device after typing "poweroff". I hope someone knows what it means. BR and thanks, Nikolaus root@letux:~# poweroff Broadcast message from root@letux (pts/0) (Mon Aug 8 21:19:21 2016): The system is going down for system halt NOW! xinit: unexpected signal

[BUG] 4.8-rc1: wlcore: NULL pointer dereference in wlcore_op_get_expected_throughput

Here is what I see in 4.8-rc1 on Pyra device after typing "poweroff". I hope someone knows what it means. BR and thanks, Nikolaus root@letux:~# poweroff Broadcast message from root@letux (pts/0) (Mon Aug 8 21:19:21 2016): The system is going down for system halt NOW! xinit: unexpected signal

[PATCH v2 1/6] staging/android: remove doc from sw_sync

From: Gustavo Padovan SW_SYNC should never be used by other pieces of the kernel apart from sync_debug as it is only a Sync File Validation Framework, so hide any info to avoid confuse this with a standard kernel internal API. Signed-off-by: Gustavo Padovan

[PATCH v2 1/6] staging/android: remove doc from sw_sync

From: Gustavo Padovan SW_SYNC should never be used by other pieces of the kernel apart from sync_debug as it is only a Sync File Validation Framework, so hide any info to avoid confuse this with a standard kernel internal API. Signed-off-by: Gustavo Padovan ---

[PATCH v2 5/6] staging/android: add Doc for SW_SYNC ioctl interface

From: Gustavo Padovan This interface is hidden from kernel headers and it is intended for use only for testing. So testers would have to add the ioctl information internally. This is to prevent misuse of this feature. Signed-off-by: Gustavo Padovan

[PATCH v2 2/6] staging/android: do not let userspace trigger WARN_ON

From: Gustavo Padovan Closing the timeline without waiting all fences to signal is not a critical failure, it is just bad usage from userspace so avoid calling WARN_ON in this case. Signed-off-by: Gustavo Padovan ---

[PATCH v2 4/6] staging/android: prepare sw_sync files for de-staging

From: Gustavo Padovan remove file paths in the comments and add short description about each file. v2: remove file paths instead of just change them. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c| 2

[PATCH v2 5/6] staging/android: add Doc for SW_SYNC ioctl interface

From: Gustavo Padovan This interface is hidden from kernel headers and it is intended for use only for testing. So testers would have to add the ioctl information internally. This is to prevent misuse of this feature. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c | 31

[PATCH v2 2/6] staging/android: do not let userspace trigger WARN_ON

From: Gustavo Padovan Closing the timeline without waiting all fences to signal is not a critical failure, it is just bad usage from userspace so avoid calling WARN_ON in this case. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v2 4/6] staging/android: prepare sw_sync files for de-staging

From: Gustavo Padovan remove file paths in the comments and add short description about each file. v2: remove file paths instead of just change them. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c| 2 +- drivers/staging/android/sync_debug.c | 2 +-

[PATCH v2 3/6] staging/android: move trace/sync.h to sync_trace.h

From: Gustavo Padovan The common behaviour for trace headers is to have them in the same folder they are used, instead of creating a special trace/ directory. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c

[PATCH v2 3/6] staging/android: move trace/sync.h to sync_trace.h

From: Gustavo Padovan The common behaviour for trace headers is to have them in the same folder they are used, instead of creating a special trace/ directory. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c| 2 +- drivers/staging/android/sync_trace.h | 32

[PATCH v2 6/6] dma-buf/sw_sync: de-stage SW_SYNC

From: Gustavo Padovan SW_SYNC allows to run tests on the sync_file framework via debugfs on /sync/sw_sync Opening and closing the file triggers creation and release of a sync timeline. To create fences on this timeline the SW_SYNC_IOC_CREATE_FENCE ioctl should

[PATCH v2 6/6] dma-buf/sw_sync: de-stage SW_SYNC

From: Gustavo Padovan SW_SYNC allows to run tests on the sync_file framework via debugfs on /sync/sw_sync Opening and closing the file triggers creation and release of a sync timeline. To create fences on this timeline the SW_SYNC_IOC_CREATE_FENCE ioctl should be used. To increment the

[PATCH v2 0/6] de-stage SW_SYNC validation frawework

From: Gustavo Padovan Hi Greg, This is the last step in the Sync Framwork de-stage task. It de-stage the SW_SYNC validation framework and the sync_debug info debugfs file. The first 2 patches are clean up and improvements and the rest is preparation to de-stage

[PATCH v2 0/6] de-stage SW_SYNC validation frawework

From: Gustavo Padovan Hi Greg, This is the last step in the Sync Framwork de-stage task. It de-stage the SW_SYNC validation framework and the sync_debug info debugfs file. The first 2 patches are clean up and improvements and the rest is preparation to de-stage and then finally the actual

Re: [PATCH] net: make net namespace sysctls belong to container's owner

Dmitry Torokhov writes: > If net namespace is attached to a user namespace let's make container's > root owner of sysctls affecting said network namespace instead of global > root. > > This also allows us to clean up net_ctl_permissions() because we do not > need to

Re: [PATCH] net: make net namespace sysctls belong to container's owner

Dmitry Torokhov writes: > If net namespace is attached to a user namespace let's make container's > root owner of sysctls affecting said network namespace instead of global > root. > > This also allows us to clean up net_ctl_permissions() because we do not > need to fudge permissions anymore for

Re: [PATCH] mm: memcontrol: only mark charged pages with PageKmemcg

On Mon, Aug 8, 2016 at 1:03 PM, Vladimir Davydov wrote: > To distinguish non-slab pages charged to kmemcg we mark them PageKmemcg [..] Eric, can you confirm that this fixes your issue? Linus

Re: [PATCH] mm: memcontrol: only mark charged pages with PageKmemcg

On Mon, Aug 8, 2016 at 1:03 PM, Vladimir Davydov wrote: > To distinguish non-slab pages charged to kmemcg we mark them PageKmemcg [..] Eric, can you confirm that this fixes your issue? Linus

Re: Linux 4.8-rc1 Cirrus QEMU crashes on boot.

On Mon, Aug 8, 2016 at 1:24 PM, Eric W. Biederman wrote: > > Booting up v4.8-rc1 in qemu today I ran I ran into this beautiful oops. > > I am just about to head out the door on vacation until the end of the > month so hopefully I am tossing out enough information to the

Re: Linux 4.8-rc1 Cirrus QEMU crashes on boot.

On Mon, Aug 8, 2016 at 1:24 PM, Eric W. Biederman wrote: > > Booting up v4.8-rc1 in qemu today I ran I ran into this beautiful oops. > > I am just about to head out the door on vacation until the end of the > month so hopefully I am tossing out enough information to the right > people. > > I have

[PATCH] staging: vt6655: channel.c: Fix block comments usage warning by checkpatch.pl

This patch fixes the following checkpatch.pl warnings: WARNING: Block comments use * on subsequent lines + /* TX_PE will reserve 3 us for MAX2829 A mode only, + it is for better TX throughput */ WARNING: Block comments use a trailing */ on a separate line + it is for

[PATCH] staging: vt6655: channel.c: Fix block comments usage warning by checkpatch.pl

This patch fixes the following checkpatch.pl warnings: WARNING: Block comments use * on subsequent lines + /* TX_PE will reserve 3 us for MAX2829 A mode only, + it is for better TX throughput */ WARNING: Block comments use a trailing */ on a separate line + it is for

Re: [Regression] Bonding no longer support tun-interfaces

Report this to the correct mailing list please, networking discussion occurs on net...@vger.kernel.org, not linux-kernel or the stable list. Thanks.

Re: [Regression] Bonding no longer support tun-interfaces

Report this to the correct mailing list please, networking discussion occurs on net...@vger.kernel.org, not linux-kernel or the stable list. Thanks.

[Regression] Bonding no longer support tun-interfaces

This has been reported (and ignored) before: http://lkml.iu.edu/hypermail/linux/kernel/1407.2/03790.html https://bugzilla.kernel.org/show_bug.cgi?id=89161 Regression was introduced by: commit 00503b6f702e (refs/bisect/bad) Author: dingtianhong Date: Sat Jan 25

[Regression] Bonding no longer support tun-interfaces

This has been reported (and ignored) before: http://lkml.iu.edu/hypermail/linux/kernel/1407.2/03790.html https://bugzilla.kernel.org/show_bug.cgi?id=89161 Regression was introduced by: commit 00503b6f702e (refs/bisect/bad) Author: dingtianhong Date: Sat Jan 25 13:00:29 2014 +0800

Re: 4.7.0-rc7 ext4 error in dx_probe

On 2016-08-08 19:55, Darrick J. Wong wrote: > On Mon, Aug 08, 2016 at 12:08:18PM -0400, Theodore Ts'o wrote: >> On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote: >>> >>> I have one lingering concern -- is it a bug that two processes could be >>> computing the checksum of a buffer

Re: 4.7.0-rc7 ext4 error in dx_probe

On 2016-08-08 19:55, Darrick J. Wong wrote: > On Mon, Aug 08, 2016 at 12:08:18PM -0400, Theodore Ts'o wrote: >> On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote: >>> >>> I have one lingering concern -- is it a bug that two processes could be >>> computing the checksum of a buffer

Re: [PATCH v18 6/6] ARM: socfpga: fpga bridge driver support

Hi Alan, On Mon, Aug 8, 2016 at 12:18 PM, atull wrote: >> Please don't use module.h in drivers controlled by a bool >> Kconfig setting. >> >> THanks, >> Paul. >> > > Thanks for the feedback. Can you provide an example of what you > would consider to be proper usage

Re: [PATCH v18 6/6] ARM: socfpga: fpga bridge driver support

Hi Alan, On Mon, Aug 8, 2016 at 12:18 PM, atull wrote: >> Please don't use module.h in drivers controlled by a bool >> Kconfig setting. >> >> THanks, >> Paul. >> > > Thanks for the feedback. Can you provide an example of what you > would consider to be proper usage in the kernel? I think

Re: [lkp] [dm flakey] 99f3c90d0d: WARNING: CPU: 20 PID: 1027 at fs/btrfs/extent-tree.c:2973 btrfs_run_delayed_refs+0x2c5/0x2f0 [btrfs]

On 08/08/2016 02:27 PM, Linus Torvalds wrote: This report should probably have gone to the btrfs people, although it doesn't really look like a bug. It looks like it's just dm-flakey now returning more errors, and causing btrfs to complain more. Which seems entirely expected. Maybe the

Re: [lkp] [dm flakey] 99f3c90d0d: WARNING: CPU: 20 PID: 1027 at fs/btrfs/extent-tree.c:2973 btrfs_run_delayed_refs+0x2c5/0x2f0 [btrfs]

On 08/08/2016 02:27 PM, Linus Torvalds wrote: This report should probably have gone to the btrfs people, although it doesn't really look like a bug. It looks like it's just dm-flakey now returning more errors, and causing btrfs to complain more. Which seems entirely expected. Maybe the

[PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Since the watermark calculations for Skylake are still broken, we're apt to hitting underruns very easily under multi-monitor configurations. While it would be lovely if this was fixed, it's not. Another problem that's been coming from this however, is the mysterious issue of underruns causing

[PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Since the watermark calculations for Skylake are still broken, we're apt to hitting underruns very easily under multi-monitor configurations. While it would be lovely if this was fixed, it's not. Another problem that's been coming from this however, is the mysterious issue of underruns causing

[PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Since the watermark calculations for Skylake are still broken, we're apt to hitting underruns very easily under multi-monitor configurations. While it would be lovely if this was fixed, it's not. Another problem that's been coming from this however, is the mysterious issue of underruns causing

[PATCH v10] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Since the watermark calculations for Skylake are still broken, we're apt to hitting underruns very easily under multi-monitor configurations. While it would be lovely if this was fixed, it's not. Another problem that's been coming from this however, is the mysterious issue of underruns causing

[PACTH v3 1/2] usb: xhci: plat: Enable runtime PM

From: Andrew Bresticker Enable runtime PM for the xhci-plat device so that the parent device may implement runtime PM. Signed-off-by: Andrew Bresticker Tested-by: Robert Foss Signed-off-by: Robert Foss

[PACTH v3 1/2] usb: xhci: plat: Enable runtime PM

From: Andrew Bresticker Enable runtime PM for the xhci-plat device so that the parent device may implement runtime PM. Signed-off-by: Andrew Bresticker Tested-by: Robert Foss Signed-off-by: Robert Foss --- drivers/usb/host/xhci-plat.c | 24 ++-- 1 file changed, 22

[PACTH v3 2/2] usb: xhci: plat: Enable async suspend/resume

From: Andrew Bresticker USB host controllers can take a significant amount of time to suspend and resume, adding several hundred miliseconds to the kernel resume time. Since the XHCI controller has no outside dependencies (other than clocks, which are suspended

[PACTH v3 0/2] usb: xhci: plat: Enable PM, async resume/suspend

From: Robert Foss This series enables runtime PM and asynchronous resume/suspend support for xhci-plat devices. This is a resumbmission of v3. Changes since v1: - Added Signed-off-by: Robert Foss - Added proper metadata tags to series.

[PACTH v3 2/2] usb: xhci: plat: Enable async suspend/resume

From: Andrew Bresticker USB host controllers can take a significant amount of time to suspend and resume, adding several hundred miliseconds to the kernel resume time. Since the XHCI controller has no outside dependencies (other than clocks, which are suspended late/resumed early), allow it to

[PACTH v3 0/2] usb: xhci: plat: Enable PM, async resume/suspend

From: Robert Foss This series enables runtime PM and asynchronous resume/suspend support for xhci-plat devices. This is a resumbmission of v3. Changes since v1: - Added Signed-off-by: Robert Foss - Added proper metadata tags to series. Changes since v2: - Added missing changelog to

Re: [PATCH] device probe: add self triggered delayed work request

On 07/29/16 22:39, Qing Huang wrote: > In normal condition, the device probe requests kept in deferred > queue would only be triggered for re-probing when another new device > probe is finished successfully. This change will set up a delayed > trigger work request if the current deferred probe

Re: [PATCH] device probe: add self triggered delayed work request

On 07/29/16 22:39, Qing Huang wrote: > In normal condition, the device probe requests kept in deferred > queue would only be triggered for re-probing when another new device > probe is finished successfully. This change will set up a delayed > trigger work request if the current deferred probe

Re: [PATCH] clk: Hi6220: enable stub clock driver for ARCH_HISI

On 08/08/16 19:02, Amit Kucheria wrote: This patch is to enable stub clock driver in config for ARCH_HISI. Reported-by: Dietmar Eggemann Signed-off-by: Leo Yan --- drivers/clk/hisilicon/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH] clk: Hi6220: enable stub clock driver for ARCH_HISI

On 08/08/16 19:02, Amit Kucheria wrote: This patch is to enable stub clock driver in config for ARCH_HISI. Reported-by: Dietmar Eggemann Signed-off-by: Leo Yan --- drivers/clk/hisilicon/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/clk/hisilicon/Kconfig

Re: [PATCH 1/3] net: stmmac: dwmac-rk: add rk3366 & rk3399-specific data

Hi Roger, Am Mittwoch, 6. Juli 2016, 18:51:29 schrieb Roger Chen: > Add constants and callback functions for the dwmac on rk3368 socs. > As can be seen, the base structure is the same, only registers and > the bits in them moved slightly. > > Signed-off-by: Roger Chen

Re: [PATCH 1/3] net: stmmac: dwmac-rk: add rk3366 & rk3399-specific data

Hi Roger, Am Mittwoch, 6. Juli 2016, 18:51:29 schrieb Roger Chen: > Add constants and callback functions for the dwmac on rk3368 socs. > As can be seen, the base structure is the same, only registers and > the bits in them moved slightly. > > Signed-off-by: Roger Chen > --- >

Re: [rcu:rcu/next 25/36] include/linux/irqflags.h:79:3: error: implicit declaration of function 'arch_irqs_disabled_flags'

On Mon, Aug 08, 2016 at 10:12:11PM +0200, Richard Weinberger wrote: > Paul, > > Am 15.06.2016 um 14:45 schrieb Paul E. McKenney: > > On Wed, Jun 15, 2016 at 09:05:37AM +0200, Richard Weinberger wrote: > >> Paul, > >> > >> Am 15.06.2016 um 00:54 schrieb Paul E. McKenney: > >>> On Mon, Jun 06, 2016

Re: [rcu:rcu/next 25/36] include/linux/irqflags.h:79:3: error: implicit declaration of function 'arch_irqs_disabled_flags'

On Mon, Aug 08, 2016 at 10:12:11PM +0200, Richard Weinberger wrote: > Paul, > > Am 15.06.2016 um 14:45 schrieb Paul E. McKenney: > > On Wed, Jun 15, 2016 at 09:05:37AM +0200, Richard Weinberger wrote: > >> Paul, > >> > >> Am 15.06.2016 um 00:54 schrieb Paul E. McKenney: > >>> On Mon, Jun 06, 2016

[PATCH v4 00/10] Gadget endpoint request allocation and MIDI

As discussed with Baolin Wang, Michal Nazarewicz and Felipe Balbi. I propose the forced buffer alignment of OUT endpoints USB requests. This is implemented by patches #1 and #3. That not just simplifies the driver code, but it also prevents nasty bugs when buflen is not aligned or even less than

[PATCH v4 00/10] Gadget endpoint request allocation and MIDI

As discussed with Baolin Wang, Michal Nazarewicz and Felipe Balbi. I propose the forced buffer alignment of OUT endpoints USB requests. This is implemented by patches #1 and #3. That not just simplifies the driver code, but it also prevents nasty bugs when buflen is not aligned or even less than

[PATCH v4 05/10] usb: gadget: f_midi: defaults buflen sizes to 512

512 is the value used by wMaxPacketSize, as specified by the USB Spec. This makes sure this driver uses, by default, the most optimal value for IN and OUT endpoint requests. Signed-off-by: Felipe F. Tonello --- drivers/usb/gadget/function/f_midi.c | 2 +-

[PATCH v4 04/10] usb: gadget: f_midi: remove alignment code for OUT endpoint

The new version of alloc_ep_req() already aligns the buffer size to wMaxPacketSize on OUT endpoints. Signed-off-by: Felipe F. Tonello --- drivers/usb/gadget/function/f_midi.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH v4 01/10] usb: gadget: fix usb_ep_align_maybe endianness and new usb_ep_align

USB spec specifies wMaxPacketSize to be little endian (as other properties), so when using this variable in the driver we should convert to the current CPU endianness if necessary. This patch also introduces usb_ep_align() which does always returns the aligned buffer size for an endpoint. This is

[PATCH v4 05/10] usb: gadget: f_midi: defaults buflen sizes to 512

512 is the value used by wMaxPacketSize, as specified by the USB Spec. This makes sure this driver uses, by default, the most optimal value for IN and OUT endpoint requests. Signed-off-by: Felipe F. Tonello --- drivers/usb/gadget/function/f_midi.c | 2 +- drivers/usb/gadget/legacy/gmidi.c|

[PATCH v4 04/10] usb: gadget: f_midi: remove alignment code for OUT endpoint

The new version of alloc_ep_req() already aligns the buffer size to wMaxPacketSize on OUT endpoints. Signed-off-by: Felipe F. Tonello --- drivers/usb/gadget/function/f_midi.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/usb/gadget/function/f_midi.c

[PATCH v4 01/10] usb: gadget: fix usb_ep_align_maybe endianness and new usb_ep_align

USB spec specifies wMaxPacketSize to be little endian (as other properties), so when using this variable in the driver we should convert to the current CPU endianness if necessary. This patch also introduces usb_ep_align() which does always returns the aligned buffer size for an endpoint. This is

<    1   2   3   4   5   6   7   8   9   10   >