[PATCH 3/3] ata: add Atari Falcon PATA controller driver

Add Atari Falcon PATA controller driver. The major difference when compared to legacy IDE's falconide host driver is that we are using polled PIO mode and thus avoiding the need for STDMA locking magic altogether. Tested under ARAnyM emulator. Signed-off-by: Bartlomiej Zolnierkiewicz

[PATCH 1/3] ata: allow subsystem to be used on m68k arch

When libata was merged m68k lacked IOMAP support. This has not been true for a long time now so allow subsystem to be used on m68k. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/ata/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/ata/Kconfig

[PATCH 0/3] ata: add m68k/Atari Falcon PATA support

Hi, This patchset adds m68k/Atari Falcon PATA support to libata. The major difference in the new libata's pata_falcon host driver when compared to legacy IDE's falconide host driver is that we are using polled PIO mode and thus avoiding the need for STDMA locking magic altogether. Tested under

[PATCH 3/3] ata: add Atari Falcon PATA controller driver

Add Atari Falcon PATA controller driver. The major difference when compared to legacy IDE's falconide host driver is that we are using polled PIO mode and thus avoiding the need for STDMA locking magic altogether. Tested under ARAnyM emulator. Signed-off-by: Bartlomiej Zolnierkiewicz ---

Re: [Linux v4.10.0-rc1+] Still call-traces after suspend-resume (pm? i915? cpu/hotplug?)

On Fri, Dec 30, 2016 at 12:40 PM, Sedat Dilek wrote: > Hi, > > I have already reported this issue in [1]. > One of the issue was solved. > Unfortunately, it looks like there is still a different problem here > (Ubuntu/precise AMD64). > > I tried v4.10-rc1 and latest Linus

Re: [Linux v4.10.0-rc1+] Still call-traces after suspend-resume (pm? i915? cpu/hotplug?)

On Fri, Dec 30, 2016 at 12:40 PM, Sedat Dilek wrote: > Hi, > > I have already reported this issue in [1]. > One of the issue was solved. > Unfortunately, it looks like there is still a different problem here > (Ubuntu/precise AMD64). > > I tried v4.10-rc1 and latest Linus tree up to... > > commit

Re: brcmfmac: fix spelling mistakes on "Ivalid"

Colin Ian King wrote: > From: Colin Ian King > > Trivial fixes to spelling mistake "Ivalid" to "Invalid" in > brcmf_err error messages. > > Signed-off-by: Colin Ian King > Acked-by: Arend van Spriel

Re: brcmfmac: fix spelling mistakes on "Ivalid"

Colin Ian King wrote: > From: Colin Ian King > > Trivial fixes to spelling mistake "Ivalid" to "Invalid" in > brcmf_err error messages. > > Signed-off-by: Colin Ian King > Acked-by: Arend van Spriel Patch applied to wireless-drivers-next.git, thanks. ad334bbb07b0 brcmfmac: fix spelling

Re: rtlwifi: fix spelling mistake: "contry" -> "country"

Colin Ian King wrote: > From: Colin Ian King > > trivial fix to spelling mistake in RT_TRACE message > > Signed-off-by: Colin Ian King > Acked-by: Larry Finger Patch applied to

Re: rtlwifi: fix spelling mistake: "contry" -> "country"

Colin Ian King wrote: > From: Colin Ian King > > trivial fix to spelling mistake in RT_TRACE message > > Signed-off-by: Colin Ian King > Acked-by: Larry Finger Patch applied to wireless-drivers-next.git, thanks. 3b1fc7680a0f rtlwifi: fix spelling mistake: "contry" -> "country" --

Re: libertas: constify cfg80211_ops structures

Bhumika Goyal wrote: > cfg80211_ops structures are only passed as an argument to the function > wiphy_new. This argument is of type const, so cfg80211_ops strutures > having this property can be declared as const. > Done using Coccinelle > > @r1 disable optional_qualifier @ >

Re: libertas: constify cfg80211_ops structures

Bhumika Goyal wrote: > cfg80211_ops structures are only passed as an argument to the function > wiphy_new. This argument is of type const, so cfg80211_ops strutures > having this property can be declared as const. > Done using Coccinelle > > @r1 disable optional_qualifier @ > identifier i; >

[PATCH v6 1/3] remoteproc: qcom: Compatible string based private resource initialization.

MSS rproc loader need chip specific resources initialization during probe to load and boot modem firmware, this need compatible string based differentiation in resources to be initialized. This patch add and provide a template struct whose fields represent all those resources which are needed to

[PATCH v6 3/3] remoteproc: qcom: Initialize and enable proxy and active regulators.

