Re: [PATCH] doc: ABI: vdso: update parse_vdso.c reference

On Wed, 8 Mar 2017 21:50:31 +0200 Baruch Siach wrote: > Since commit f9b6b0ef603 ("selftests: move vDSO tests from > Documentation/vDSO") > parse_vdso.c moved under selftests. Update the reference to match. Applied to the docs tree, thanks. jon

Re: [PATCH] doc: ABI: vdso: update parse_vdso.c reference

On Wed, 8 Mar 2017 21:50:31 +0200 Baruch Siach wrote: > Since commit f9b6b0ef603 ("selftests: move vDSO tests from > Documentation/vDSO") > parse_vdso.c moved under selftests. Update the reference to match. Applied to the docs tree, thanks. jon

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

On Mon, 13 Mar 2017 23:59:57 +0100 "Rafael J. Wysocki" wrote: > Well, to be honest, I downloaded the previous iteration from Patchwork and > I though it would apply, so I didn't check. Sorry about that. > > The one below applies for me with "git am" on top of 4.11-rc2.

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

On Mon, 13 Mar 2017 23:59:57 +0100 "Rafael J. Wysocki" wrote: > Well, to be honest, I downloaded the previous iteration from Patchwork and > I though it would apply, so I didn't check. Sorry about that. > > The one below applies for me with "git am" on top of 4.11-rc2. Works for me too. Now

Re: [PATCH net-next 4/4] net-next: dsa: add dsa support for Mediatek MT7530 switch

