Re: [PATCH] Make mtdblock can handle partition bigger than 4G.

Hi Lepton, On Fri, 17 Feb 2017 15:37:33 -0800 Lepton Wu wrote: Can you please add a commit message and prefix the subject with 'mtd: '. Something like 'mtd: Fix mtdblock for >4GB MTD devices'. > Signed-off-by: Lepton Wu > --- > drivers/mtd/mtdblock.c

Re: [PATCH] Make mtdblock can handle partition bigger than 4G.

Hi Lepton, On Fri, 17 Feb 2017 15:37:33 -0800 Lepton Wu wrote: Can you please add a commit message and prefix the subject with 'mtd: '. Something like 'mtd: Fix mtdblock for >4GB MTD devices'. > Signed-off-by: Lepton Wu > --- > drivers/mtd/mtdblock.c| 33 +

[PATCH 1/6] staging: rtl8192e: Replaced comparison to NULL statements

This patch corrects check generated by checkpatch.pl by replacing comparison to null statements with equivalent statements in the form of "!x". Signed-off-by: simran singhal --- drivers/staging/rtl8192e/rtl819x_BAProc.c | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH 1/6] staging: rtl8192e: Replaced comparison to NULL statements

This patch corrects check generated by checkpatch.pl by replacing comparison to null statements with equivalent statements in the form of "!x". Signed-off-by: simran singhal --- drivers/staging/rtl8192e/rtl819x_BAProc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [4.9.10] ip_route_me_harder() reading off-slab

On 17 February 2017 at 13:36, Eric Dumazet wrote: > On Fri, 2017-02-17 at 12:36 +0800, Daniel J Blueman wrote: >> When booting a VM in libvirt/KVM attached to a local bridge and KASAN >> enabled on 4.9.10, we see a stream of KASAN warnings about off-slab >> access [1]. >>

Re: [4.9.10] ip_route_me_harder() reading off-slab

On 17 February 2017 at 13:36, Eric Dumazet wrote: > On Fri, 2017-02-17 at 12:36 +0800, Daniel J Blueman wrote: >> When booting a VM in libvirt/KVM attached to a local bridge and KASAN >> enabled on 4.9.10, we see a stream of KASAN warnings about off-slab >> access [1]. >> >> Let me know if you'd

RE: [PATCH] media: uvcvideo: Add support for changing UVC_URBS/UVC_MAX_PACKETS from sysfs

Ping ! >-Original Message- >From: Anurag Kumar Vulisha [mailto:anurag.kumar.vuli...@xilinx.com] >Sent: Friday, February 03, 2017 10:10 PM >To: Laurent Pinchart ; Mauro Carvalho >Chehab >Cc: Punnaiah Choudary Kalluri

RE: [PATCH] media: uvcvideo: Add support for changing UVC_URBS/UVC_MAX_PACKETS from sysfs

Ping ! >-Original Message- >From: Anurag Kumar Vulisha [mailto:anurag.kumar.vuli...@xilinx.com] >Sent: Friday, February 03, 2017 10:10 PM >To: Laurent Pinchart ; Mauro Carvalho >Chehab >Cc: Punnaiah Choudary Kalluri ; Anirudha Sarangi >; linux-me...@vger.kernel.org; linux-

Re: [PATCH v2 2/3] extable: verify address is read-only