Certain regulators need voting by rproc on behalf of hexagon only during restart operation but certain regulator need to be voted till hexagon is up, these regulators are identified as proxy and active regulators respectively. This patch provide interface to initialize, enable and disable proxy

[PATCH v6 2/3] remoteproc: qcom: Initialize and enable proxy and active clocks.

Certain clocks need voting by rproc on behalf of hexagon only during restart operation but certain clocks need to be voted till hexagon is up, these clocks are identified as proxy and active clocks respectively. This patch provide interface to initialize, enable and disable proxy and active clocks

[PATCH v6 0/3]remoteproc: qcom: Modification of MSS rproc driver for future platform support.

This is patchset v6 having modifications as per comment on patchset v5. Major changes w.r.t. patchset v5 are as below. 1- Squashing into one the two different patches to initialize and enable the regulators and clocks. 2- Removal of certain unnecessary code and also cleaning of

[PATCH v6 1/3] remoteproc: qcom: Compatible string based private resource initialization.

MSS rproc loader need chip specific resources initialization during probe to load and boot modem firmware, this need compatible string based differentiation in resources to be initialized. This patch add and provide a template struct whose fields represent all those resources which are needed to

[PATCH v6 3/3] remoteproc: qcom: Initialize and enable proxy and active regulators.

Certain regulators need voting by rproc on behalf of hexagon only during restart operation but certain regulator need to be voted till hexagon is up, these regulators are identified as proxy and active regulators respectively. This patch provide interface to initialize, enable and disable proxy

[PATCH v6 2/3] remoteproc: qcom: Initialize and enable proxy and active clocks.

Certain clocks need voting by rproc on behalf of hexagon only during restart operation but certain clocks need to be voted till hexagon is up, these clocks are identified as proxy and active clocks respectively. This patch provide interface to initialize, enable and disable proxy and active clocks

[PATCH v6 0/3]remoteproc: qcom: Modification of MSS rproc driver for future platform support.

This is patchset v6 having modifications as per comment on patchset v5. Major changes w.r.t. patchset v5 are as below. 1- Squashing into one the two different patches to initialize and enable the regulators and clocks. 2- Removal of certain unnecessary code and also cleaning of

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

On 30.12.2016 15:30, Sean Young wrote: On Fri, Dec 30, 2016 at 01:07:52PM +, Sean Young wrote: Hi Ivo,, On Fri, Dec 30, 2016 at 01:30:01PM +0200, Ivaylo Dimitrov wrote: On 20.12.2016 19:50, Sean Young wrote: This driver was written using lirc since rc-core did not support

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

On 30.12.2016 15:30, Sean Young wrote: On Fri, Dec 30, 2016 at 01:07:52PM +, Sean Young wrote: Hi Ivo,, On Fri, Dec 30, 2016 at 01:30:01PM +0200, Ivaylo Dimitrov wrote: On 20.12.2016 19:50, Sean Young wrote: This driver was written using lirc since rc-core did not support

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

On Tue, Dec 27, 2016 at 6:19 PM, Tony Lindgren wrote: > Having the pin control framework call pin controller functions > before it's probe has finished is not nice as the pin controller > device driver does not yet have struct pinctrl_dev handle. > Let's fix this issue by

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

On Tue, Dec 27, 2016 at 6:19 PM, Tony Lindgren wrote: > Having the pin control framework call pin controller functions > before it's probe has finished is not nice as the pin controller > device driver does not yet have struct pinctrl_dev handle. > Let's fix this issue by adding deferred work

[PATCH] pinctrl: add some comments to the hog/late init code

It confused me a bit so it may confuse others. Make it crystal clear what is going on here for any future readers. Cc: Tony Lindgren Signed-off-by: Linus Walleij --- drivers/pinctrl/core.c | 12 1 file changed, 12 insertions(+) diff

[PATCH] pinctrl: add some comments to the hog/late init code

It confused me a bit so it may confuse others. Make it crystal clear what is going on here for any future readers. Cc: Tony Lindgren Signed-off-by: Linus Walleij --- drivers/pinctrl/core.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/pinctrl/core.c

[PATCH v2] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, this patch adds this reserved zone and redefines the usable memory range. Signed-off-by: Neil Armstrong --- Changes since v1 at [1] : - Renamed reg into linux,usable-memory to ovveride u-boot

[PATCH v2] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, this patch adds this reserved zone and redefines the usable memory range. Signed-off-by: Neil Armstrong --- Changes since v1 at [1] : - Renamed reg into linux,usable-memory to ovveride u-boot memory - only kept secmon