> +static int > +mt7530_setup(struct dsa_switch *ds) > +{ > + struct mt7530_priv *priv = ds->priv; > + int ret, i, phy_mode; > + u8 cpup_mask = 0; > + u32 id, val; > + struct regmap *regmap; > + > + /* Make sure that cpu port specfied on the dt is appropriate */ > + if

Re: [PATCH net-next 4/4] net-next: dsa: add dsa support for Mediatek MT7530 switch

> +static int > +mt7530_setup(struct dsa_switch *ds) > +{ > + struct mt7530_priv *priv = ds->priv; > + int ret, i, phy_mode; > + u8 cpup_mask = 0; > + u32 id, val; > + struct regmap *regmap; > + > + /* Make sure that cpu port specfied on the dt is appropriate */ > + if

[RFC 1/2] fanotify: new event FAN_MODIFY_DIR

Fanotify currently does not report directory modification events (rename, unlink, etc.). But these events are essential for about half of concievable fanotify use cases, especially: - file system indexers / desktop search tools - file synchronization tools (like Dropbox, Nextcloud, etc.),

[RFC 1/2] fanotify: new event FAN_MODIFY_DIR

Fanotify currently does not report directory modification events (rename, unlink, etc.). But these events are essential for about half of concievable fanotify use cases, especially: - file system indexers / desktop search tools - file synchronization tools (like Dropbox, Nextcloud, etc.),

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

On Monday, March 13, 2017 04:54:38 PM Jonathan Corbet wrote: > On Thu, 09 Mar 2017 16:28:32 +0100 > "Rafael J. Wysocki" wrote: > > > The user/admin documentation of cpufreq is badly outdated. It > > conains stale and/or inaccurate information along with things > > that are

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

On Monday, March 13, 2017 04:54:38 PM Jonathan Corbet wrote: > On Thu, 09 Mar 2017 16:28:32 +0100 > "Rafael J. Wysocki" wrote: > > > The user/admin documentation of cpufreq is badly outdated. It > > conains stale and/or inaccurate information along with things > > that are not particularly

[tip:x86/urgent] x86/kasan: Fix boot with KASAN=y and PROFILE_ANNOTATED_BRANCHES=y

Commit-ID: be3606ff739d1c1be36389f8737c577ad87e1f57 Gitweb: http://git.kernel.org/tip/be3606ff739d1c1be36389f8737c577ad87e1f57 Author: Andrey Ryabinin AuthorDate: Mon, 13 Mar 2017 19:33:37 +0300 Committer: Thomas Gleixner CommitDate: Tue, 14

[tip:x86/urgent] x86/kasan: Fix boot with KASAN=y and PROFILE_ANNOTATED_BRANCHES=y

Commit-ID: be3606ff739d1c1be36389f8737c577ad87e1f57 Gitweb: http://git.kernel.org/tip/be3606ff739d1c1be36389f8737c577ad87e1f57 Author: Andrey Ryabinin AuthorDate: Mon, 13 Mar 2017 19:33:37 +0300 Committer: Thomas Gleixner CommitDate: Tue, 14 Mar 2017 00:00:55 +0100 x86/kasan: Fix boot

[PATCH 1/1] Drivers: hv: vmbus: Don't leak channel ids

From: K. Y. Srinivasan If we cannot allocate memory for the channel, free the relid associated with the channel. Signed-off-by: K. Y. Srinivasan Cc: --- drivers/hv/channel_mgmt.c |1 + 1 files changed, 1 insertions(+), 0

[PATCH 1/1] Drivers: hv: vmbus: Don't leak channel ids

From: K. Y. Srinivasan If we cannot allocate memory for the channel, free the relid associated with the channel. Signed-off-by: K. Y. Srinivasan Cc: --- drivers/hv/channel_mgmt.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/hv/channel_mgmt.c

Re: [PATCH net-next] net: dsa: mv88e6xxx: debug ATU Age Time

On Mon, Mar 13, 2017 at 03:42:36PM -0700, Florian Fainelli wrote: > On 03/13/2017 03:39 PM, Andrew Lunn wrote: > > On Mon, Mar 13, 2017 at 03:20:43PM -0400, Vivien Didelot wrote: > >> The ATU ageing time value programmed in the switch is rounded up to the > >> nearest multiple of its coefficient

Re: [PATCH net-next] net: dsa: mv88e6xxx: debug ATU Age Time

On Mon, Mar 13, 2017 at 03:42:36PM -0700, Florian Fainelli wrote: > On 03/13/2017 03:39 PM, Andrew Lunn wrote: > > On Mon, Mar 13, 2017 at 03:20:43PM -0400, Vivien Didelot wrote: > >> The ATU ageing time value programmed in the switch is rounded up to the > >> nearest multiple of its coefficient

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

On Thu, 09 Mar 2017 16:28:32 +0100 "Rafael J. Wysocki" wrote: > 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

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

On Thu, 09 Mar 2017 16:28:32 +0100 "Rafael J. Wysocki" wrote: > 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

Re: [PATCH net-next] net: dsa: mv88e6xxx: set out of range ageing time

On Mon, Mar 13, 2017 at 03:19:32PM -0400, Vivien Didelot wrote: > The minimum and maximum value of the ATU Age Time varies depending on > the switch model. The current code returns -ERANGE for out-of-range > values, and makes switchdev commit phase fail with this stacktrace: Hi Vivien I took a

Re: [PATCH net-next] net: dsa: mv88e6xxx: set out of range ageing time

On Mon, Mar 13, 2017 at 03:19:32PM -0400, Vivien Didelot wrote: > The minimum and maximum value of the ATU Age Time varies depending on > the switch model. The current code returns -ERANGE for out-of-range > values, and makes switchdev commit phase fail with this stacktrace: Hi Vivien I took a

Re: [PATCH][RFC v4] ACPI throttling: Disable the MSR T-state if enabled after resumed

On Friday, February 17, 2017 04:27:30 PM Chen Yu wrote: > Previously a bug was reported that on certain Broadwell > platform, after resumed from S3, the CPU is running at > an anomalously low speed, due to the BIOS has enabled the > MSR throttling across S3. The solution to this was to introduce >

Re: [PATCH][RFC v4] ACPI throttling: Disable the MSR T-state if enabled after resumed

On Friday, February 17, 2017 04:27:30 PM Chen Yu wrote: > Previously a bug was reported that on certain Broadwell > platform, after resumed from S3, the CPU is running at > an anomalously low speed, due to the BIOS has enabled the > MSR throttling across S3. The solution to this was to introduce >

Re: [PATCH net-next] net: dsa: mv88e6xxx: debug ATU Age Time

On 03/13/2017 03:39 PM, Andrew Lunn wrote: > On Mon, Mar 13, 2017 at 03:20:43PM -0400, Vivien Didelot wrote: >> The ATU ageing time value programmed in the switch is rounded up to the >> nearest multiple of its coefficient (variable depending on the model.) >> >> Add a debug message to inform the

Re: [PATCH net-next] net: dsa: mv88e6xxx: debug ATU Age Time

On 03/13/2017 03:39 PM, Andrew Lunn wrote: > On Mon, Mar 13, 2017 at 03:20:43PM -0400, Vivien Didelot wrote: >> The ATU ageing time value programmed in the switch is rounded up to the >> nearest multiple of its coefficient (variable depending on the model.) >> >> Add a debug message to inform the

Re: [PATCH net-next] net: dsa: mv88e6xxx: debug ATU Age Time

On Mon, Mar 13, 2017 at 03:20:43PM -0400, Vivien Didelot wrote: > The ATU ageing time value programmed in the switch is rounded up to the > nearest multiple of its coefficient (variable depending on the model.) > > Add a debug message to inform the user about the exact programmed value. > > On

Re: [PATCH net-next] net: dsa: mv88e6xxx: debug ATU Age Time

On Mon, Mar 13, 2017 at 03:20:43PM -0400, Vivien Didelot wrote: > The ATU ageing time value programmed in the switch is rounded up to the > nearest multiple of its coefficient (variable depending on the model.) > > Add a debug message to inform the user about the exact programmed value. > > On

Re: [patch 1/7] tty_port: allow a port to be opened with a tty that has no file handle

On Tue, Mar 14, 2017 at 06:12:47AM +0800, Greg Kroah-Hartman wrote: > On Mon, Mar 13, 2017 at 10:05:52PM +, okash.khaw...@gmail.com wrote: > > Allow access to TTY device from kernel. This is based on Alan Cox's patch > > (http://www.mail-archive.com/linux-kernel at > >

Re: [patch 1/7] tty_port: allow a port to be opened with a tty that has no file handle

On Tue, Mar 14, 2017 at 06:12:47AM +0800, Greg Kroah-Hartman wrote: > On Mon, Mar 13, 2017 at 10:05:52PM +, okash.khaw...@gmail.com wrote: > > Allow access to TTY device from kernel. This is based on Alan Cox's patch > > (http://www.mail-archive.com/linux-kernel at > >

Re: [PATCH 4.10 00/75] 4.10.3-stable review

On Mon, Mar 13, 2017 at 04:43:09PM +0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.10.3 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.10 00/75] 4.10.3-stable review

On Mon, Mar 13, 2017 at 04:43:09PM +0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.10.3 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.9 00/63] 4.9.15-stable review