Hi Eddie, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [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/Eddie-Kovsky/provide-check

Re: [PATCH v2 2/3] extable: verify address is read-only

Hi Eddie, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [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/Eddie-Kovsky/provide-check

Re: [PATCH v2 2/3] extable: verify address is read-only

Hi Eddie, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc8 next-20170217] [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/Eddie-Kovsky/provide-check-for-ro_after_init

Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Andy, On Fri, Feb 17, 2017 at 10:12:36PM -0800, Andy Lutomirski wrote: On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu wrote: Greetings, FYI here is an old bug, however is still active in mainline kernel.

Re: [PATCH v2 2/3] extable: verify address is read-only

Hi Eddie, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc8 next-20170217] [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/Eddie-Kovsky/provide-check-for-ro_after_init

Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Andy, On Fri, Feb 17, 2017 at 10:12:36PM -0800, Andy Lutomirski wrote: On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu wrote: Greetings, FYI here is an old bug, however is still active in mainline kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master [

Re: [PATCH v2 3/3] Make vmbus register arguments read-only

Hi Eddie, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [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/Eddie-Kovsky/provide-check

Re: [PATCH v2 3/3] Make vmbus register arguments read-only

Hi Eddie, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc8 next-20170217] [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/Eddie-Kovsky/provide-check

Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu wrote: > Greetings, > > FYI here is an old bug, however is still active in mainline kernel. > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > [3.185986] init[1] vsyscall attempted with

Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu wrote: > Greetings, > > FYI here is an old bug, however is still active in mainline kernel. > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > [3.185986] init[1] vsyscall attempted with vsyscall=none >

[PATCH v2 3/3] Make vmbus register arguments read-only

Use the new RO check functions introduced in this series to make the vmbus register functions verify that the address of their arguments are read-only. Addresses that fail the verification are rejected. Signed-off-by: Eddie Kovsky --- drivers/hv/vmbus_drv.c | 10 ++ 1

[PATCH v2 3/3] Make vmbus register arguments read-only

Use the new RO check functions introduced in this series to make the vmbus register functions verify that the address of their arguments are read-only. Addresses that fail the verification are rejected. Signed-off-by: Eddie Kovsky --- drivers/hv/vmbus_drv.c | 10 ++ 1 file changed, 10

[PATCH v2 0/3] provide check for ro_after_init memory sections

Provide a mechansim for other functions to verify that their arguments are read-only. Use this mechansim in the vmbus register functions to reject arguments that fail this test. This implements a suggestion made by Kees Cook for the Kernel Self Protection Project: * provide mechanism to

[PATCH v2 0/3] provide check for ro_after_init memory sections

Provide a mechansim for other functions to verify that their arguments are read-only. Use this mechansim in the vmbus register functions to reject arguments that fail this test. This implements a suggestion made by Kees Cook for the Kernel Self Protection Project: * provide mechanism to

[PATCH v2 1/3] module: verify address is read-only

Implement a mechanism to check if a module's address is in the rodata or ro_after_init sections. It mimics the exsiting functions that test if an address is inside a module's text section. Signed-off-by: Eddie Kovsky --- include/linux/module.h | 7 +++ kernel/module.c

[PATCH v2 2/3] extable: verify address is read-only

Provide a mechanism to check if the address of a variable is const or ro_after_init. It mimics the existing functions that test if an address is inside the kernel's text section. Signed-off-by: Eddie Kovsky --- include/linux/kernel.h | 2 ++ kernel/extable.c | 29

[PATCH v2 1/3] module: verify address is read-only

Implement a mechanism to check if a module's address is in the rodata or ro_after_init sections. It mimics the exsiting functions that test if an address is inside a module's text section. Signed-off-by: Eddie Kovsky --- include/linux/module.h | 7 +++ kernel/module.c| 44

[PATCH v2 2/3] extable: verify address is read-only

Provide a mechanism to check if the address of a variable is const or ro_after_init. It mimics the existing functions that test if an address is inside the kernel's text section. Signed-off-by: Eddie Kovsky --- include/linux/kernel.h | 2 ++ kernel/extable.c | 29

[x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

master git bisect good 4ce4a759a3e221b5265ebd03c2fb69a7cf3e # 11:40121+ 255 Add linux-next specific files for 20170217 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/lkp Intel Corporation dmesg-yocto-vp-48:2017021802472

[x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

t specific files for 20170217 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/lkp Intel Corporation dmesg-yocto-vp-48:20170218024722:x86_64-randconfig-w0-02171423:4.3.0-01035-ga75a3f6:2.gz Description: a

[x86/vsyscall] 3dc33bd30f Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Kees, It's an old patch, however the panic still happens in linux-next 20170217. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b Author: Kees Cook <keesc...@chromium.org> AuthorDate: Wed Aug 12 17:55:19 2015

[x86/vsyscall] 3dc33bd30f Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Hi Kees, It's an old patch, however the panic still happens in linux-next 20170217. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b Author: Kees Cook AuthorDate: Wed Aug 12 17:55:19 2015 -0700 Commit: Ingo Molnar

[GIT] Networking

1) Fix leak in dpaa_eth error paths, from Dan Carpenter. 2) Use after free when using IPV6_RECVPKTINFO, from Andrey Konovalov. 3) fanout_release() cannot be invoked from atomic contexts, from Anoob Soman. 4) Fix bogus attempt at lockdep annotation in IRDA. 5) dev_fill_metadata_dst() can

[GIT] Networking

1) Fix leak in dpaa_eth error paths, from Dan Carpenter. 2) Use after free when using IPV6_RECVPKTINFO, from Andrey Konovalov. 3) fanout_release() cannot be invoked from atomic contexts, from Anoob Soman. 4) Fix bogus attempt at lockdep annotation in IRDA. 5) dev_fill_metadata_dst() can