Re: rtlwifi: rtl_usb: Fix missing entry in USB driver's private data

Larry Finger wrote: > These drivers need to be able to reference "struct ieee80211_hw" from > the driver's private data, and vice versa. The USB driver failed to > store the address of ieee80211_hw in the private data. Although this > bug has been present for a long

Re: rtlwifi: rtl_usb: Fix missing entry in USB driver's private data

Larry Finger wrote: > These drivers need to be able to reference "struct ieee80211_hw" from > the driver's private data, and vice versa. The USB driver failed to > store the address of ieee80211_hw in the private data. Although this > bug has been present for a long time, it was not exposed until

Re: sg_io HARDENED_USERCOPY_PAGESPAN trace

On Thu, Dec 29, 2016 at 10:43:51AM -0500, Dave Jones wrote: > On Wed, Dec 28, 2016 at 11:56:42PM -0800, Christoph Hellwig wrote: > > On Wed, Dec 28, 2016 at 04:40:16PM -0500, Dave Jones wrote: > > > sg_io+0x113/0x470 > > > > Can you resolve that to a source line using a gdb? > > It's the

Re: sg_io HARDENED_USERCOPY_PAGESPAN trace

On Thu, Dec 29, 2016 at 10:43:51AM -0500, Dave Jones wrote: > On Wed, Dec 28, 2016 at 11:56:42PM -0800, Christoph Hellwig wrote: > > On Wed, Dec 28, 2016 at 04:40:16PM -0500, Dave Jones wrote: > > > sg_io+0x113/0x470 > > > > Can you resolve that to a source line using a gdb? > > It's the

Re: [PATCH v2 3/4] ARM64: dts: exynos5433: use macros for pinctrl configuration on Exynos5433

On Fri, Dec 30, 2016 at 5:14 AM, Andi Shyti wrote: > Use the macros defined in include/dt-bindings/pinctrl/samsung.h > instead of hardcoded values. > > Signed-off-by: Andi Shyti These look fine, but that this and the other DTS patch through ARM

Re: [PATCH v2 3/4] ARM64: dts: exynos5433: use macros for pinctrl configuration on Exynos5433

On Fri, Dec 30, 2016 at 5:14 AM, Andi Shyti wrote: > Use the macros defined in include/dt-bindings/pinctrl/samsung.h > instead of hardcoded values. > > Signed-off-by: Andi Shyti These look fine, but that this and the other DTS patch through ARM SoC. If you also need the headerfile patch

Re: [PATCH v2 2/4] pinctrl: dt-bindings: samsung: add drive strength macros for Exynos5433

On Fri, Dec 30, 2016 at 5:14 AM, Andi Shyti wrote: > Commit 5db7e3bb87df ("pinctrl: dt-bindings: samsung: Add header with > values used for configuration") has added a header file for defining the > pinctrl values in order to avoid hardcoded settings in the Exynos > DTS

Re: [PATCH v2 2/4] pinctrl: dt-bindings: samsung: add drive strength macros for Exynos5433

On Fri, Dec 30, 2016 at 5:14 AM, Andi Shyti wrote: > Commit 5db7e3bb87df ("pinctrl: dt-bindings: samsung: Add header with > values used for configuration") has added a header file for defining the > pinctrl values in order to avoid hardcoded settings in the Exynos > DTS related files. > > Extend

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

On Fri, Dec 30, 2016 at 01:07:52PM +, Sean Young wrote: > Hi Ivo,, > > On Fri, Dec 30, 2016 at 01:30:01PM +0200, Ivaylo Dimitrov wrote: > > On 20.12.2016 19:50, Sean Young wrote: > > >This driver was written using lirc since rc-core did not support > > >transmitter-only hardware at that

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

On Fri, Dec 30, 2016 at 01:07:52PM +, Sean Young wrote: > Hi Ivo,, > > On Fri, Dec 30, 2016 at 01:30:01PM +0200, Ivaylo Dimitrov wrote: > > On 20.12.2016 19:50, Sean Young wrote: > > >This driver was written using lirc since rc-core did not support > > >transmitter-only hardware at that

Re: [PATCH v2 1/4] pinctrl: samsung: Fix the width of PINCFG_TYPE_DRV bitfields for Exynos5433

On Fri, Dec 30, 2016 at 5:14 AM, Andi Shyti wrote: > From: Chanwoo Choi > > This patch fixes the wrong width of PINCFG_TYPE_DRV bitfields for Exynos5433 > because PINCFG_TYPE_DRV of Exynos5433 has 4bit fields in the *_DRV > registers. Usually,

