[PATCH] Input: elantech - add Fujitsu Lifebook E556 to force crc_enabled

Another Lifebook machine that needs the same quirk as other similar models to make the driver working. Also let's reorder elantech_dmi_force_crc_enabled list so LIfebook enries are in alphabetical order. Reported-by: William Linna Cc: sta...@vger.kernel.org

[PATCH] Input: elantech - add Fujitsu Lifebook E556 to force crc_enabled

Another Lifebook machine that needs the same quirk as other similar models to make the driver working. Also let's reorder elantech_dmi_force_crc_enabled list so LIfebook enries are in alphabetical order. Reported-by: William Linna Cc: sta...@vger.kernel.org Signed-off-by: Dmitry Torokhov ---

[GIT] Networking

Here are the build and merge fixups for the networking stuff. Please pull, thanks a lot! The following changes since commit 41844e36206be90cd4d962ea49b0abc3612a99d0: Merge tag 'staging-4.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging (2016-10-05 14:50:51 -0700) are

[GIT] Networking

Here are the build and merge fixups for the networking stuff. Please pull, thanks a lot! The following changes since commit 41844e36206be90cd4d962ea49b0abc3612a99d0: Merge tag 'staging-4.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging (2016-10-05 14:50:51 -0700) are

Re: [RFC PATCH-tip v4 01/10] locking/osq: Make lock/unlock proper acquire/release barrier