[drm] bea5b158ff BUG: unable to handle kernel NULL pointer dereference at 0000000000000748

0- 1 Add linux-next specific files for 20170217 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/pipermail/lkp Intel Corporation dmesg-quantal-vp-95:20170218095527:x86_64-randconfig-ne0-02160954:4.8.0-rc4-00

[drm] bea5b158ff BUG: unable to handle kernel NULL pointer dereference at 0000000000000748

nel.dk/linux-block # extra tests on tree/branch linux-next/master git bisect bad 4ce4a759a3e221b5265ebd03c2fb69a7cf3e # 11:07 0- 1 Add linux-next specific files for 20170217 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists.01.org/piperma

[x86/mm] e1a58320a3 WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page()

1fd6 # 04:30 0- 2 Merge tag 'powerpc-4.10-5' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux # extra tests on tree/branch linux-next/master git bisect bad 4ce4a759a3e221b5265ebd03c2fb69a7cf3e # 04:35 0- 28 Add linux-next specific files for 20170217

[x86/mm] e1a58320a3 WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page()

/linux/kernel/git/powerpc/linux # extra tests on tree/branch linux-next/master git bisect bad 4ce4a759a3e221b5265ebd03c2fb69a7cf3e # 04:35 0- 28 Add linux-next specific files for 20170217 --- 0-DAY kernel test infrastructureOpen Source Technology Center https://lists

Re: [PATCH 17/35] drivers/gpu: Convert remaining uses of pr_warning to pr_warn

On 02/18/2017 01:22 AM, Christian König wrote: > Am 17.02.2017 um 08:11 schrieb Joe Perches: >> To enable eventual removal of pr_warning >> >> This makes pr_warn use consistent for drivers/gpu >> >> Prior to this patch, there were 15 uses of pr_warning and >> 20 uses of pr_warn in drivers/gpu >>

Re: [PATCH 17/35] drivers/gpu: Convert remaining uses of pr_warning to pr_warn

On 02/18/2017 01:22 AM, Christian König wrote: > Am 17.02.2017 um 08:11 schrieb Joe Perches: >> To enable eventual removal of pr_warning >> >> This makes pr_warn use consistent for drivers/gpu >> >> Prior to this patch, there were 15 uses of pr_warning and >> 20 uses of pr_warn in drivers/gpu >>

[PATCH] tiny: remove a redundant semicolon in wait.h

In the end of macro wait_event_interruptible_lock_irq_timeout(), there is a semicolon, and at the location where this macro is referenced by macro wait_event_interruptible_lock_irq_timeout(), there is another semicolon, then we have two semicolon at end of a line. Redundant semicolons here

[PATCH] tiny: remove a redundant semicolon in wait.h

In the end of macro wait_event_interruptible_lock_irq_timeout(), there is a semicolon, and at the location where this macro is referenced by macro wait_event_interruptible_lock_irq_timeout(), there is another semicolon, then we have two semicolon at end of a line. Redundant semicolons here

Re: [PATCH] staging: rtl8192u: Fix warnings about endianness