Re: [PATCH v2 1/4] pinctrl: samsung: Fix the width of PINCFG_TYPE_DRV bitfields for Exynos5433

On Fri, Dec 30, 2016 at 5:14 AM, Andi Shyti wrote: > From: Chanwoo Choi > > This patch fixes the wrong width of PINCFG_TYPE_DRV bitfields for Exynos5433 > because PINCFG_TYPE_DRV of Exynos5433 has 4bit fields in the *_DRV > registers. Usually, other Exynos have 2bit field for PINCFG_TYPE_DRV. >

[no subject]

Ciao, è un piacere conoscerti.Io sono Christina H. Koch, uno Stato ufficiale dell'Esercito da stati uniti d'America,ho una cosa importante da discutere con te, che può portare a un business partner o qualcos'altro, mi presento meglio e inviare le mie foto non appena ho ricevuto la tua mail.

[no subject]

Ciao, è un piacere conoscerti.Io sono Christina H. Koch, uno Stato ufficiale dell'Esercito da stati uniti d'America,ho una cosa importante da discutere con te, che può portare a un business partner o qualcos'altro, mi presento meglio e inviare le mie foto non appena ho ricevuto la tua mail.

Re: [RFC v2 2/3] pinctrl: imx: use radix trees for groups and functions

On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson wrote: > This change is inspired from the pinctrl-single architecture. > > The problem with current implementation is that it isn't possible > to add/remove functions and/or groups dynamically. The radix tree > offers

Re: [RFC v2 2/3] pinctrl: imx: use radix trees for groups and functions

On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson wrote: > This change is inspired from the pinctrl-single architecture. > > The problem with current implementation is that it isn't possible > to add/remove functions and/or groups dynamically. The radix tree > offers an easy way to do so. The intent

Re: [RFC v2 1/3] pinctrl: imx: remove const qualifier of imx_pinctrl_soc_info

On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson wrote: > Otherwise can't dynamically update fields such as ngroups which can > change over time (with a dt-overlay for instance). > > Signed-off-by: Gary Bisson Patch applied with

Re: [RFC v2 1/3] pinctrl: imx: remove const qualifier of imx_pinctrl_soc_info

On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson wrote: > Otherwise can't dynamically update fields such as ngroups which can > change over time (with a dt-overlay for instance). > > Signed-off-by: Gary Bisson Patch applied with Fabio's review tag. Yours, Linus Walleij

Re: [RFC v2 2/3] pinctrl: imx: use radix trees for groups and functions

n Thu, Dec 29, 2016 at 10:44 AM, Gary Bisson wrote: > On Tue, Dec 27, 2016 at 11:07 PM, Linus Walleij > wrote: >> >> On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson >> wrote: >> >> > This change is inspired

Re: [RFC v2 2/3] pinctrl: imx: use radix trees for groups and functions

n Thu, Dec 29, 2016 at 10:44 AM, Gary Bisson wrote: > On Tue, Dec 27, 2016 at 11:07 PM, Linus Walleij > wrote: >> >> On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson >> wrote: >> >> > This change is inspired from the pinctrl-single architecture. >> > >> > The problem with current implementation is

Re: [PATCH 10/20] gpio: pca953x: Add optional reset gpio control

On Thu, Dec 29, 2016 at 11:27 PM, Steve Longerbeam wrote: > Add optional reset-gpios pin control. If present, de-assert the > specified reset gpio pin to bring the chip out of reset. > > Signed-off-by: Steve Longerbeam > Cc: Linus Walleij

Re: [PATCH 10/20] gpio: pca953x: Add optional reset gpio control

On Thu, Dec 29, 2016 at 11:27 PM, Steve Longerbeam wrote: > Add optional reset-gpios pin control. If present, de-assert the > specified reset gpio pin to bring the chip out of reset. > > Signed-off-by: Steve Longerbeam > Cc: Linus Walleij > Cc: Alexandre Courbot > Cc:

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

Hi Ivo,, On Fri, Dec 30, 2016 at 01:30:01PM +0200, Ivaylo Dimitrov wrote: > On 20.12.2016 19:50, Sean Young wrote: > >This driver was written using lirc since rc-core did not support > >transmitter-only hardware at that time. Now that it does, port > >this driver. > > > >Compile tested only. > >

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

Hi Ivo,, On Fri, Dec 30, 2016 at 01:30:01PM +0200, Ivaylo Dimitrov wrote: > On 20.12.2016 19:50, Sean Young wrote: > >This driver was written using lirc since rc-core did not support > >transmitter-only hardware at that time. Now that it does, port > >this driver. > > > >Compile tested only. > >