On Mon, Mar 13, 2017 at 04:38:47PM +0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.15 release. > There are 63 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.9 00/63] 4.9.15-stable review

On Mon, Mar 13, 2017 at 04:38:47PM +0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.15 release. > There are 63 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.4 00/36] 4.4.54-stable review

On Mon, Mar 13, 2017 at 04:39:00PM +0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.54 release. > There are 36 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 4.4 00/36] 4.4.54-stable review

On Mon, Mar 13, 2017 at 04:39:00PM +0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.54 release. > There are 36 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [Xen-devel] [PATCH 0/7] Xen transport for 9pfs frontend driver

On Thu, 9 Mar 2017, Roger Pau Monné wrote: > On Tue, Mar 07, 2017 at 10:27:05AM -0800, Stefano Stabellini wrote: > > On Tue, 7 Mar 2017, Roger Pau Monné wrote: > > > On Mon, Mar 06, 2017 at 12:00:41PM -0800, Stefano Stabellini wrote: > > > > Hi all, > > > > > > > > This patch series implements a

Re: [Xen-devel] [PATCH 0/7] Xen transport for 9pfs frontend driver

On Thu, 9 Mar 2017, Roger Pau Monné wrote: > On Tue, Mar 07, 2017 at 10:27:05AM -0800, Stefano Stabellini wrote: > > On Tue, 7 Mar 2017, Roger Pau Monné wrote: > > > On Mon, Mar 06, 2017 at 12:00:41PM -0800, Stefano Stabellini wrote: > > > > Hi all, > > > > > > > > This patch series implements a