On February 16, 2017 4:31:16 AM GMT+08:00, Dan Carpenter wrote: >On Wed, Feb 15, 2017 at 09:33:15AM +0100, Arnd Bergmann wrote: >> I see the same warning was addressed very differently in 99277c1f9962 >> ("Staging: rtl8192e: Fix Sparse warning of cast to restricted

Re: [PATCH] staging: rtl8192u: Fix warnings about endianness

On February 16, 2017 4:31:16 AM GMT+08:00, Dan Carpenter wrote: >On Wed, Feb 15, 2017 at 09:33:15AM +0100, Arnd Bergmann wrote: >> I see the same warning was addressed very differently in 99277c1f9962 >> ("Staging: rtl8192e: Fix Sparse warning of cast to restricted __le16 >in >>

[PATCH] bcm2048: Fix checkpatch checks

Fix following checks: CHECK: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON() + BUG_ON((index+2) >= BCM2048_MAX_RDS_RT); CHECK: spaces preferred around that '+' (ctx:VxV) + BUG_ON((index+2) >= BCM2048_MAX_RDS_RT); ^

[PATCH] bcm2048: Fix checkpatch checks

Fix following checks: CHECK: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON() + BUG_ON((index+2) >= BCM2048_MAX_RDS_RT); CHECK: spaces preferred around that '+' (ctx:VxV) + BUG_ON((index+2) >= BCM2048_MAX_RDS_RT); ^

RFC: Getting rid of LTR in VMX

There's no code here because the patch is trivial, but I want to run the idea by you all first to see if there are any issues. VMX is silly and forces the TSS limit to the minimum on VM exits. KVM wastes lots of cycles bumping it back up to accomodate the io bitmap. I propose that we rework

RFC: Getting rid of LTR in VMX

There's no code here because the patch is trivial, but I want to run the idea by you all first to see if there are any issues. VMX is silly and forces the TSS limit to the minimum on VM exits. KVM wastes lots of cycles bumping it back up to accomodate the io bitmap. I propose that we rework

Re: [PATCH v9 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry Torokhov wrote: > > AFAIK there is no mainline board using the DT except ours (and the upcoming > > OMAP5-Pyra), so we shouldn't care too much. If you prefer, you can remove > > this > > compatibility property. We don't need it for our

Re: [PATCH v9 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

Hi, On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry Torokhov wrote: > > AFAIK there is no mainline board using the DT except ours (and the upcoming > > OMAP5-Pyra), so we shouldn't care too much. If you prefer, you can remove > > this > > compatibility property. We don't need it for our

[net-next][PATCH v1] RDS: keep data type consistent in the user visible header

rds.h is exported to /usr/include/rds.h, so u8, u64 leads to errors like below. /usr/include/linux/rds.h:197: error: expected specifier-qualifier-list before 'u8' /usr/include/linux/rds.h:202: error: expected specifier-qualifier-list before 'u8' Fix it by following same types as rest of the

[net-next][PATCH v1] RDS: keep data type consistent in the user visible header

rds.h is exported to /usr/include/rds.h, so u8, u64 leads to errors like below. /usr/include/linux/rds.h:197: error: expected specifier-qualifier-list before 'u8' /usr/include/linux/rds.h:202: error: expected specifier-qualifier-list before 'u8' Fix it by following same types as rest of the

[net-next][PATCH] RDS: keep data type consistent in the user visible header

From: Santosh Shilimkar rds.h is exported to /usr/include/rds.h, so u8, u64 leads to errors like below. /usr/include/linux/rds.h:197: error: expected specifier-qualifier-list before 'u8' /usr/include/linux/rds.h:202: error: expected specifier-qualifier-list before 'u8'

[net-next][PATCH] RDS: keep data type consistent in the user visible header

From: Santosh Shilimkar rds.h is exported to /usr/include/rds.h, so u8, u64 leads to errors like below. /usr/include/linux/rds.h:197: error: expected specifier-qualifier-list before 'u8' /usr/include/linux/rds.h:202: error: expected specifier-qualifier-list before 'u8' Fix it by following

Re: [PATCH] Staging: ks7010: ks_*: Braces should be used on all arms of these statements

On Fri, 2017-02-17 at 14:50 -0800, Joe Perches wrote: > On Fri, 2017-02-17 at 22:41 +0100, Shiva Kerdel wrote: > > Braces should be used on all arms of these statements (CHECK).. > > [] > > diff --git a/drivers/staging/ks7010/ks_hostif.c > > b/drivers/staging/ks7010/ks_hostif.c > > [] > > @@

Re: [PATCH] Staging: ks7010: ks_*: Braces should be used on all arms of these statements

On Fri, 2017-02-17 at 14:50 -0800, Joe Perches wrote: > On Fri, 2017-02-17 at 22:41 +0100, Shiva Kerdel wrote: > > Braces should be used on all arms of these statements (CHECK).. > > [] > > diff --git a/drivers/staging/ks7010/ks_hostif.c > > b/drivers/staging/ks7010/ks_hostif.c > > [] > > @@

Re: [RFC 7/8] fpga-region: add sysfs interface

On Fri, Feb 17, 2017 at 04:28:37PM -0600, Yves Vandervennet wrote: > Moritz, > > whatever solution we decide to go with has to work with other OS'es. The > last thing we want to do is to have wrappers that are Linux specific. I do agree that we should make sure the format is reasonably well

Re: [RFC 7/8] fpga-region: add sysfs interface

On Fri, Feb 17, 2017 at 04:28:37PM -0600, Yves Vandervennet wrote: > Moritz, > > whatever solution we decide to go with has to work with other OS'es. The > last thing we want to do is to have wrappers that are Linux specific. I do agree that we should make sure the format is reasonably well

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

Ok, I personally like that better anyhow. Also, there was mention of the line limit even exceeding 100 characters (130ish?) and that was being tossed around at one point (if I remember correctly). On Fri, Feb 17, 2017 at 8:38 PM, Joe Perches wrote: > On Fri, 2017-02-17 at

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

Ok, I personally like that better anyhow. Also, there was mention of the line limit even exceeding 100 characters (130ish?) and that was being tossed around at one point (if I remember correctly). On Fri, Feb 17, 2017 at 8:38 PM, Joe Perches wrote: > On Fri, 2017-02-17 at 20:32 -0500, Adan

Re: [PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

On Friday, February 17, 2017 05:26:59 PM Florian Fainelli wrote: > > On 02/17/2017 05:20 PM, Rafael J. Wysocki wrote: > > On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote: > >> On 02/17/2017 10:30 AM, Markus Mayer wrote: > >>> From: Markus Mayer > >>> > >>>

Re: [PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

On Friday, February 17, 2017 05:26:59 PM Florian Fainelli wrote: > > On 02/17/2017 05:20 PM, Rafael J. Wysocki wrote: > > On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote: > >> On 02/17/2017 10:30 AM, Markus Mayer wrote: > >>> From: Markus Mayer > >>> > >>> Add maintainer

[RFC][PATCH] cpufreq: User/admin documentation update and consolidation

From: Rafael J. Wysocki The user/admin documentation of cpufreq is badly outdated. It conains stale and/or inaccurate information along with things that are not particularly useful. Also, some of the important pieces are missing from it. For this reason, add a new

[RFC][PATCH] cpufreq: User/admin documentation update and consolidation

From: Rafael J. Wysocki The user/admin documentation of cpufreq is badly outdated. It conains stale and/or inaccurate information along with things that are not particularly useful. Also, some of the important pieces are missing from it. For this reason, add a new user/admin document for

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

Thanks, Joe. Is this to say that scripts/checkpatch.pl should be updated to some higher column limit? I have made these cleanup changes before in a like manner. On Fri, Feb 17, 2017 at 8:17 PM, Joe Perches wrote: > On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote: >>

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

Thanks, Joe. Is this to say that scripts/checkpatch.pl should be updated to some higher column limit? I have made these cleanup changes before in a like manner. On Fri, Feb 17, 2017 at 8:17 PM, Joe Perches wrote: > On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote: >> Fix checkpatch.pl

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

On Fri, 2017-02-17 at 20:32 -0500, Adan Hawthorn wrote: > Thanks, Joe. > > Is this to say that scripts/checkpatch.pl should be updated to some > higher column limit? I have made these cleanup changes before in a > like manner. Hard to say. There could be some sensitivity to long identifier

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

On Fri, 2017-02-17 at 20:32 -0500, Adan Hawthorn wrote: > Thanks, Joe. > > Is this to say that scripts/checkpatch.pl should be updated to some > higher column limit? I have made these cleanup changes before in a > like manner. Hard to say. There could be some sensitivity to long identifier

Re: [PATCH] PM / QoS: Fix memory leak on resume_latency.notifiers

On Thursday, February 16, 2017 05:21:50 PM John Keeping wrote: > Since commit 2d984ad132a8 ("PM / QoS: Introcuce latency tolerance device > PM QoS type") we reassign "c" to point at qos->latency_tolerance before > freeing c->notifiers, but the notifiers field of latency_tolerance is > never used.

Re: [PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

On 02/17/2017 05:20 PM, Rafael J. Wysocki wrote: > On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote: >> On 02/17/2017 10:30 AM, Markus Mayer wrote: >>> From: Markus Mayer >>> >>> Add maintainer information for bmips-cpufreq.c. >>> >>> Signed-off-by: Markus

Re: [PATCH] PM / QoS: Fix memory leak on resume_latency.notifiers

On Thursday, February 16, 2017 05:21:50 PM John Keeping wrote: > Since commit 2d984ad132a8 ("PM / QoS: Introcuce latency tolerance device > PM QoS type") we reassign "c" to point at qos->latency_tolerance before > freeing c->notifiers, but the notifiers field of latency_tolerance is > never used.

Re: [PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

On 02/17/2017 05:20 PM, Rafael J. Wysocki wrote: > On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote: >> On 02/17/2017 10:30 AM, Markus Mayer wrote: >>> From: Markus Mayer >>> >>> Add maintainer information for bmips-cpufreq.c. >>> >>> Signed-off-by: Markus Mayer >> >> Looks

Re: [PATCH] PM / sleep: Fix test_suspend after sleep state rework

On Friday, February 17, 2017 02:18:44 PM Geert Uytterhoeven wrote: > When passing "test_suspend=mem" to the kernel: > > PM: can't test 'mem' suspend state > > and the suspend test is not run. > > Commit 406e79385f3223d8 ("PM / sleep: System sleep state selection > interface rework") changed

Re: [PATCH trivial 4/4] PM / Documentation: Spelling s/wrtie/write/

On Friday, February 17, 2017 04:36:39 PM Geert Uytterhoeven wrote: > Signed-off-by: Geert Uytterhoeven > Cc: Rafael J. Wysocki > Cc: linux...@vger.kernel.org > --- > Documentation/power/states.txt | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote: > On 02/17/2017 10:30 AM, Markus Mayer wrote: > > From: Markus Mayer > > > > Add maintainer information for bmips-cpufreq.c. > > > > Signed-off-by: Markus Mayer > > Looks great, thanks

Re: [PATCH] PM / sleep: Fix test_suspend after sleep state rework

On Friday, February 17, 2017 02:18:44 PM Geert Uytterhoeven wrote: > When passing "test_suspend=mem" to the kernel: > > PM: can't test 'mem' suspend state > > and the suspend test is not run. > > Commit 406e79385f3223d8 ("PM / sleep: System sleep state selection > interface rework") changed

Re: [PATCH trivial 4/4] PM / Documentation: Spelling s/wrtie/write/

On Friday, February 17, 2017 04:36:39 PM Geert Uytterhoeven wrote: > Signed-off-by: Geert Uytterhoeven > Cc: Rafael J. Wysocki > Cc: linux...@vger.kernel.org > --- > Documentation/power/states.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH] MAINTAINERS: cpufreq: add bmips-cpufreq.c

On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote: > On 02/17/2017 10:30 AM, Markus Mayer wrote: > > From: Markus Mayer > > > > Add maintainer information for bmips-cpufreq.c. > > > > Signed-off-by: Markus Mayer > > Looks great, thanks for adding this, one nit below: > > > ---

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote: > Fix checkpatch.pl warning of the form "WARNING: line over 80 characters." [] > diff --git a/drivers/staging/bcm2835-audio/bcm2835.h > b/drivers/staging/bcm2835-audio/bcm2835.h [] > @@ -163,8 +163,10 @@ int bcm2835_audio_write(struct

Re: [PATCH 5/5] staging: bcm2835-audio: bcm2835.h: fix line length coding style issue

On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote: > Fix checkpatch.pl warning of the form "WARNING: line over 80 characters." [] > diff --git a/drivers/staging/bcm2835-audio/bcm2835.h > b/drivers/staging/bcm2835-audio/bcm2835.h [] > @@ -163,8 +163,10 @@ int bcm2835_audio_write(struct

Re: [PATCH v4 29/36] media: imx: mipi-csi2: enable setting and getting of frame rates

On 02/15/2017 06:19 PM, Steve Longerbeam wrote: From: Russell King Setting and getting frame rates is part of the negotiation mechanism between subdevs. The lack of support means that a frame rate at the sensor can't be negotiated through the subdev path. Add

Re: [PATCH v4 29/36] media: imx: mipi-csi2: enable setting and getting of frame rates

On 02/15/2017 06:19 PM, Steve Longerbeam wrote: From: Russell King Setting and getting frame rates is part of the negotiation mechanism between subdevs. The lack of support means that a frame rate at the sensor can't be negotiated through the subdev path. Add support at MIPI CSI2 level for

Re: [PATCH v4 29/36] media: imx: mipi-csi2: enable setting and getting of frame rates

On 02/15/2017 06:19 PM, Steve Longerbeam wrote: From: Russell King Setting and getting frame rates is part of the negotiation mechanism between subdevs. The lack of support means that a frame rate at the sensor can't be negotiated through the subdev path. Add

Re: [PATCH v4 29/36] media: imx: mipi-csi2: enable setting and getting of frame rates

On 02/15/2017 06:19 PM, Steve Longerbeam wrote: From: Russell King Setting and getting frame rates is part of the negotiation mechanism between subdevs. The lack of support means that a frame rate at the sensor can't be negotiated through the subdev path. Add support at MIPI CSI2 level for

Re: [PATCH 4/5] staging: bcm2835-audio: bcm2835.h: fix volatile coding style issue

Thank you, Joe. Please remove this patch at this time; it was sent in error. On Fri, Feb 17, 2017 at 6:04 PM, Joe Perches wrote: > On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote: >> Fix checkpatch.pl warning of the form "WARNING: Use of volatile is >> usually wrong:

Re: [PATCH 4/5] staging: bcm2835-audio: bcm2835.h: fix volatile coding style issue

Thank you, Joe. Please remove this patch at this time; it was sent in error. On Fri, Feb 17, 2017 at 6:04 PM, Joe Perches wrote: > On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote: >> Fix checkpatch.pl warning of the form "WARNING: Use of volatile is >> usually wrong: see

Re: [PATCH 35/35] sound/soc: Convert remaining uses of pr_warning to pr_warn

On Fri, 2017-02-17 at 15:57 -0800, Nicolin Chen wrote: > On Fri, Feb 17, 2017 at 11:48:54PM +, Mark Brown wrote: > > On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote: > > > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote: > > > > To enable eventual removal of pr_warning

Re: [PATCH 35/35] sound/soc: Convert remaining uses of pr_warning to pr_warn

On Fri, 2017-02-17 at 15:57 -0800, Nicolin Chen wrote: > On Fri, Feb 17, 2017 at 11:48:54PM +, Mark Brown wrote: > > On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote: > > > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote: > > > > To enable eventual removal of pr_warning

Re: [Suggestion/Problems] perf annoate: Some problems related to the source code view and Improvement of it with line numbers

On 02/17/2017 10:29 PM, Arnaldo Carvalho de Melo wrote: Em Fri, Feb 17, 2017 at 11:33:29AM +0900, Taeung Song escreveu: Hi, Arnaldo :) Regarding perf annotate: 1) Problem : wrong line numbers on perf-annotate (both stdio and TUI) 2) Problem : wrong sum of overhead(percent) matching source

Re: [Suggestion/Problems] perf annoate: Some problems related to the source code view and Improvement of it with line numbers

On 02/17/2017 10:29 PM, Arnaldo Carvalho de Melo wrote: Em Fri, Feb 17, 2017 at 11:33:29AM +0900, Taeung Song escreveu: Hi, Arnaldo :) Regarding perf annotate: 1) Problem : wrong line numbers on perf-annotate (both stdio and TUI) 2) Problem : wrong sum of overhead(percent) matching source

Re: [PATCH V2 4/6] PM / domain: Register for PM QOS performance notifier

Viresh Kumar writes: > Some platforms have the capability to configure the performance state of > their Power Domains. The performance levels are represented by positive > integer values, a lower value represents lower performance state. > > This patch registers the

Re: [PATCH V2 4/6] PM / domain: Register for PM QOS performance notifier

Viresh Kumar writes: > Some platforms have the capability to configure the performance state of > their Power Domains. The performance levels are represented by positive > integer values, a lower value represents lower performance state. > > This patch registers the power domain framework for PM

Re: [RFT 3/4] regulator: max14577: Remove support for platform data

On Fri, Feb 17, 2017 at 10:01:59PM +0200, Krzysztof Kozlowski wrote: > max14577 family of drivers are used only on Exynos-based ARMv7 boards > which all were converted to DeviceTree long time ago. Remove the > support for platform data to simplify the driver. Acked-by: Mark Brown

Re: [RFT 3/4] regulator: max14577: Remove support for platform data

On Fri, Feb 17, 2017 at 10:01:59PM +0200, Krzysztof Kozlowski wrote: > max14577 family of drivers are used only on Exynos-based ARMv7 boards > which all were converted to DeviceTree long time ago. Remove the > support for platform data to simplify the driver. Acked-by: Mark Brown

Re: [PATCH V2 5/6] PM / domain: Save/restore performance state at runtime suspend/resume

Viresh Kumar writes: > With runtime PM, the devices get suspended while the system is up and > running in order to save power. At such times, it is important to > re-evaluate the required performance state of the domain, in order to > choose a lower state if possible. >

Re: [PATCH V2 5/6] PM / domain: Save/restore performance state at runtime suspend/resume

Viresh Kumar writes: > With runtime PM, the devices get suspended while the system is up and > running in order to save power. At such times, it is important to > re-evaluate the required performance state of the domain, in order to > choose a lower state if possible. > > This patch updates the

Re: [PATCH 35/35] sound/soc: Convert remaining uses of pr_warning to pr_warn

On Fri, Feb 17, 2017 at 11:48:54PM +, Mark Brown wrote: > On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote: > > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote: > > > To enable eventual removal of pr_warning > > > > > > This makes pr_warn use consistent for sound/soc >

Re: [PATCH 35/35] sound/soc: Convert remaining uses of pr_warning to pr_warn

On Fri, Feb 17, 2017 at 11:48:54PM +, Mark Brown wrote: > On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote: > > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote: > > > To enable eventual removal of pr_warning > > > > > > This makes pr_warn use consistent for sound/soc >

Re: e1000_netpoll() , BUG: sleeping function called from invalid context

On 18.02.2017 00:44, Cong Wang wrote: On Fri, Feb 17, 2017 at 3:38 PM, Gabriel C wrote: My card seems to use the e1000e driver which is buit-in.. Anyway here an objdump -x : http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/objdump-x_e1000.ko.txt Found

Re: e1000_netpoll() , BUG: sleeping function called from invalid context

On 18.02.2017 00:44, Cong Wang wrote: On Fri, Feb 17, 2017 at 3:38 PM, Gabriel C wrote: My card seems to use the e1000e driver which is buit-in.. Anyway here an objdump -x : http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/objdump-x_e1000.ko.txt Found disable_hardirq() but not

Re: [PATCH 35/35] sound/soc: Convert remaining uses of pr_warning to pr_warn

On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote: > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote: > > To enable eventual removal of pr_warning > > > > This makes pr_warn use consistent for sound/soc > > > > Prior to this patch, there were 5 uses of pr_warning and > >

Re: [PATCH 35/35] sound/soc: Convert remaining uses of pr_warning to pr_warn

On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote: > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote: > > To enable eventual removal of pr_warning > > > > This makes pr_warn use consistent for sound/soc > > > > Prior to this patch, there were 5 uses of pr_warning and > >

  1   2   3   4   5   6   7   8   9   10   >