Re: [PATCH 2/2] iio: misc: add support for GPIO power switches

n Thu, Dec 29, 2016 at 5:29 PM, Sebastian Reichel wrote: > On Wed, Dec 28, 2016 at 01:50:17PM +0100, Linus Walleij wrote: >> On Sun, Dec 11, 2016 at 11:21 PM, Bartosz Golaszewski >> wrote: >> >> > Some power-measuring ADCs work together with power load

Re: [PATCH 2/2] iio: misc: add support for GPIO power switches

n Thu, Dec 29, 2016 at 5:29 PM, Sebastian Reichel wrote: > On Wed, Dec 28, 2016 at 01:50:17PM +0100, Linus Walleij wrote: >> On Sun, Dec 11, 2016 at 11:21 PM, Bartosz Golaszewski >> wrote: >> >> > Some power-measuring ADCs work together with power load switches which >> > allow to power-cycle

Re: net: wireless: marvell: libertas: constify cfg80211_ops structures

Bhumika Goyal wrote: > cfg80211_ops structures are only passed as an argument to the function > wiphy_new. This argument is of type const, so cfg80211_ops strutures > having this property can be declared as const. > Done using Coccinelle > > @r1 disable optional_qualifier @ >

Re: net: wireless: marvell: libertas: constify cfg80211_ops structures

Bhumika Goyal wrote: > cfg80211_ops structures are only passed as an argument to the function > wiphy_new. This argument is of type const, so cfg80211_ops strutures > having this property can be declared as const. > Done using Coccinelle > > @r1 disable optional_qualifier @ > identifier i; >

Re: [PATCH] pinctrl: single: fix spelling mistakes on "Ivalid"

On Fri, Dec 23, 2016 at 1:47 AM, Colin King wrote: > From: Colin Ian King > > Trivial fixe to spelling mistake "Ivalid" to "Invalid" in > dev_err error message. > > Signed-off-by: Colin Ian King Patch applied with

Re: [PATCH] pinctrl: single: fix spelling mistakes on "Ivalid"

On Fri, Dec 23, 2016 at 1:47 AM, Colin King wrote: > From: Colin Ian King > > Trivial fixe to spelling mistake "Ivalid" to "Invalid" in > dev_err error message. > > Signed-off-by: Colin Ian King Patch applied with Tony's ACK. Yours, Linus Walleij

Re: [PATCH V1] pinctrl:pxa:pinctrl-pxa2xx:- No need of devm functions

On Thu, Dec 29, 2016 at 8:20 AM, Robert Jarzmik wrote: > Linus Walleij writes: > >> On Thu, Dec 8, 2016 at 3:35 PM, Arvind Yadav >> wrote: >> >>> In functions pxa2xx_build_functions, the memory allocated for >>>

Re: net: wireless: ath: wil6210: constify cfg80211_ops structures

Bhumika Goyal wrote: > cfg80211_ops structures are only passed as an argument to the function > wiphy_new. This argument is of type const, so cfg80211_ops strutures > having this property can be declared as const. > Done using Coccinelle > > @r1 disable optional_qualifier @ >

Re: [PATCH V1] pinctrl:pxa:pinctrl-pxa2xx:- No need of devm functions

On Thu, Dec 29, 2016 at 8:20 AM, Robert Jarzmik wrote: > Linus Walleij writes: > >> On Thu, Dec 8, 2016 at 3:35 PM, Arvind Yadav >> wrote: >> >>> In functions pxa2xx_build_functions, the memory allocated for >>> 'functions' is live within the function only. After the >>> allocation it is

Re: net: wireless: ath: wil6210: constify cfg80211_ops structures

Bhumika Goyal wrote: > cfg80211_ops structures are only passed as an argument to the function > wiphy_new. This argument is of type const, so cfg80211_ops strutures > having this property can be declared as const. > Done using Coccinelle > > @r1 disable optional_qualifier @ > identifier i; >

Re: [linux-sunxi] [PATCH 1/2] drivers: pinctrl: add driver for Allwinner H5 SoC

On Mon, Dec 26, 2016 at 3:33 PM, André Przywara wrote: > So while this patch technically looks correct, I was wondering if we > should really explore the possibility of making the whole of sunxi > pinctrl DT controlled. > I brought this up a while ago, but people weren't

Re: [linux-sunxi] [PATCH 1/2] drivers: pinctrl: add driver for Allwinner H5 SoC

On Mon, Dec 26, 2016 at 3:33 PM, André Przywara wrote: > So while this patch technically looks correct, I was wondering if we > should really explore the possibility of making the whole of sunxi > pinctrl DT controlled. > I brought this up a while ago, but people weren't overly enthusiastic >