On Wed, 05 Oct 2016, Waiman Long wrote: diff --git a/kernel/locking/osq_lock.c b/kernel/locking/osq_lock.c index 05a3785..1e6823a 100644 --- a/kernel/locking/osq_lock.c +++ b/kernel/locking/osq_lock.c @@ -12,6 +12,23 @@ */ static DEFINE_PER_CPU_SHARED_ALIGNED(struct optimistic_spin_node,

[PATCH] Added Support for STMicroelectronics 16 channels LED7708 LED Driver

--- .../devicetree/bindings/leds/leds-st.txt | 105 ++ KERNEL/Documentation/leds/leds-st7708.txt | 167 +++ KERNEL/drivers/leds/leds-st.c | 1210 KERNEL/include/linux/platform_data/leds-st.h | 170 +++ patches/defconfig

Re: [RFC PATCH-tip v4 01/10] locking/osq: Make lock/unlock proper acquire/release barrier

On Wed, 05 Oct 2016, Waiman Long wrote: diff --git a/kernel/locking/osq_lock.c b/kernel/locking/osq_lock.c index 05a3785..1e6823a 100644 --- a/kernel/locking/osq_lock.c +++ b/kernel/locking/osq_lock.c @@ -12,6 +12,23 @@ */ static DEFINE_PER_CPU_SHARED_ALIGNED(struct optimistic_spin_node,

[PATCH] Added Support for STMicroelectronics 16 channels LED7708 LED Driver

--- .../devicetree/bindings/leds/leds-st.txt | 105 ++ KERNEL/Documentation/leds/leds-st7708.txt | 167 +++ KERNEL/drivers/leds/leds-st.c | 1210 KERNEL/include/linux/platform_data/leds-st.h | 170 +++ patches/defconfig

Re: [PATCH] sparc: migrate exception table users off module.h and onto extable.h

From: Paul Gortmaker Date: Mon, 19 Sep 2016 17:36:29 -0400 > These files were only including module.h for exception table > related functions. We've now separated that content out into its > own file "extable.h" so now move over to that and avoid all the > extra

Re: [PATCH] sparc: migrate exception table users off module.h and onto extable.h

From: Paul Gortmaker Date: Mon, 19 Sep 2016 17:36:29 -0400 > These files were only including module.h for exception table > related functions. We've now separated that content out into its > own file "extable.h" so now move over to that and avoid all the > extra header content in module.h that

[git pull] Input updates for 4.9-rc0

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. You will get new driver for Elan eKTF2127 touchscreen controllers; a new "gpio-decoder" driver to read and report state of several GPIO lines;

[git pull] Input updates for 4.9-rc0

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. You will get new driver for Elan eKTF2127 touchscreen controllers; a new "gpio-decoder" driver to read and report state of several GPIO lines;

[PATCH] x86/unwind: fix oprofile module link error

When compiling on x86 with CONFIG_OPROFILE=m and CONFIG_FRAME_POINTER=n, the oprofile module fails to link: ERROR: ftrace_graph_ret_addr" [arch/x86/oprofile/oprofile.ko] undefined! The problem was introduced when oprofile was converted to use the new x86 unwinder. When frame pointers are

[PATCH] x86/unwind: fix oprofile module link error

When compiling on x86 with CONFIG_OPROFILE=m and CONFIG_FRAME_POINTER=n, the oprofile module fails to link: ERROR: ftrace_graph_ret_addr" [arch/x86/oprofile/oprofile.ko] undefined! The problem was introduced when oprofile was converted to use the new x86 unwinder. When frame pointers are

Re: [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue

On Wed, Oct 05, 2016 at 02:53:58PM -0700, Nadim Almas wrote: > Fixed coding style issue > > Signed-off-by: Nadim Almas > --- > drivers/staging/dgnc/dgnc_neo.h | 18 -- > 1 file changed, 12 insertions(+), 6 deletions(-) > > diff --git

Re: [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue

On Wed, Oct 05, 2016 at 02:53:58PM -0700, Nadim Almas wrote: > Fixed coding style issue > > Signed-off-by: Nadim Almas > --- > drivers/staging/dgnc/dgnc_neo.h | 18 -- > 1 file changed, 12 insertions(+), 6 deletions(-) > > diff --git a/drivers/staging/dgnc/dgnc_neo.h

[PATCH v3 2/4] net: phy: dp83867: add support for MAC impedance configuration

Add support for programmable MAC impedance configuration Signed-off-by: Mugunthan V N --- drivers/net/phy/dp83867.c | 28 1 file changed, 28 insertions(+) diff --git a/drivers/net/phy/dp83867.c b/drivers/net/phy/dp83867.c index 91177a4..1b63924

[PATCH v3 2/4] net: phy: dp83867: add support for MAC impedance configuration

Add support for programmable MAC impedance configuration Signed-off-by: Mugunthan V N --- drivers/net/phy/dp83867.c | 28 1 file changed, 28 insertions(+) diff --git a/drivers/net/phy/dp83867.c b/drivers/net/phy/dp83867.c index 91177a4..1b63924 100644 ---

[PATCH v3 1/4] net: phy: dp83867: Add documentation for optional impedance control

Add documention of ti,impedance-control which can be used to correct MAC impedance mismatch using phy extended registers. Signed-off-by: Mugunthan V N --- Documentation/devicetree/bindings/net/ti,dp83867.txt | 12 1 file changed, 12 insertions(+) diff --git

[PATCH v3 1/4] net: phy: dp83867: Add documentation for optional impedance control

Add documention of ti,impedance-control which can be used to correct MAC impedance mismatch using phy extended registers. Signed-off-by: Mugunthan V N --- Documentation/devicetree/bindings/net/ti,dp83867.txt | 12 1 file changed, 12 insertions(+) diff --git

[PATCH v3 3/4] ARM: dts: dra72-evm-revc: add phy impedance settings

The default impedance settings of the phy is not the optimal value, due to this the second ethernet is not working. Fix it with correct values which makes the second ethernet port to work. Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/dra72-evm-revc.dts | 2 ++ 1 file

[PATCH v3 0/4] add support for impedance control for TI dp83867 phy and fix 2nd ethernet on dra72 rev C evm

Add support for configurable impedance control for TI dp83867 phy via devicetree. More documentation in [1]. CPSW second ethernet is not working, fix it by enabling impedance configuration on the phy. Verified the patch on DRA72 Rev C evm, logs at [2]. Also pushed a branch [3] for others to test.

[PATCH v3 4/4] ARM: dts: dra72-evm-revc: fix correct phy delay

The current delay settings of the phy are not the optimal value, fix it with correct values. Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/dra72-evm-revc.dts | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v3 3/4] ARM: dts: dra72-evm-revc: add phy impedance settings

The default impedance settings of the phy is not the optimal value, due to this the second ethernet is not working. Fix it with correct values which makes the second ethernet port to work. Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/dra72-evm-revc.dts | 2 ++ 1 file changed, 2

[PATCH v3 0/4] add support for impedance control for TI dp83867 phy and fix 2nd ethernet on dra72 rev C evm

Add support for configurable impedance control for TI dp83867 phy via devicetree. More documentation in [1]. CPSW second ethernet is not working, fix it by enabling impedance configuration on the phy. Verified the patch on DRA72 Rev C evm, logs at [2]. Also pushed a branch [3] for others to test.

[PATCH v3 4/4] ARM: dts: dra72-evm-revc: fix correct phy delay

The current delay settings of the phy are not the optimal value, fix it with correct values. Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/dra72-evm-revc.dts | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/dra72-evm-revc.dts

[PATCH] Let CONFIG_STRICT_DEVMEM depends on CONFIG_DEVMEM

With CONFIG_DEVMEM not set, CONFIG_STRICT_DEVMEM will be useless even if it is set =y, thus let's update the dependency in Kconfig. Signed-off-by: Dave Young --- lib/Kconfig.debug |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-x86.orig/lib/Kconfig.debug

[PATCH] Let CONFIG_STRICT_DEVMEM depends on CONFIG_DEVMEM

With CONFIG_DEVMEM not set, CONFIG_STRICT_DEVMEM will be useless even if it is set =y, thus let's update the dependency in Kconfig. Signed-off-by: Dave Young --- lib/Kconfig.debug |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-x86.orig/lib/Kconfig.debug +++

Re: [GIT] Networking

Hi Dave, On Wed, 05 Oct 2016 22:56:12 -0400 (EDT) David Miller wrote: > > Yes, this is where the change got lost. No worries. > I have all of the fixups queued up in my net tree and will send in a pull > request later. Thanks. -- Cheers, Stephen Rothwell

Re: [GIT] Networking

Hi Dave, On Wed, 05 Oct 2016 22:56:12 -0400 (EDT) David Miller wrote: > > Yes, this is where the change got lost. No worries. > I have all of the fixups queued up in my net tree and will send in a pull > request later. Thanks. -- Cheers, Stephen Rothwell

Re: [tip:x86/apic] x86/acpi: Introduce persistent storage for cpuid <-> apicid mapping

On Wed, Oct 5, 2016 at 7:04 AM, Thomas Gleixner wrote: >> @@ -176,6 +177,11 @@ static int acpi_register_lapic(int id, u >> return -EINVAL; >> } >> >> +if (!enabled && (id == disabled_id)) { >> +++disabled_cpus; >> +return -EINVAL; >> +} >

Re: [tip:x86/apic] x86/acpi: Introduce persistent storage for cpuid <-> apicid mapping

On Wed, Oct 5, 2016 at 7:04 AM, Thomas Gleixner wrote: >> @@ -176,6 +177,11 @@ static int acpi_register_lapic(int id, u >> return -EINVAL; >> } >> >> +if (!enabled && (id == disabled_id)) { >> +++disabled_cpus; >> +return -EINVAL; >> +} > > Why would you need

Re: Zram for FreeBSD

Hi, On (10/05/16 16:47), Cory Pruce wrote: >Could one of you tell me why these compression algo’s were chosen, zram supports more than that. https://marc.info/?l=linux-kernel=146469777105130 >if they were implemented as a need for zram, and hm... not all of them (if any at all). lzo,

Re: Zram for FreeBSD

Hi, On (10/05/16 16:47), Cory Pruce wrote: >Could one of you tell me why these compression algo’s were chosen, zram supports more than that. https://marc.info/?l=linux-kernel=146469777105130 >if they were implemented as a need for zram, and hm... not all of them (if any at all). lzo,

Re: error: 'struct net_device' has no member named 'nf_hooks_ingress'

On (10/06/16 06:11), Eric Dumazet wrote: > On Wed, 2016-10-05 at 22:56 +0200, Michal Sojka wrote: > > > this commit is now in mainline as > > e3b37f11e6e4e6b6f02cc762f182ce233d2c1c9d and it breaks my build: > > > > net/netfilter/core.c: In function 'nf_set_hooks_head': > >

Re: error: 'struct net_device' has no member named 'nf_hooks_ingress'

On (10/06/16 06:11), Eric Dumazet wrote: > On Wed, 2016-10-05 at 22:56 +0200, Michal Sojka wrote: > > > this commit is now in mainline as > > e3b37f11e6e4e6b6f02cc762f182ce233d2c1c9d and it breaks my build: > > > > net/netfilter/core.c: In function 'nf_set_hooks_head': > >

Re: [PATCH v3 1/2] config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc

On Wed, Oct 05, 2016 at 05:56:16PM -0500, Babu Moger wrote: > Dave, Gentle reminder to review this patch. Thanks No need to ping Dave. It is in patchwork and he will review the patch eventually. Sam

Re: [PATCH v3 1/2] config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc

On Wed, Oct 05, 2016 at 05:56:16PM -0500, Babu Moger wrote: > Dave, Gentle reminder to review this patch. Thanks No need to ping Dave. It is in patchwork and he will review the patch eventually. Sam

Re: [RFC][PATCH 6/7] printk: use alternative printk buffers

On (10/05/16 11:50), Petr Mladek wrote: [..] > > well, it solves a number of problems that the existing implementation > > cannot handle. > > Please, provide a summary. I wonder if these are real life problems. anything that starts from printk(). I'm trying to address printk() recursion only, by

Re: [RFC][PATCH 6/7] printk: use alternative printk buffers

On (10/05/16 11:50), Petr Mladek wrote: [..] > > well, it solves a number of problems that the existing implementation > > cannot handle. > > Please, provide a summary. I wonder if these are real life problems. anything that starts from printk(). I'm trying to address printk() recursion only, by

Re: [RESEND PATCH v2 2/3] cpufreq: brcmstb-avs-cpufreq: AVS CPUfreq driver for Broadcom STB SoCs

Thanks for accepting all the comments :) On 05-10-16, 14:04, Markus Mayer wrote: > Is there an easy way for me to know via the framework whether init is > being called for the first time vs. init is being called on a > different core after a previous attempt to initialize on another core >

Re: [RESEND PATCH v2 2/3] cpufreq: brcmstb-avs-cpufreq: AVS CPUfreq driver for Broadcom STB SoCs

Thanks for accepting all the comments :) On 05-10-16, 14:04, Markus Mayer wrote: > Is there an easy way for me to know via the framework whether init is > being called for the first time vs. init is being called on a > different core after a previous attempt to initialize on another core >

[GIT PULL] Mailbox changes for v4.9

Hi Linus, The following changes since commit d060e0f603a4156087813d221d818bb39ec91429: Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma (2016-09-06 12:33:12 -0700) are available in the git repository at:

[GIT PULL] Mailbox changes for v4.9

Hi Linus, The following changes since commit d060e0f603a4156087813d221d818bb39ec91429: Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma (2016-09-06 12:33:12 -0700) are available in the git repository at:

linux-next: Tree for Oct 6

Hi all, There will be no linux-next release tomorrow. Please do *not* add any v4.10 material to your linux-next included trees until v4.9-rc1 has been released i.e. the merge window closes. Changes since 20161005: The akpm-current tree gained a conflict against the percpu tree. Non-merge

linux-next: Tree for Oct 6

Hi all, There will be no linux-next release tomorrow. Please do *not* add any v4.10 material to your linux-next included trees until v4.9-rc1 has been released i.e. the merge window closes. Changes since 20161005: The akpm-current tree gained a conflict against the percpu tree. Non-merge

[GIT PULL]: dmaengine updates for 4.9-rc1

Hello Linus, Here is the pull request for dmaengine. One note though, we have dependency between dmaengine tree and tty tree, as one series was merged thru Greg's tree. To resolve we had merged 'tty-for-dma' tag from greg's tree into dmaengine next. This merge will show up conflict in

ERROR: "bad_dma_ops" [drivers/net/ethernet/qualcomm/emac/qcom-emac.ko] undefined!

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a6930aaee06755d1bdcfd943fbf614e4d92bb0c7 commit: b9b17debc69d27cd55e21ee51a5ba7fc50a426cf net: emac: emac gigabit ethernet controller driver date: 5 weeks ago config: m32r-allmodconfig (attached as

[GIT PULL]: dmaengine updates for 4.9-rc1

Hello Linus, Here is the pull request for dmaengine. One note though, we have dependency between dmaengine tree and tty tree, as one series was merged thru Greg's tree. To resolve we had merged 'tty-for-dma' tag from greg's tree into dmaengine next. This merge will show up conflict in

ERROR: "bad_dma_ops" [drivers/net/ethernet/qualcomm/emac/qcom-emac.ko] undefined!

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a6930aaee06755d1bdcfd943fbf614e4d92bb0c7 commit: b9b17debc69d27cd55e21ee51a5ba7fc50a426cf net: emac: emac gigabit ethernet controller driver date: 5 weeks ago config: m32r-allmodconfig (attached as

web.upgrades

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

web.upgrades

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

Re: linux-next: manual merge of the akpm-current tree with the percpu tree

Hi all, On Thu, 6 Oct 2016 13:43:57 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the akpm-current tree got a conflict in: > > mm/percpu.c > > between commits: > > 93c76b6b2faa ("mm/percpu.c: correct max_distance calculation for >

Re: [GIT] Networking

From: Stephen Rothwell Date: Thu, 6 Oct 2016 13:51:52 +1100 > On Wed, 5 Oct 2016 19:14:21 -0700 Linus Torvalds > wrote: >> >> On Wed, Oct 5, 2016 at 5:52 PM, Stephen Rothwell >> wrote: >> > >> > Except that commit

Re: linux-next: manual merge of the akpm-current tree with the percpu tree

Hi all, On Thu, 6 Oct 2016 13:43:57 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the akpm-current tree got a conflict in: > > mm/percpu.c > > between commits: > > 93c76b6b2faa ("mm/percpu.c: correct max_distance calculation for > pcpu_embed_first_chunk()") >

Re: [GIT] Networking

From: Stephen Rothwell Date: Thu, 6 Oct 2016 13:51:52 +1100 > On Wed, 5 Oct 2016 19:14:21 -0700 Linus Torvalds > wrote: >> >> On Wed, Oct 5, 2016 at 5:52 PM, Stephen Rothwell >> wrote: >> > >> > Except that commit effectively moved that function from >> > net/netfilter/nf_tables_netdev.c to

Re: [GIT] Networking

Hi Linus, On Wed, 5 Oct 2016 19:14:21 -0700 Linus Torvalds wrote: > > On Wed, Oct 5, 2016 at 5:52 PM, Stephen Rothwell > wrote: > > > > Except that commit effectively moved that function from > > net/netfilter/nf_tables_netdev.c to > >

Re: [GIT] Networking

Hi Linus, On Wed, 5 Oct 2016 19:14:21 -0700 Linus Torvalds wrote: > > On Wed, Oct 5, 2016 at 5:52 PM, Stephen Rothwell > wrote: > > > > Except that commit effectively moved that function from > > net/netfilter/nf_tables_netdev.c to > > include/net/netfilter/nf_tables_ipv4.h while commit

Re: net/sunrpc/stats.c:204: undefined reference to `_GLOBAL_OFFSET_TABLE_'

On Thu, 6 Oct 2016, Fengguang Wu wrote: > On Tue, Oct 04, 2016 at 09:08:27AM -0400, Nicolas Pitre wrote: > >On Tue, 4 Oct 2016, Fengguang Wu wrote: > > > > > CC Michal. It looks like a microblaze specific error. I'll blacklist > > > this old error on microblaze if there are no good solutions. > >

linux-next: manual merge of the akpm-current tree with the percpu tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/percpu.c between commits: 93c76b6b2faa ("mm/percpu.c: correct max_distance calculation for pcpu_embed_first_chunk()") 9b7396624a7b ("mm/percpu.c: fix potential memory leakage for

Re: net/sunrpc/stats.c:204: undefined reference to `_GLOBAL_OFFSET_TABLE_'

On Thu, 6 Oct 2016, Fengguang Wu wrote: > On Tue, Oct 04, 2016 at 09:08:27AM -0400, Nicolas Pitre wrote: > >On Tue, 4 Oct 2016, Fengguang Wu wrote: > > > > > CC Michal. It looks like a microblaze specific error. I'll blacklist > > > this old error on microblaze if there are no good solutions. > >

linux-next: manual merge of the akpm-current tree with the percpu tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/percpu.c between commits: 93c76b6b2faa ("mm/percpu.c: correct max_distance calculation for pcpu_embed_first_chunk()") 9b7396624a7b ("mm/percpu.c: fix potential memory leakage for

[PATCH v2] scsi: ufshcd: fix possible unclocked register access

Vendor specific setup_clocks callback may require the clocks managed by ufshcd driver to be ON. So if the vendor specific setup_clocks callback is called while the required clocks are turned off, it could result into unclocked register access. To prevent possible unclock register access, this

[PATCH v2] scsi: ufshcd: fix possible unclocked register access

Vendor specific setup_clocks callback may require the clocks managed by ufshcd driver to be ON. So if the vendor specific setup_clocks callback is called while the required clocks are turned off, it could result into unclocked register access. To prevent possible unclock register access, this

Re: [GIT] Networking

On Wed, Oct 5, 2016 at 5:52 PM, Stephen Rothwell wrote: > > Except that commit effectively moved that function from > net/netfilter/nf_tables_netdev.c to > include/net/netfilter/nf_tables_ipv4.h while commit c73c24849011 > ("netfilter: nf_tables_netdev: remove redundant

Re: [GIT] Networking

On Wed, Oct 5, 2016 at 5:52 PM, Stephen Rothwell wrote: > > Except that commit effectively moved that function from > net/netfilter/nf_tables_netdev.c to > include/net/netfilter/nf_tables_ipv4.h while commit c73c24849011 > ("netfilter: nf_tables_netdev: remove redundant ip_hdr assignment") >

Re: [RFC PATCH] mm, compaction: allow compaction for GFP_NOFS requests

On Wed, Oct 05, 2016 at 01:38:45PM +0200, Michal Hocko wrote: > On Wed 05-10-16 07:32:02, Dave Chinner wrote: > > On Tue, Oct 04, 2016 at 10:12:15AM +0200, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > compaction has been disabled for GFP_NOFS and GFP_NOIO requests

Re: [RFC PATCH] mm, compaction: allow compaction for GFP_NOFS requests

On Wed, Oct 05, 2016 at 01:38:45PM +0200, Michal Hocko wrote: > On Wed 05-10-16 07:32:02, Dave Chinner wrote: > > On Tue, Oct 04, 2016 at 10:12:15AM +0200, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > compaction has been disabled for GFP_NOFS and GFP_NOIO requests since > > > the

Re: BUG_ON() in workingset_node_shadows_dec() triggers

On Wed, Oct 5, 2016 at 6:59 PM, Dave Chinner wrote: > > In XFS, we use ASSERT() (could be XFS_BUG_ON() for all > that the name matters) but we only define that to BUG_ON if > CONFIG_XFS_DEBUG=y. > > For "production debug" kernels we have CONFIG_XFS_WARN=y, which > turns

Re: BUG_ON() in workingset_node_shadows_dec() triggers

On Wed, Oct 5, 2016 at 6:59 PM, Dave Chinner wrote: > > In XFS, we use ASSERT() (could be XFS_BUG_ON() for all > that the name matters) but we only define that to BUG_ON if > CONFIG_XFS_DEBUG=y. > > For "production debug" kernels we have CONFIG_XFS_WARN=y, which > turns ASSERT() into WARN_ON().

Re: [PATCH] x86/entry/64: Fix context tracking state warning when load_gs_index fails

On Sep 29, 2016 5:43 PM, "Wanpeng Li" wrote: > > 2016-09-30 5:01 GMT+08:00 Andy Lutomirski : > > On Mon, Sep 26, 2016 at 4:49 AM, Wanpeng Li wrote: > >> From: Wanpeng Li > >> > >> WARNING: CPU: 0 PID: 3331

Re: [PATCH] tpm: don't destroy chip device prematurely

On Thu, Oct 06, 2016 at 12:43:13AM +, Winkler, Tomas wrote: > > You keep asserting that, but it just isn't true at all. > > Okay, let's rephrase, that calling device_del before tpm_transmit is not sane > when using runtime_pm. Maybe, but I haven't heard an explanation from you why that is

Re: [PATCH] x86/entry/64: Fix context tracking state warning when load_gs_index fails

On Sep 29, 2016 5:43 PM, "Wanpeng Li" wrote: > > 2016-09-30 5:01 GMT+08:00 Andy Lutomirski : > > On Mon, Sep 26, 2016 at 4:49 AM, Wanpeng Li wrote: > >> From: Wanpeng Li > >> > >> WARNING: CPU: 0 PID: 3331 at arch/x86/entry/common.c:45 > >> enter_from_user_mode+0x32/0x50 > >> CPU: 0 PID:

Re: [PATCH] tpm: don't destroy chip device prematurely

On Thu, Oct 06, 2016 at 12:43:13AM +, Winkler, Tomas wrote: > > You keep asserting that, but it just isn't true at all. > > Okay, let's rephrase, that calling device_del before tpm_transmit is not sane > when using runtime_pm. Maybe, but I haven't heard an explanation from you why that is

Re: BUG_ON() in workingset_node_shadows_dec() triggers

On Tue, Oct 04, 2016 at 08:29:00PM -0700, Linus Torvalds wrote: > On Tue, Oct 4, 2016 at 7:43 PM, Paul Gortmaker > wrote: > > > > A couple years ago Ingo had an idea to kill BUG_ON abuse that I made > > a 1st pass at. Back then it seemed nobody cared. Maybe that

Re: BUG_ON() in workingset_node_shadows_dec() triggers

On Tue, Oct 04, 2016 at 08:29:00PM -0700, Linus Torvalds wrote: > On Tue, Oct 4, 2016 at 7:43 PM, Paul Gortmaker > wrote: > > > > A couple years ago Ingo had an idea to kill BUG_ON abuse that I made > > a 1st pass at. Back then it seemed nobody cared. Maybe that has since > > changed? > > > >

[ANNOUNCE] 3.12.64-rt86

Dear RT Folks, I'm pleased to announce the 3.12.64-rt86 stable release. This release is just an update to the new stable 3.12.64 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 3.12.64-rt86

Dear RT Folks, I'm pleased to announce the 3.12.64-rt86 stable release. This release is just an update to the new stable 3.12.64 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 4.4.23-rt33

Dear RT Folks, I'm pleased to announce the 4.4.23-rt33 stable release. This release is just an update to the new stable 4.4.23 version and no RT specific changes have been made. You can get this release via the git tree at:

[ANNOUNCE] 4.4.23-rt33

Dear RT Folks, I'm pleased to announce the 4.4.23-rt33 stable release. This release is just an update to the new stable 4.4.23 version and no RT specific changes have been made. You can get this release via the git tree at:

Re: [PATCH] random: Fix early crash in credit_entropy_bits

This was discussed and Linus wanted to fix it a different way. Please see this thread: http://www.gossamer-threads.com/lists/linux/kernel/2525929 Cheers, - Ted

Re: [PATCH] random: Fix early crash in credit_entropy_bits

This was discussed and Linus wanted to fix it a different way. Please see this thread: http://www.gossamer-threads.com/lists/linux/kernel/2525929 Cheers, - Ted

Re: [RFC 1/2] sdhci: Add device tree property sd-broken-highspeed

On 2016/10/6 5:22, Julia Cartwright wrote: On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote: On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote: On 23 September 2016 at 22:01, Zach Brown wrote: Certain board configurations can make

Re: [RFC 1/2] sdhci: Add device tree property sd-broken-highspeed

On 2016/10/6 5:22, Julia Cartwright wrote: On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote: On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote: On 23 September 2016 at 22:01, Zach Brown wrote: Certain board configurations can make highspeed malfunction due to timing issues. In

Re: [PATCH v2] phy: micrel.c: Enable ksz9031 energy-detect power-down mode

From: Mike Looijmans Date: Tue, 4 Oct 2016 07:52:04 +0200 > Set bit 0 in register 1C.23 to enable the EDPD feature of the > KSZ9031 PHY. This reduces power consumption when the link is > down. > > Signed-off-by: Mike Looijmans > --- > v2:

Re: [PATCH v2] phy: micrel.c: Enable ksz9031 energy-detect power-down mode

From: Mike Looijmans Date: Tue, 4 Oct 2016 07:52:04 +0200 > Set bit 0 in register 1C.23 to enable the EDPD feature of the > KSZ9031 PHY. This reduces power consumption when the link is > down. > > Signed-off-by: Mike Looijmans > --- > v2: Unconditionally enable EDPD mode Applied.

Talent Scout

Dear Concern, I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film Corporation Located in the United State, is Soliciting for the Right to use Your Photo/Face and Personality as One of the Semi -Major Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story of

Talent Scout

Dear Concern, I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film Corporation Located in the United State, is Soliciting for the Right to use Your Photo/Face and Personality as One of the Semi -Major Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story of

[PATCH] scsi: ufshcd: fix possible unclocked register access

Vendor specific setup_clocks callback may require the clocks managed by ufshcd driver to be ON. So if the vendor specific setup_clocks callback is called while the required clocks are turned off, it could result into unclocked register access. To prevent possible unclock register access, this

[PATCH] scsi: ufshcd: fix possible unclocked register access

Vendor specific setup_clocks callback may require the clocks managed by ufshcd driver to be ON. So if the vendor specific setup_clocks callback is called while the required clocks are turned off, it could result into unclocked register access. To prevent possible unclock register access, this

Re: [GIT] Networking

Hi Linus, On Wed, 5 Oct 2016 15:37:17 -0700 Linus Torvalds wrote: > > On Wed, Oct 5, 2016 at 3:29 PM, Stephen Rothwell > wrote: > > > > I have been carrying the following merge fix patch (for the merge of > > the net-next tree with Linus'

Re: [GIT] Networking

Hi Linus, On Wed, 5 Oct 2016 15:37:17 -0700 Linus Torvalds wrote: > > On Wed, Oct 5, 2016 at 3:29 PM, Stephen Rothwell > wrote: > > > > I have been carrying the following merge fix patch (for the merge of > > the net-next tree with Linus' tree) for a while now which seems to have > > got

RE: [PATCH] tpm: don't destroy chip device prematurely

> On Wed, Oct 05, 2016 at 08:09:17PM +, Winkler, Tomas wrote: > > > It could, but that patch was not merged yet, and I believe even if the > > issue is exposed only with runtime_pm currently, we have a bug in > > design even w/o runtime pm. > > Please don't make changes without any

RE: [PATCH] tpm: don't destroy chip device prematurely

> On Wed, Oct 05, 2016 at 08:09:17PM +, Winkler, Tomas wrote: > > > It could, but that patch was not merged yet, and I believe even if the > > issue is exposed only with runtime_pm currently, we have a bug in > > design even w/o runtime pm. > > Please don't make changes without any

Re: callchain map refcounting fixes was Re: [PATCH perf/core] perf script: fix a use after free crash.

On Wed, 5 Oct 2016 08:45:24 -0300 Arnaldo Carvalho de Melo wrote: > Em Sat, Oct 01, 2016 at 08:13:36PM -0700, Krister Johansen escreveu: > > If dso__load_kcore frees all of the existing maps, but one has already > > been attached to a callchain cursor node, then we can get a

Re: callchain map refcounting fixes was Re: [PATCH perf/core] perf script: fix a use after free crash.

On Wed, 5 Oct 2016 08:45:24 -0300 Arnaldo Carvalho de Melo wrote: > Em Sat, Oct 01, 2016 at 08:13:36PM -0700, Krister Johansen escreveu: > > If dso__load_kcore frees all of the existing maps, but one has already > > been attached to a callchain cursor node, then we can get a SIGSEGV in > > any

Re: [GIT] Networking

From: Pablo Neira Ayuso Date: Thu, 6 Oct 2016 02:09:45 +0200 > On Wed, Oct 05, 2016 at 03:37:17PM -0700, Linus Torvalds wrote: >> On Wed, Oct 5, 2016 at 3:29 PM, Stephen Rothwell >> wrote: >> > >> > I have been carrying the following merge fix patch

Re: [GIT] Networking

From: Pablo Neira Ayuso Date: Thu, 6 Oct 2016 02:09:45 +0200 > On Wed, Oct 05, 2016 at 03:37:17PM -0700, Linus Torvalds wrote: >> On Wed, Oct 5, 2016 at 3:29 PM, Stephen Rothwell >> wrote: >> > >> > I have been carrying the following merge fix patch (for the merge of >> > the net-next tree

Re: [PATCH V3 2/4] ARM64 LPC: LPC driver implementation on Hip06

On Tue, 2016-10-04 at 13:02 +0100, John Garry wrote: > Right, so I think Zhichang can make the necessary generic changes to  > 8250 OF driver to support IO port as well as MMIO-based. > > However an LPC-based earlycon driver is still required. > > A note on hip07-based D05 (for those unaware):

Re: [PATCH V3 2/4] ARM64 LPC: LPC driver implementation on Hip06

On Tue, 2016-10-04 at 13:02 +0100, John Garry wrote: > Right, so I think Zhichang can make the necessary generic changes to  > 8250 OF driver to support IO port as well as MMIO-based. > > However an LPC-based earlycon driver is still required. > > A note on hip07-based D05 (for those unaware):

  1   2   3   4   5   6   7   8   9   10   >