Re: [PATCH] usbnet: smsc95xx: Reduce logging noise

From: Guenter Roeck Date: Fri, 10 Mar 2017 17:45:21 -0800 > An insert/remove stress test generated the following log message sequence. ... > Use netdev_dbg() instead of netdev_warn() for the repeating messages > to reduce logging noise. > > Signed-off-by: Guenter Roeck

Re: [PATCH] usbnet: smsc95xx: Reduce logging noise

From: Guenter Roeck Date: Fri, 10 Mar 2017 17:45:21 -0800 > An insert/remove stress test generated the following log message sequence. ... > Use netdev_dbg() instead of netdev_warn() for the repeating messages > to reduce logging noise. > > Signed-off-by: Guenter Roeck The problem I have with

Re: [PATCH v2 4/7] xen/9pfs: connect to the backend

On Thu, 9 Mar 2017, Boris Ostrovsky wrote: > > + > > +static int xen_9pfs_front_alloc_dataring(struct xenbus_device *dev, > > + struct xen_9pfs_dataring *ring) > > +{ > > + int i; > > + int ret = -ENOMEM; > > + > > + init_waitqueue_head(>wq); > > + spin_lock_init(>lock); > > +

Re: [PATCH v2 4/7] xen/9pfs: connect to the backend

On Thu, 9 Mar 2017, Boris Ostrovsky wrote: > > + > > +static int xen_9pfs_front_alloc_dataring(struct xenbus_device *dev, > > + struct xen_9pfs_dataring *ring) > > +{ > > + int i; > > + int ret = -ENOMEM; > > + > > + init_waitqueue_head(>wq); > > + spin_lock_init(>lock); > > +

[PATCH v4] statx: optimize copy of struct statx to userspace

From: Eric Biggers I found that statx() was significantly slower than stat(). As a microbenchmark, I compared 10,000,000 invocations of fstat() on a tmpfs file to the same with statx() passed a NULL path: $ time ./stat_benchmark real0m1.464s

[PATCH v4] statx: optimize copy of struct statx to userspace

From: Eric Biggers I found that statx() was significantly slower than stat(). As a microbenchmark, I compared 10,000,000 invocations of fstat() on a tmpfs file to the same with statx() passed a NULL path: $ time ./stat_benchmark real0m1.464s user0m0.275s

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Hello, Greg KH, on mar. 14 mars 2017 06:14:04 +0800, wrote: > On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > > This patchset introduces a TTY-based way for the synths to communicate > > with devices as an alternate for direct serial comms used by the synths > > at the

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Hello, Greg KH, on mar. 14 mars 2017 06:14:04 +0800, wrote: > On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > > This patchset introduces a TTY-based way for the synths to communicate > > with devices as an alternate for direct serial comms used by the synths > > at the

Re: [PATCH] net: usb: asix88179_178a: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 12 Mar 2017 18:02:36 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: usb: asix88179_178a: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 12 Mar 2017 18:02:36 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: [PATCH] net: usb: catc: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 12 Mar 2017 22:08:26 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: usb: catc: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 12 Mar 2017 22:08:26 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: [PATCH 3/3] staging: dngc: ch->ch_bd is already assigned to bd variable

On Sun, Mar 12, 2017 at 11:47:28PM +0900, Daeseok Youn wrote: > The bd variable in dgnc_tty_digiseta() is assigned with > ch->ch_bd but it is not used in this function except checking NULL. > The ch->ch_bd could be replaced with bd variable in dgnc_tty_digiseta() > > Signed-off-by: Daeseok Youn

Re: [PATCH] net: usb: r8152: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 12 Mar 2017 22:41:58 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH 3/3] staging: dngc: ch->ch_bd is already assigned to bd variable

On Sun, Mar 12, 2017 at 11:47:28PM +0900, Daeseok Youn wrote: > The bd variable in dgnc_tty_digiseta() is assigned with > ch->ch_bd but it is not used in this function except checking NULL. > The ch->ch_bd could be replaced with bd variable in dgnc_tty_digiseta() > > Signed-off-by: Daeseok Youn

Re: [PATCH] net: usb: r8152: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 12 Mar 2017 22:41:58 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: [PATCH] net: net_netdev: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 9 Mar 2017 23:10:13 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: net_netdev: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Thu, 9 Mar 2017 23:10:13 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: [PATCH v2] net: tun: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sat, 11 Mar 2017 22:03:50 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes > --- > Changelog: > v2: > - Finaly, I've found

Re: [PATCH v2] net: tun: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sat, 11 Mar 2017 22:03:50 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes > --- > Changelog: > v2: > - Finaly, I've found the hardware and do basic test ;) >

Re: [PATCH 3/4] arm: dts: imx: Add iMX6Q-based Kontron SMARC-sAMX6i module

On Tue, Feb 28, 2017 at 6:20 PM, Russell King - ARM Linux wrote: > On Tue, Feb 28, 2017 at 05:49:57PM -0600, Rob Herring wrote: >> On Tue, Feb 28, 2017 at 5:10 PM, Russell King - ARM Linux >> wrote: >> > On Tue, Feb 28, 2017 at 05:06:02PM -0600, Rob

Re: [PATCH 3/4] arm: dts: imx: Add iMX6Q-based Kontron SMARC-sAMX6i module

On Tue, Feb 28, 2017 at 6:20 PM, Russell King - ARM Linux wrote: > On Tue, Feb 28, 2017 at 05:49:57PM -0600, Rob Herring wrote: >> On Tue, Feb 28, 2017 at 5:10 PM, Russell King - ARM Linux >> wrote: >> > On Tue, Feb 28, 2017 at 05:06:02PM -0600, Rob Herring wrote: >> >> On Sun, Feb 19, 2017 at

[PATCH v2] mm: fix condition for throttle_direct_reclaim

Recently kswapd has been modified to give up after MAX_RECLAIM_RETRIES number of unsucessful iterations. Before going to sleep, kswapd thread will unconditionally wakeup all threads sleeping on pfmemalloc_wait. However the awoken threads will recheck the watermarks and wake the kswapd thread and

[PATCH v2] mm: fix condition for throttle_direct_reclaim

Recently kswapd has been modified to give up after MAX_RECLAIM_RETRIES number of unsucessful iterations. Before going to sleep, kswapd thread will unconditionally wakeup all threads sleeping on pfmemalloc_wait. However the awoken threads will recheck the watermarks and wake the kswapd thread and

Re: [Outreachy kernel] [PATCH v2] staging: sm750fb: Improved code readability

On Mon, 13 Mar 2017, Arushi Singhal wrote: > New variables are added to make the code more readable. > > Signed-off-by: Arushi Singhal > --- > changes in v2 > - removed the error. > > drivers/staging/sm750fb/ddk750_mode.c | 103 >

Re: [Outreachy kernel] [PATCH v2] staging: sm750fb: Improved code readability

On Mon, 13 Mar 2017, Arushi Singhal wrote: > New variables are added to make the code more readable. > > Signed-off-by: Arushi Singhal > --- > changes in v2 > - removed the error. > > drivers/staging/sm750fb/ddk750_mode.c | 103 > -- > 1 file changed, 49

Re: [PATCH 5/7] ath9k: of: Use the clk API to get the reference clock rate

On 03/13/2017 10:05 PM, Alban wrote: @@ -573,6 +575,12 @@ static int ath9k_of_init(struct ath_softc *sc) ath_dbg(common, CONFIG, "parsing configuration from OF node\n"); + clk = clk_get(sc->dev, "ref"); + if (!IS_ERR(clk)) { + ah->is_clk_25mhz =

Re: [PATCH 5/7] ath9k: of: Use the clk API to get the reference clock rate

On 03/13/2017 10:05 PM, Alban wrote: @@ -573,6 +575,12 @@ static int ath9k_of_init(struct ath_softc *sc) ath_dbg(common, CONFIG, "parsing configuration from OF node\n"); + clk = clk_get(sc->dev, "ref"); + if (!IS_ERR(clk)) { + ah->is_clk_25mhz =

Re: [PATCH 3/7] ath9k: Add support for reading the EEPROM data using the nvmem API

On 03/13/2017 10:05 PM, Alban wrote: @@ -654,6 +656,25 @@ static int ath9k_init_softc(u16 devid, struct ath_softc *sc, if (ret) return ret; + /* If the EEPROM hasn't been retrieved via firmware request +* use the nvmem API insted. +*/ + if

Re: [PATCH 3/7] ath9k: Add support for reading the EEPROM data using the nvmem API

On 03/13/2017 10:05 PM, Alban wrote: @@ -654,6 +656,25 @@ static int ath9k_init_softc(u16 devid, struct ath_softc *sc, if (ret) return ret; + /* If the EEPROM hasn't been retrieved via firmware request +* use the nvmem API insted. +*/ + if

Re: [patch 0/7] staging: speakup: introduce tty-based comms

On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > Hi, > > This patchset introduces a TTY-based way for the synths to communicate > with devices as an alternate for direct serial comms used by the synths > at the moment. It then migrates some of the synths to the TTY-based

Re: [patch 0/7] staging: speakup: introduce tty-based comms

On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > Hi, > > This patchset introduces a TTY-based way for the synths to communicate > with devices as an alternate for direct serial comms used by the synths > at the moment. It then migrates some of the synths to the TTY-based

Re: [patch 1/7] tty_port: allow a port to be opened with a tty that has no file handle

On Mon, Mar 13, 2017 at 10:05:52PM +, okash.khaw...@gmail.com wrote: > Allow access to TTY device from kernel. This is based on Alan Cox's patch > (http://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1215095.html), > with description quoted below. > > "tty_port: allow a port to be

Re: [patch 1/7] tty_port: allow a port to be opened with a tty that has no file handle

On Mon, Mar 13, 2017 at 10:05:52PM +, okash.khaw...@gmail.com wrote: > Allow access to TTY device from kernel. This is based on Alan Cox's patch > (http://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1215095.html), > with description quoted below. > > "tty_port: allow a port to be

RE: [HMM v17 09/14] mm/hmm/mirror: mirror process address space on device with HMM helpers

+/* + * struct hmm_mirror_ops - HMM mirror device operations callback + * + * @update: callback to update range on a device */ struct +hmm_mirror_ops { + /* update() - update virtual address range of memory +* +* @mirror: pointer to struct hmm_mirror +* @update:

RE: [HMM v17 09/14] mm/hmm/mirror: mirror process address space on device with HMM helpers

+/* + * struct hmm_mirror_ops - HMM mirror device operations callback + * + * @update: callback to update range on a device */ struct +hmm_mirror_ops { + /* update() - update virtual address range of memory +* +* @mirror: pointer to struct hmm_mirror +* @update:

[patch 4/7] staging: speakup: move spk_stop_serial_interrupt into synth-specific release function

This moves call to spk_stop_serial_interrupt() function out of synth_release() and into release() method of specific spk_synth instances. This is because a TTY-based synth implementation wouldn't need spk_stop_serial_interrupt() call. Moving it into each synth's release() method gives the decision

[patch 4/7] staging: speakup: move spk_stop_serial_interrupt into synth-specific release function

This moves call to spk_stop_serial_interrupt() function out of synth_release() and into release() method of specific spk_synth instances. This is because a TTY-based synth implementation wouldn't need spk_stop_serial_interrupt() call. Moving it into each synth's release() method gives the decision

[patch 5/7] staging: speakup: move those functions which do outgoing serial comms, into serialio.c

This moves spk_synth_immediate and spk_serial_synth_probe functions into serialio.c. These functions do outgoing serial comms. The move is a step towards collecting all serial comms in serialio.c. This also renames spk_synth_immediate to spk_serial_synth_immediate. Code inside those functions has

[patch 7/7] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio

This changes the above five synths to TTY-based comms. They were chosen as a first pass because their serial comms are straightforward, i.e. they don't use serial input and don't do internal port knocking. Signed-off-by: Okash Khawaja Reviewed-by: Samuel Thibault

[patch 6/7] staging: speakup: add tty-based comms functions

This adds spk_ttyio.c file. It contains a set of functions which implement those methods in spk_synth struct which relate to sending bytes out using serial comms. Implementations in this file perform the same function but using TTY subsystem instead. Currently synths access serial ports, directly

[patch 5/7] staging: speakup: move those functions which do outgoing serial comms, into serialio.c

This moves spk_synth_immediate and spk_serial_synth_probe functions into serialio.c. These functions do outgoing serial comms. The move is a step towards collecting all serial comms in serialio.c. This also renames spk_synth_immediate to spk_serial_synth_immediate. Code inside those functions has

[patch 7/7] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio

This changes the above five synths to TTY-based comms. They were chosen as a first pass because their serial comms are straightforward, i.e. they don't use serial input and don't do internal port knocking. Signed-off-by: Okash Khawaja Reviewed-by: Samuel Thibault Index:

[patch 6/7] staging: speakup: add tty-based comms functions

This adds spk_ttyio.c file. It contains a set of functions which implement those methods in spk_synth struct which relate to sending bytes out using serial comms. Implementations in this file perform the same function but using TTY subsystem instead. Currently synths access serial ports, directly

[patch 0/7] staging: speakup: introduce tty-based comms

Hi, This patchset introduces a TTY-based way for the synths to communicate with devices as an alternate for direct serial comms used by the synths at the moment. It then migrates some of the synths to the TTY-based comms. Synths migrated in this patchset are dummy, acntsa, bns and txprt. As

[patch 1/7] tty_port: allow a port to be opened with a tty that has no file handle

Allow access to TTY device from kernel. This is based on Alan Cox's patch (http://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1215095.html), with description quoted below. "tty_port: allow a port to be opened with a tty that has no file handle Let us create tty objects entirely in

[patch 0/7] staging: speakup: introduce tty-based comms

Hi, This patchset introduces a TTY-based way for the synths to communicate with devices as an alternate for direct serial comms used by the synths at the moment. It then migrates some of the synths to the TTY-based comms. Synths migrated in this patchset are dummy, acntsa, bns and txprt. As

[patch 1/7] tty_port: allow a port to be opened with a tty that has no file handle

Allow access to TTY device from kernel. This is based on Alan Cox's patch (http://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1215095.html), with description quoted below. "tty_port: allow a port to be opened with a tty that has no file handle Let us create tty objects entirely in

[patch 2/7] staging: speakup: spk_serial_out and spk_wait_for_xmitr to take synth arg

These two functions are always called from a context where spk_synth instance is available. They also use the spk_synth instance but instead of taking it as an argument, they rely on a global spk_synth instance inside synth.c which points to the same synth as the one being passed in as argument.

[patch 3/7] staging: serial: add spk_io_ops struct to spk_synth

This patch adds spk_io_ops struct which contain those methods whose job is to communicate with synth device. Currently, all comms with external synth device use raw serial i/o. Starting with this patch set, an alternative tty-based way of communication is being introduced. The idea is to group all

[patch 2/7] staging: speakup: spk_serial_out and spk_wait_for_xmitr to take synth arg

These two functions are always called from a context where spk_synth instance is available. They also use the spk_synth instance but instead of taking it as an argument, they rely on a global spk_synth instance inside synth.c which points to the same synth as the one being passed in as argument.

[patch 3/7] staging: serial: add spk_io_ops struct to spk_synth

This patch adds spk_io_ops struct which contain those methods whose job is to communicate with synth device. Currently, all comms with external synth device use raw serial i/o. Starting with this patch set, an alternative tty-based way of communication is being introduced. The idea is to group all

Re: [PATCH v3 0/2] staging: checkpatch cleanups

On Tue, Mar 14, 2017 at 01:49:52AM +0530, Arushi Singhal wrote: > Improve readability by fixing multiple checkpatch.pl > issues in drivers. > > Arushi Singhal (2): > staging: speakup: identation should use tabs > staging: dvb-frontends: removed code in comments. What changed from v2?

Re: [PATCH] vfio pci: kernel support of error recovery only for non fatal error

On Mon, 27 Feb 2017 15:28:43 +0800 Cao jin wrote: > 0. What happens now (PCIE AER only) >Fatal errors cause a link reset. >Non fatal errors don't. >All errors stop the VM eventually, but not immediately >because it's detected and reported asynchronously.

Re: [PATCH v3 0/2] staging: checkpatch cleanups

On Tue, Mar 14, 2017 at 01:49:52AM +0530, Arushi Singhal wrote: > Improve readability by fixing multiple checkpatch.pl > issues in drivers. > > Arushi Singhal (2): > staging: speakup: identation should use tabs > staging: dvb-frontends: removed code in comments. What changed from v2?

Re: [PATCH] vfio pci: kernel support of error recovery only for non fatal error

On Mon, 27 Feb 2017 15:28:43 +0800 Cao jin wrote: > 0. What happens now (PCIE AER only) >Fatal errors cause a link reset. >Non fatal errors don't. >All errors stop the VM eventually, but not immediately >because it's detected and reported asynchronously. >Interrupts are

Re: [PATCH v3 1/2] staging: speakup: identation should use tabs

On Tue, Mar 14, 2017 at 01:49:54AM +0530, Arushi Singhal wrote: > Indentation should always use tabs and never spaces. > > Signed-off-by: Arushi Singhal > --- > drivers/staging/speakup/speakup_dtlk.h | 10 +- > 1 file changed, 5 insertions(+), 5

Re: [PATCH v3 1/2] staging: speakup: identation should use tabs

On Tue, Mar 14, 2017 at 01:49:54AM +0530, Arushi Singhal wrote: > Indentation should always use tabs and never spaces. > > Signed-off-by: Arushi Singhal > --- > drivers/staging/speakup/speakup_dtlk.h | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) What changed from v2?

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On 03/13/2017 02:29 PM, Rob Clark wrote: > On Mon, Mar 13, 2017 at 5:09 PM, Laura Abbott wrote: >>> Hm, we might want to expose all the heaps as individual >>> /dev/ion_$heapname nodes? Should we do this from the start, since >>> we're massively revamping the uapi anyway (imo

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On 03/13/2017 02:29 PM, Rob Clark wrote: > On Mon, Mar 13, 2017 at 5:09 PM, Laura Abbott wrote: >>> Hm, we might want to expose all the heaps as individual >>> /dev/ion_$heapname nodes? Should we do this from the start, since >>> we're massively revamping the uapi anyway (imo not needed, current

[PATCH 5/5] fpga-region: separate out common code from dt specific code

FPGA region is a layer above the FPGA manager and FPGA bridge frameworks. Currently, FPGA region is dependent on device tree. This commit separates the device tree specific code from the common code, separating fpga-region.c into fpga-region.c, of-fpga-region.c, and fpga-region.h. Functons

[PATCH 5/5] fpga-region: separate out common code from dt specific code

FPGA region is a layer above the FPGA manager and FPGA bridge frameworks. Currently, FPGA region is dependent on device tree. This commit separates the device tree specific code from the common code, separating fpga-region.c into fpga-region.c, of-fpga-region.c, and fpga-region.h. Functons

[PATCH 4/5] fpga-mgr: separate getting/locking FPGA manager

Add fpga_mgr_lock/unlock functions that get a mutex for exclusive use. of_fpga_mgr_get, fpga_mgr_get, and fpga_mgr_put no longer lock the FPGA manager mutex. This makes it more straightforward to save a reference to a FPGA manager and only attempting to lock it when programming the FPGA.

[PATCH 4/5] fpga-mgr: separate getting/locking FPGA manager

Add fpga_mgr_lock/unlock functions that get a mutex for exclusive use. of_fpga_mgr_get, fpga_mgr_get, and fpga_mgr_put no longer lock the FPGA manager mutex. This makes it more straightforward to save a reference to a FPGA manager and only attempting to lock it when programming the FPGA.

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