[PATCH] net: stmmac: remove unused duplicate property snps,axi_all

From: Niklas Cassel For core revision 3.x Address-Aligned Beats is available in two registers. The DT property snps,aal was created for AAL in the DMA bus register, which is a read/write bit. The DT property snps,axi_all was created for AXI_AAL in the AXI bus mode

[PATCH] net: stmmac: remove unused duplicate property snps,axi_all

From: Niklas Cassel For core revision 3.x Address-Aligned Beats is available in two registers. The DT property snps,aal was created for AAL in the DMA bus register, which is a read/write bit. The DT property snps,axi_all was created for AXI_AAL in the AXI bus mode register, which is a read only

Re: [patch] mm, thp: always direct reclaim for MADV_HUGEPAGE even when deferred

On Fri 30-12-16 12:36:20, Mel Gorman wrote: [...] > I'll neither ack nor nak this patch. However, I would much prefer an > additional option be added to sysfs called defer-fault that would avoid > all fault-based stalls but still potentially stall for MADV_HUGEPAGE. Would you consider changing

Re: [patch] mm, thp: always direct reclaim for MADV_HUGEPAGE even when deferred

On Fri 30-12-16 12:36:20, Mel Gorman wrote: [...] > I'll neither ack nor nak this patch. However, I would much prefer an > additional option be added to sysfs called defer-fault that would avoid > all fault-based stalls but still potentially stall for MADV_HUGEPAGE. Would you consider changing

Re: orinoco: Use shash instead of ahash for MIC calculations

Kalle Valo writes: > Kalle Valo writes: > >> Andrew Lutomirski wrote: >>> Eric Biggers pointed out that the orinoco driver pointed scatterlists >>> at the stack. >>> >>> Fix it by switching from ahash to shash. The result should be

Re: orinoco: Use shash instead of ahash for MIC calculations

Kalle Valo writes: > Kalle Valo writes: > >> Andrew Lutomirski wrote: >>> Eric Biggers pointed out that the orinoco driver pointed scatterlists >>> at the stack. >>> >>> Fix it by switching from ahash to shash. The result should be >>> simpler, faster, and more correct. >>> >>> Cc:

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Fri, Dec 30, 2016 at 12:05:45PM +0100, Michal Hocko wrote: > On Fri 30-12-16 10:19:26, Mel Gorman wrote: > > On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote: > > > On Fri 23-12-16 23:26:00, Nils Holland wrote: > > > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote: >

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Fri, Dec 30, 2016 at 12:05:45PM +0100, Michal Hocko wrote: > On Fri 30-12-16 10:19:26, Mel Gorman wrote: > > On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote: > > > On Fri 23-12-16 23:26:00, Nils Holland wrote: > > > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote: >

Re: [patch] mm, thp: always direct reclaim for MADV_HUGEPAGE even when deferred

On Thu, Dec 22, 2016 at 01:05:27PM -0800, David Rientjes wrote: > On Thu, 22 Dec 2016, Michal Hocko wrote: > > > > Currently, when defrag is set to "madvise", thp allocations will direct > > > reclaim. However, when defrag is set to "defer", all thp allocations do > > > not attempt reclaim

Re: [patch] mm, thp: always direct reclaim for MADV_HUGEPAGE even when deferred

On Thu, Dec 22, 2016 at 01:05:27PM -0800, David Rientjes wrote: > On Thu, 22 Dec 2016, Michal Hocko wrote: > > > > Currently, when defrag is set to "madvise", thp allocations will direct > > > reclaim. However, when defrag is set to "defer", all thp allocations do > > > not attempt reclaim

Re: [PATCH 0/2] Use macros to describe gpios on rockchip platform

Am Samstag, 22. Oktober 2016, 20:51:46 CET schrieb Andy Yan: > As patch 150696e2e3a4("Add GPIO pin index definition for rockchip pinctrl") > has been applied, now we can use these macros to describe the corresponding > gpio ranther than hard code numbers, this will make the dts easier to read >

Re: [PATCH 0/2] Use macros to describe gpios on rockchip platform

Am Samstag, 22. Oktober 2016, 20:51:46 CET schrieb Andy Yan: > As patch 150696e2e3a4("Add GPIO pin index definition for rockchip pinctrl") > has been applied, now we can use these macros to describe the corresponding > gpio ranther than hard code numbers, this will make the dts easier to read >

Re: [PATCH] virtio-crypto: support crypto engine framework

On Tue, Dec 27, 2016 at 02:49:07PM +0800, Gonglei wrote: > crypto engine was introduced since 'commit 735d37b5424b ("crypto: engine > - Introduce the block request crypto engine framework")' which uses work > queue to realize the asynchronous processing for ablk_cipher and ahash. > > For

Re: [PATCH] virtio-crypto: support crypto engine framework

On Tue, Dec 27, 2016 at 02:49:07PM +0800, Gonglei wrote: > crypto engine was introduced since 'commit 735d37b5424b ("crypto: engine > - Introduce the block request crypto engine framework")' which uses work > queue to realize the asynchronous processing for ablk_cipher and ahash. > > For

Re: [BUG] ARM64: amlogic: gxbb: unhandled level 2 translation fault (11)

On 12/30/2016 10:44 AM, Neil Armstrong wrote: > On 12/30/2016 09:51 AM, Neil Armstrong wrote: >> On 12/29/2016 10:18 PM, Heinrich Schuchardt wrote: >>> On 12/29/2016 10:07 AM, Neil Armstrong wrote: On 12/24/2016 03:00 PM, Heinrich Schuchardt wrote: > When trying to run sddm on an

Re: [BUG] ARM64: amlogic: gxbb: unhandled level 2 translation fault (11)

On 12/30/2016 10:44 AM, Neil Armstrong wrote: > On 12/30/2016 09:51 AM, Neil Armstrong wrote: >> On 12/29/2016 10:18 PM, Heinrich Schuchardt wrote: >>> On 12/29/2016 10:07 AM, Neil Armstrong wrote: On 12/24/2016 03:00 PM, Heinrich Schuchardt wrote: > When trying to run sddm on an

Re: [PATCH v5 09/14] ACPI: platform: setup MSI domain for ACPI based platform device

Hi Rafael, On 2016/12/26 9:31, Hanjun Guo wrote: [cut] > > + if (pdevinfo->pre_add_cb) > + pdevinfo->pre_add_cb(>dev); > + -> because it looks like this might be done in acpi_platform_notify() for platform devices. >>> It works and I just simply add the code below:

Re: [PATCH v5 09/14] ACPI: platform: setup MSI domain for ACPI based platform device

Hi Rafael, On 2016/12/26 9:31, Hanjun Guo wrote: [cut] > > + if (pdevinfo->pre_add_cb) > + pdevinfo->pre_add_cb(>dev); > + -> because it looks like this might be done in acpi_platform_notify() for platform devices. >>> It works and I just simply add the code below:

Re: dmaengine: dw-dmac: Custom cyclic API (Why?)

++dw-dmac Maintainers On 30-12-2016 11:32, Jose Abreu wrote: > Hi All, > > > I am going to work with dw-dmac AHB controller and I wanted to > use SND_DMAENGINE_PCM. In order to use this, a standard DMA > driver with cyclic support is needed. I found out that dw-dmac is > capable of cyclic

Re: dmaengine: dw-dmac: Custom cyclic API (Why?)

++dw-dmac Maintainers On 30-12-2016 11:32, Jose Abreu wrote: > Hi All, > > > I am going to work with dw-dmac AHB controller and I wanted to > use SND_DMAENGINE_PCM. In order to use this, a standard DMA > driver with cyclic support is needed. I found out that dw-dmac is > capable of cyclic

Re: orinoco: Use shash instead of ahash for MIC calculations

Kalle Valo writes: > Andrew Lutomirski wrote: >> Eric Biggers pointed out that the orinoco driver pointed scatterlists >> at the stack. >> >> Fix it by switching from ahash to shash. The result should be >> simpler, faster, and more correct. >> >> Cc:

Re: orinoco: Use shash instead of ahash for MIC calculations

Kalle Valo writes: > Andrew Lutomirski wrote: >> Eric Biggers pointed out that the orinoco driver pointed scatterlists >> at the stack. >> >> Fix it by switching from ahash to shash. The result should be >> simpler, faster, and more correct. >> >> Cc: sta...@vger.kernel.org # 4.9 only >>

Re: [PATCH v2 4/8] PM / devfreq: exynos-ppmu: Show the registred device for ppmu device

2016-12-30 19:35 GMT+09:00 MyungJoo Ham : > On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: >> This patch just adds the simple log to show the PPMU device's registration >> during the kernel booting. >> >> Cc: Kukjin Kim >>

Re: [PATCH v2 4/8] PM / devfreq: exynos-ppmu: Show the registred device for ppmu device

2016-12-30 19:35 GMT+09:00 MyungJoo Ham : > On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: >> This patch just adds the simple log to show the PPMU device's registration >> during the kernel booting. >> >> Cc: Kukjin Kim >> Cc: Krzysztof Kozlowski >> Cc: Javier Martinez Canillas >> Cc:

[PATCH] PM / domains: Fix 'may be used uninitialized' build warning

This patch fixes the following gcc warning: drivers/base/power/domain.c: In function ‘genpd_runtime_resume’: drivers/base/power/domain.c:642:14: warning: ‘time_start’ may be used uninitialized in this function [-Wmaybe-uninitialized] elapsed_ns = ktime_to_ns(ktime_sub(ktime_get(), time_start)

[PATCH] PM / domains: Fix 'may be used uninitialized' build warning

This patch fixes the following gcc warning: drivers/base/power/domain.c: In function ‘genpd_runtime_resume’: drivers/base/power/domain.c:642:14: warning: ‘time_start’ may be used uninitialized in this function [-Wmaybe-uninitialized] elapsed_ns = ktime_to_ns(ktime_sub(ktime_get(), time_start)

[RFC v4 3/6] sched/deadline: fix the update of the total -deadline utilization

From: Luca Abeni Now that the inactive timer can be armed to fire at the 0-lag time, it is possible to use inactive_task_timer() to update the total -deadline utilization (dl_b->total_bw) at the correct time, fixing dl_overflow() and __setparam_dl(). Signed-off-by: Luca

[RFC v4 3/6] sched/deadline: fix the update of the total -deadline utilization

From: Luca Abeni Now that the inactive timer can be armed to fire at the 0-lag time, it is possible to use inactive_task_timer() to update the total -deadline utilization (dl_b->total_bw) at the correct time, fixing dl_overflow() and __setparam_dl(). Signed-off-by: Luca Abeni ---

[RFC v4 6/6] sched/deadline: make GRUB a task's flag

From: Luca Abeni Signed-off-by: Luca Abeni --- include/uapi/linux/sched.h | 1 + kernel/sched/core.c| 3 ++- kernel/sched/deadline.c| 3 ++- 3 files changed, 5 insertions(+), 2 deletions(-) diff --git a/include/uapi/linux/sched.h

[RFC v4 2/6] sched/deadline: improve the tracking of active utilization

From: Luca Abeni This patch implements a more theoretically sound algorithm for tracking active utilization: instead of decreasing it when a task blocks, use a timer (the "inactive timer", named after the "Inactive" task state of the GRUB algorithm) to decrease the active

Re: orinoco: Use shash instead of ahash for MIC calculations

Andrew Lutomirski wrote: > Eric Biggers pointed out that the orinoco driver pointed scatterlists > at the stack. > > Fix it by switching from ahash to shash. The result should be > simpler, faster, and more correct. > > Cc: sta...@vger.kernel.org # 4.9 only > Reported-by: Eric

[RFC v4 1/6] sched/deadline: track the active utilization

From: Luca Abeni Active utilization is defined as the total utilization of active (TASK_RUNNING) tasks queued on a runqueue. Hence, it is increased when a task wakes up and is decreased when a task blocks. When a task is migrated from CPUi to CPUj, immediately subtract the

[RFC v4 0/6] CPU reclaiming for SCHED_DEADLINE

From: Luca Abeni Hi all, here is a new version of the patchset implementing CPU reclaiming (using the GRUB algorithm[1]) for SCHED_DEADLINE. Basically, this feature allows SCHED_DEADLINE tasks to consume more than their reserved runtime, up to a maximum fraction of the CPU

[RFC v4 6/6] sched/deadline: make GRUB a task's flag

From: Luca Abeni Signed-off-by: Luca Abeni --- include/uapi/linux/sched.h | 1 + kernel/sched/core.c| 3 ++- kernel/sched/deadline.c| 3 ++- 3 files changed, 5 insertions(+), 2 deletions(-) diff --git a/include/uapi/linux/sched.h b/include/uapi/linux/sched.h index 5f0fe01..e2a6c7b

[RFC v4 2/6] sched/deadline: improve the tracking of active utilization

From: Luca Abeni This patch implements a more theoretically sound algorithm for tracking active utilization: instead of decreasing it when a task blocks, use a timer (the "inactive timer", named after the "Inactive" task state of the GRUB algorithm) to decrease the active utilization at the so

Re: orinoco: Use shash instead of ahash for MIC calculations

Andrew Lutomirski wrote: > Eric Biggers pointed out that the orinoco driver pointed scatterlists > at the stack. > > Fix it by switching from ahash to shash. The result should be > simpler, faster, and more correct. > > Cc: sta...@vger.kernel.org # 4.9 only > Reported-by: Eric Biggers >

<    1   2   3   4   5   6   7   >