[PATCH] staging: dgnc: re-arrange functions for removing forward declarations

Re-arrange the functions for removing forward declarations in dgnc_driver.c Signed-off-by: Daeseok Youn --- I've checked the object size of dgnc_driver.c before and after. It has same size after re-arranging functions. drivers/staging/dgnc/dgnc_driver.c | 533

[PATCH] staging: dgnc: re-arrange functions for removing forward declarations

Re-arrange the functions for removing forward declarations in dgnc_driver.c Signed-off-by: Daeseok Youn --- I've checked the object size of dgnc_driver.c before and after. It has same size after re-arranging functions. drivers/staging/dgnc/dgnc_driver.c | 533

Re: BYD TouchPad driver (4.8.1) misdetects a Logitech mouse

On Friday 11 November 2016, Eric Wong wrote: > Sorry for the late response, forwarding to Dmitry and linux-input. > I haven't dealt with input in years... > > Michael Shell wrote: > > Not a big deal, but something nonetheless ... > > > > I recently upgraded my kernel from

Re: BYD TouchPad driver (4.8.1) misdetects a Logitech mouse

On Friday 11 November 2016, Eric Wong wrote: > Sorry for the late response, forwarding to Dmitry and linux-input. > I haven't dealt with input in years... > > Michael Shell wrote: > > Not a big deal, but something nonetheless ... > > > > I recently upgraded my kernel from 4.3 to 4.8.1 (this is a

Re: [PATCH v4 1/5] arm64: perf: Basic uncore counter support for Cavium ThunderX SOC

On Thu, Nov 10, 2016 at 04:54:06PM +, Mark Rutland wrote: > > +/* > > + * Some notes about the various counters supported by this "uncore" PMU > > + * and the design: > > + * > > + * All counters are 64 bit long. > > + * There are no overflow interrupts. > > + * Counters are summarized per

Re: [PATCH v4 1/5] arm64: perf: Basic uncore counter support for Cavium ThunderX SOC

On Thu, Nov 10, 2016 at 04:54:06PM +, Mark Rutland wrote: > > +/* > > + * Some notes about the various counters supported by this "uncore" PMU > > + * and the design: > > + * > > + * All counters are 64 bit long. > > + * There are no overflow interrupts. > > + * Counters are summarized per

Re: [PATCH v5 6/8] Documentation: bindings: add compatible specific to legacy SCPI protocol

On 10/11/16 19:03, Olof Johansson wrote: On Thu, Nov 10, 2016 at 6:34 AM, Sudeep Holla wrote: On 10/11/16 14:12, Rob Herring wrote: On Thu, Nov 10, 2016 at 4:26 AM, Sudeep Holla wrote: On 10/11/16 01:22, Rob Herring wrote: On Wed, Nov

Re: [PATCH v5 6/8] Documentation: bindings: add compatible specific to legacy SCPI protocol

On 10/11/16 19:03, Olof Johansson wrote: On Thu, Nov 10, 2016 at 6:34 AM, Sudeep Holla wrote: On 10/11/16 14:12, Rob Herring wrote: On Thu, Nov 10, 2016 at 4:26 AM, Sudeep Holla wrote: On 10/11/16 01:22, Rob Herring wrote: On Wed, Nov 02, 2016 at 10:52:09PM -0600, Sudeep Holla

Re: [PATCH v5 00/23] Support qcom's HSIC USB and rewrite USB2 HS support

On Tue, Oct 18, 2016 at 01:51:39PM -0700, Stephen Boyd wrote: > Quoting Peter Chen (2016-10-18 02:31:40) > > On Mon, Oct 17, 2016 at 06:56:13PM -0700, Stephen Boyd wrote: > > > I've also sent separate patches for other minor pieces to make this > > > all work. The full tree can be found here[2],

Re: [PATCH v5 00/23] Support qcom's HSIC USB and rewrite USB2 HS support

On Tue, Oct 18, 2016 at 01:51:39PM -0700, Stephen Boyd wrote: > Quoting Peter Chen (2016-10-18 02:31:40) > > On Mon, Oct 17, 2016 at 06:56:13PM -0700, Stephen Boyd wrote: > > > I've also sent separate patches for other minor pieces to make this > > > all work. The full tree can be found here[2],

Re: [patch v5] i2c: mux: mellanox: add driver

On 2016-11-10 13:56, Vadim Pasternak wrote: > > >> -Original Message- >> From: Peter Rosin [mailto:p...@axentia.se] >> Sent: Thursday, November 10, 2016 1:13 PM >> To: Vadim Pasternak ; w...@the-dreams.de >> Cc: linux-...@vger.kernel.org;

Re: [patch v5] i2c: mux: mellanox: add driver

On 2016-11-10 13:56, Vadim Pasternak wrote: > > >> -Original Message- >> From: Peter Rosin [mailto:p...@axentia.se] >> Sent: Thursday, November 10, 2016 1:13 PM >> To: Vadim Pasternak ; w...@the-dreams.de >> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; >>

Re: [PATCH v3 05/46] perf/x86/intel/cmt: add per-package locks

* Peter Zijlstra wrote: > On Thu, Nov 10, 2016 at 06:22:17PM -0800, David Carrillo-Cisneros wrote: > > A possible alternative to nested spinlocks is to use a single rw_lock to > > protect changes to the monr hierarchy. > > > > This works because, when manipulating pmonrs,

Re: [PATCH v3 05/46] perf/x86/intel/cmt: add per-package locks

* Peter Zijlstra wrote: > On Thu, Nov 10, 2016 at 06:22:17PM -0800, David Carrillo-Cisneros wrote: > > A possible alternative to nested spinlocks is to use a single rw_lock to > > protect changes to the monr hierarchy. > > > > This works because, when manipulating pmonrs, the monr hierarchy

Re: [PATCH v3 05/46] perf/x86/intel/cmt: add per-package locks

On Thu, Nov 10, 2016 at 06:22:17PM -0800, David Carrillo-Cisneros wrote: > A possible alternative to nested spinlocks is to use a single rw_lock to > protect changes to the monr hierarchy. > > This works because, when manipulating pmonrs, the monr hierarchy (monr's > parent and children) is read

Re: [PATCH v3 05/46] perf/x86/intel/cmt: add per-package locks

On Thu, Nov 10, 2016 at 06:22:17PM -0800, David Carrillo-Cisneros wrote: > A possible alternative to nested spinlocks is to use a single rw_lock to > protect changes to the monr hierarchy. > > This works because, when manipulating pmonrs, the monr hierarchy (monr's > parent and children) is read

Re: question about clk_get_parent

On Thu, 10 Nov 2016, Russell King - ARM Linux wrote: > On Thu, Nov 10, 2016 at 09:55:16PM +0100, Julia Lawall wrote: > > As far as I can see in the various definitions of clk_get_parent, they all > > return either NULL or a value stored in a structure field. But the > > documentation with the

Re: question about clk_get_parent

On Thu, 10 Nov 2016, Russell King - ARM Linux wrote: > On Thu, Nov 10, 2016 at 09:55:16PM +0100, Julia Lawall wrote: > > As far as I can see in the various definitions of clk_get_parent, they all > > return either NULL or a value stored in a structure field. But the > > documentation with the

[PATCH net 0/2] r8152: rx patches

Let the rx sw checksum available and add some checks for rx desc. Hayes Wang (2): r8152: fix the sw rx checksum is unavailable r8152: rx descriptor check drivers/net/usb/r8152.c | 46 +- 1 file changed, 45 insertions(+), 1 deletion(-) -- 2.7.4

[PATCH net 0/2] r8152: rx patches

Let the rx sw checksum available and add some checks for rx desc. Hayes Wang (2): r8152: fix the sw rx checksum is unavailable r8152: rx descriptor check drivers/net/usb/r8152.c | 46 +- 1 file changed, 45 insertions(+), 1 deletion(-) -- 2.7.4

[PATCH net 1/2] r8152: fix the sw rx checksum is unavailable

Fix the hw rx checksum is always enabled, and the user couldn't switch it to sw rx checksum. Note that the RTL_VER_01 only supports sw rx checksum only. Besides, the hw rx checksum for RTL_VER_02 is disabled after commit b9a321b48af4 ("r8152: Fix broken RX checksums."). Re-enable it.

[PATCH net 1/2] r8152: fix the sw rx checksum is unavailable

Fix the hw rx checksum is always enabled, and the user couldn't switch it to sw rx checksum. Note that the RTL_VER_01 only supports sw rx checksum only. Besides, the hw rx checksum for RTL_VER_02 is disabled after commit b9a321b48af4 ("r8152: Fix broken RX checksums."). Re-enable it.

[PATCH net 2/2] r8152: rx descriptor check

For some platforms, the data in memory is not the same with the one from the device. That is, the data of memory is unbelievable. The check is used to find out this situation. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 49

[PATCH net 2/2] r8152: rx descriptor check

For some platforms, the data in memory is not the same with the one from the device. That is, the data of memory is unbelievable. The check is used to find out this situation. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 49 + 1 file

Re: [PATCH v6 2/6] mm/cma: introduce new zone, ZONE_CMA

On Tue, Nov 08, 2016 at 02:59:19PM +0800, Chen Feng wrote: > > > On 2016/11/8 11:59, Joonsoo Kim wrote: > > On Mon, Nov 07, 2016 at 03:46:02PM +0800, Chen Feng wrote: > >> > >> > >> On 2016/11/7 15:44, Chen Feng wrote: > >>> On 2016/11/7 15:27, Joonsoo Kim wrote: > On Mon, Nov 07, 2016 at

Re: [PATCH v6 2/6] mm/cma: introduce new zone, ZONE_CMA

On Tue, Nov 08, 2016 at 02:59:19PM +0800, Chen Feng wrote: > > > On 2016/11/8 11:59, Joonsoo Kim wrote: > > On Mon, Nov 07, 2016 at 03:46:02PM +0800, Chen Feng wrote: > >> > >> > >> On 2016/11/7 15:44, Chen Feng wrote: > >>> On 2016/11/7 15:27, Joonsoo Kim wrote: > On Mon, Nov 07, 2016 at

[PATCH 2/2] staging: iio: ad7606: move out of staging

Move the ad7606 driver from staging/iio/adc to iio/adc. Also, update the corresponding Makefile and Kconfig associated with the change. Signed-off-by: Eva Rachel Retuya --- drivers/iio/adc/Kconfig | 34 +++ drivers/iio/adc/Makefile | 3 +

[PATCH 2/2] staging: iio: ad7606: move out of staging

Move the ad7606 driver from staging/iio/adc to iio/adc. Also, update the corresponding Makefile and Kconfig associated with the change. Signed-off-by: Eva Rachel Retuya --- drivers/iio/adc/Kconfig | 34 +++ drivers/iio/adc/Makefile | 3 + drivers/iio/adc/ad7606.c

[PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

Eliminate the non-standard attribute in_voltage_range and move its functionality under the scale attribute. read_raw() has been taken care of previously so only write_raw() is handled here. Additionally, rename the attribute in_voltage_range_available into in_voltage_scale_available.

[PATCH 0/2] staging: iio: ad7606: move driver out of staging

Address the last remaining TODO [1] for this driver and move it from staging into mainline. [1] https://marc.info/?l=linux-iio=147689684332118=2 Eva Rachel Retuya (2): staging: iio: ad7606: replace range/range_available with corresponding scale staging: iio: ad7606: move out of staging

[PATCH 1/2] staging: iio: ad7606: replace range/range_available with corresponding scale

Eliminate the non-standard attribute in_voltage_range and move its functionality under the scale attribute. read_raw() has been taken care of previously so only write_raw() is handled here. Additionally, rename the attribute in_voltage_range_available into in_voltage_scale_available.

[PATCH 0/2] staging: iio: ad7606: move driver out of staging

Address the last remaining TODO [1] for this driver and move it from staging into mainline. [1] https://marc.info/?l=linux-iio=147689684332118=2 Eva Rachel Retuya (2): staging: iio: ad7606: replace range/range_available with corresponding scale staging: iio: ad7606: move out of staging

Re: [PATCH] drivers: mfd: ti_am335x_tscadc: increase ADC ref clock to 24MHz

On Friday 11 November 2016 09:00 AM, John Syne wrote: > >> On Nov 9, 2016, at 9:07 PM, Vignesh R wrote: >> >> Hi, >> >> On Thursday 10 November 2016 05:23 AM, John Syne wrote: >>> OK, then back to my original question. Given that these DT properties are >>> supported in the

Re: [PATCH] drivers: mfd: ti_am335x_tscadc: increase ADC ref clock to 24MHz

On Friday 11 November 2016 09:00 AM, John Syne wrote: > >> On Nov 9, 2016, at 9:07 PM, Vignesh R wrote: >> >> Hi, >> >> On Thursday 10 November 2016 05:23 AM, John Syne wrote: >>> OK, then back to my original question. Given that these DT properties are >>> supported in the driver >>> >> >>

Re: [PATCH] cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB SoCs

Hi Markus, [auto build test ERROR on pm/linux-next] [also build test ERROR on next-20161110] [cannot apply to v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Markus-Mayer/cpufreq

Re: [PATCH] cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB SoCs

Hi Markus, [auto build test ERROR on pm/linux-next] [also build test ERROR on next-20161110] [cannot apply to v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Markus-Mayer/cpufreq

Re: [PATCH v3 8/9] media: venus: add Makefiles and Kconfig files

On Mon, Nov 7, 2016 at 11:04 PM, Stanimir Varbanov wrote: > Makefile and Kconfig files to build the Venus video codec driver. > > Signed-off-by: Stanimir Varbanov > --- > drivers/media/platform/qcom/Kconfig| 7 +++ >

Re: [PATCH v3 8/9] media: venus: add Makefiles and Kconfig files

On Mon, Nov 7, 2016 at 11:04 PM, Stanimir Varbanov wrote: > Makefile and Kconfig files to build the Venus video codec driver. > > Signed-off-by: Stanimir Varbanov > --- > drivers/media/platform/qcom/Kconfig| 7 +++ > drivers/media/platform/qcom/Makefile | 1 + >

Re: [PATCH] mm: support anonymous stable page

Sorry for sending a wrong version. Here is new one. >From 2d42ead9335cde51fd58d6348439ca03cf359ba2 Mon Sep 17 00:00:00 2001 From: Minchan Kim Date: Fri, 11 Nov 2016 15:02:57 +0900 Subject: [PATCH] mm: support anonymous stable page For developemnt for zram-swap asynchronous

Re: [PATCH] mm: support anonymous stable page

Sorry for sending a wrong version. Here is new one. >From 2d42ead9335cde51fd58d6348439ca03cf359ba2 Mon Sep 17 00:00:00 2001 From: Minchan Kim Date: Fri, 11 Nov 2016 15:02:57 +0900 Subject: [PATCH] mm: support anonymous stable page For developemnt for zram-swap asynchronous writeback, I found

[git pull] vfs.git

Christoph's and Jan's aio fixes, fixup for generic_file_splice_read (removal of pointless detritus that actually breaks it when used for gfs2 ->splice_read()) and fixup for generic_file_read_iter() interaction with ITER_PIPE destinations. The following changes since commit

[git pull] vfs.git

Christoph's and Jan's aio fixes, fixup for generic_file_splice_read (removal of pointless detritus that actually breaks it when used for gfs2 ->splice_read()) and fixup for generic_file_read_iter() interaction with ITER_PIPE destinations. The following changes since commit

Re: [v17 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

Hi Jitao, I couldn't locate the original mail, so posting on this thread instead. Some comments below. On 11/10/2016 10:09 PM, Enric Balletbo Serra wrote: Hi Jitao, 2016-08-27 8:44 GMT+02:00 Jitao Shi : This patch adds drm_bridge driver for parade DSI to eDP bridge

Re: [v17 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

Hi Jitao, I couldn't locate the original mail, so posting on this thread instead. Some comments below. On 11/10/2016 10:09 PM, Enric Balletbo Serra wrote: Hi Jitao, 2016-08-27 8:44 GMT+02:00 Jitao Shi : This patch adds drm_bridge driver for parade DSI to eDP bridge chip. Signed-off-by:

Re: [tip:x86/urgent] x86/cpu: Deal with broken firmware (VMWare/XEN)

Hi Thomas, On Wed, 2016-11-09 at 12:27 -0800, tip-bot for Thomas Gleixner wrote: > Commit-ID: d49597fd3bc7d9534de55e9256767f073be1b33a > Gitweb: >

Re: [tip:x86/urgent] x86/cpu: Deal with broken firmware (VMWare/XEN)

Hi Thomas, On Wed, 2016-11-09 at 12:27 -0800, tip-bot for Thomas Gleixner wrote: > Commit-ID: d49597fd3bc7d9534de55e9256767f073be1b33a > Gitweb: >

Re: [patch] mm, slab: faster active and free stats

On Wed, Nov 09, 2016 at 04:38:08PM -0800, David Rientjes wrote: > On Tue, 8 Nov 2016, Andrew Morton wrote: > > > > Reading /proc/slabinfo or monitoring slabtop(1) can become very expensive > > > if there are many slab caches and if there are very lengthy per-node > > > partial and/or free lists.

Re: [patch] mm, slab: faster active and free stats

On Wed, Nov 09, 2016 at 04:38:08PM -0800, David Rientjes wrote: > On Tue, 8 Nov 2016, Andrew Morton wrote: > > > > Reading /proc/slabinfo or monitoring slabtop(1) can become very expensive > > > if there are many slab caches and if there are very lengthy per-node > > > partial and/or free lists.

Re: [PATCH v16 0/5] Mediatek MT8173 CMDQ support

On Thu, Nov 10, 2016 at 4:45 PM, Horng-Shyang Liao wrote: > On Tue, 2016-11-01 at 19:28 +0800, HS Liao wrote: >> Hi, >> >> This is Mediatek MT8173 Command Queue(CMDQ) driver. The CMDQ is used >> to help write registers with critical time limitation, such as >> updating

Re: [PATCH v16 0/5] Mediatek MT8173 CMDQ support

On Thu, Nov 10, 2016 at 4:45 PM, Horng-Shyang Liao wrote: > On Tue, 2016-11-01 at 19:28 +0800, HS Liao wrote: >> Hi, >> >> This is Mediatek MT8173 Command Queue(CMDQ) driver. The CMDQ is used >> to help write registers with critical time limitation, such as >> updating display configuration

[PATCH] mm: support anonymous stable page

For developemnt for zram-swap asynchronous writeback, I found strange corruption of compressed page. With investigation, it reveals currently stable page doesn't support anonymous page. IOW, reuse_swap_page can reuse the page without waiting writeback completion so that it can corrupt data during

[PATCH] mm: support anonymous stable page

For developemnt for zram-swap asynchronous writeback, I found strange corruption of compressed page. With investigation, it reveals currently stable page doesn't support anonymous page. IOW, reuse_swap_page can reuse the page without waiting writeback completion so that it can corrupt data during

Re: [PATCH 06/35] staging: lustre: osc: Performance tune for LRU

Hi Jinshan, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20161110] [cannot apply to v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/James-Simmons

Re: [PATCH 06/35] staging: lustre: osc: Performance tune for LRU

Hi Jinshan, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20161110] [cannot apply to v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/James-Simmons

[PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence

[PATCH v8 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal

[PATCH v8 0/3] drm: add explict fencing

From: Gustavo Padovan Hi, New version of the DRM fences patches with all comments on v7 adressed. Please refer to the cover letter[1] in a previous version to check for more details. The changes since the last version can be seen in commit message on each

[PATCH v8 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and

[PATCH v8 2/3] drm/fence: add fence timeline to drm_crtc

From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init()

[PATCH v8 1/3] drm/fence: add in-fences support

From: Gustavo Padovan There is now a new property called IN_FENCE_FD attached to every plane state that receives sync_file fds from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_array subclass or just a normal fence) and then used by DRM to

[PATCH v8 0/3] drm: add explict fencing

From: Gustavo Padovan Hi, New version of the DRM fences patches with all comments on v7 adressed. Please refer to the cover letter[1] in a previous version to check for more details. The changes since the last version can be seen in commit message on each patch. Robert Foss managed to port

[PATCH v8 3/3] drm/fence: add out-fences support

From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the OUT_FENCE_PTR prop to send the sync_file fd back to userspace. The sync_file and fd are allocated/created before

[PATCH v4 1/6] kconfig: introduce the "imply" keyword

The "imply" keyword is a weak version of "select" where the target config symbol can still be turned off, avoiding those pitfalls that come with the "select" keyword. This is useful e.g. with multiple drivers that want to indicate their ability to hook into a secondary subsystem while allowing

[PATCH v4 6/6] posix-timers: make it configurable

Some embedded systems have no use for them. This removes about 25KB from the kernel binary size when configured out. Corresponding syscalls are routed to a stub logging the attempt to use those syscalls which should be enough of a clue if they were disabled without proper consideration. They

[PATCH v4 3/6] ptp_clock: allow for it to be optional

In order to break the hard dependency between the PTP clock subsystem and ethernet drivers capable of being clock providers, this patch provides simple PTP stub functions to allow linkage of those drivers into the kernel even when the PTP subsystem is configured out. Drivers must be ready to

[PATCH v4 1/6] kconfig: introduce the "imply" keyword

The "imply" keyword is a weak version of "select" where the target config symbol can still be turned off, avoiding those pitfalls that come with the "select" keyword. This is useful e.g. with multiple drivers that want to indicate their ability to hook into a secondary subsystem while allowing

[PATCH v4 6/6] posix-timers: make it configurable

Some embedded systems have no use for them. This removes about 25KB from the kernel binary size when configured out. Corresponding syscalls are routed to a stub logging the attempt to use those syscalls which should be enough of a clue if they were disabled without proper consideration. They

[PATCH v4 3/6] ptp_clock: allow for it to be optional

In order to break the hard dependency between the PTP clock subsystem and ethernet drivers capable of being clock providers, this patch provides simple PTP stub functions to allow linkage of those drivers into the kernel even when the PTP subsystem is configured out. Drivers must be ready to

[PATCH v4 2/6] kconfig: regenerate *.c_shipped files after previous changes

Signed-off-by: Nicolas Pitre --- scripts/kconfig/zconf.hash.c_shipped | 30 +- scripts/kconfig/zconf.tab.c_shipped | 1581 -- 2 files changed, 753 insertions(+), 858 deletions(-) diff --git a/scripts/kconfig/zconf.hash.c_shipped

[PATCH v4 2/6] kconfig: regenerate *.c_shipped files after previous changes

Signed-off-by: Nicolas Pitre --- scripts/kconfig/zconf.hash.c_shipped | 30 +- scripts/kconfig/zconf.tab.c_shipped | 1581 -- 2 files changed, 753 insertions(+), 858 deletions(-) diff --git a/scripts/kconfig/zconf.hash.c_shipped

[PATCH v4 5/6] posix_cpu_timers_exit: wrong place to collect entropy

There is no logical relation between add_device_randomness() and posix_cpu_timers_exit(). Let's move the former to where the later is called. This way, when posix-cpu-timers.c is compiled out, there is no need to worry about not losing a call to add_device_randomness(). Signed-off-by: Nicolas

[PATCH v4 5/6] posix_cpu_timers_exit: wrong place to collect entropy

There is no logical relation between add_device_randomness() and posix_cpu_timers_exit(). Let's move the former to where the later is called. This way, when posix-cpu-timers.c is compiled out, there is no need to worry about not losing a call to add_device_randomness(). Signed-off-by: Nicolas

[PATCH v4 0/6] make POSIX timers optional with some Kconfig help

Many embedded systems don't need the full POSIX timer support. Configuring them out provides a nice kernel image size reduction. When POSIX timers are configured out, the PTP clock subsystem should be left out as well. However a bunch of ethernet drivers currently *select* the later in their

[PATCH v4 0/6] make POSIX timers optional with some Kconfig help

Many embedded systems don't need the full POSIX timer support. Configuring them out provides a nice kernel image size reduction. When POSIX timers are configured out, the PTP clock subsystem should be left out as well. However a bunch of ethernet drivers currently *select* the later in their

[PATCH v4 4/6] timer: move sys_alarm from timer.c to itimer.c

Move the only user of alarm_setitimer to itimer.c where it is defined. This allows for making alarm_setitimer static, and dropping it from the build when __ARCH_WANT_SYS_ALARM is not defined. Signed-off-by: Nicolas Pitre --- include/linux/time.h | 2 -- kernel/time/itimer.c |

[PATCH v4 4/6] timer: move sys_alarm from timer.c to itimer.c

Move the only user of alarm_setitimer to itimer.c where it is defined. This allows for making alarm_setitimer static, and dropping it from the build when __ARCH_WANT_SYS_ALARM is not defined. Signed-off-by: Nicolas Pitre --- include/linux/time.h | 2 -- kernel/time/itimer.c | 15

Re: commit d7afaec0b564f0609e116f5: fuse: add FUSE_NO_OPEN_SUPPORT flag to INIT

On Nov 11 2016, Miklos Szeredi wrote: > On Thu, Nov 10, 2016 at 11:31 PM, Nikolaus Rath wrote: >> Hi Andrew, >> >> In commit d7afaec0b564f0609e116f5 you added a new FUSE_NO_OPEN_SUPPORT >> flag. But as far as I can tell, the flag is simply accepted without

Re: commit d7afaec0b564f0609e116f5: fuse: add FUSE_NO_OPEN_SUPPORT flag to INIT

On Nov 11 2016, Miklos Szeredi wrote: > On Thu, Nov 10, 2016 at 11:31 PM, Nikolaus Rath wrote: >> Hi Andrew, >> >> In commit d7afaec0b564f0609e116f5 you added a new FUSE_NO_OPEN_SUPPORT >> flag. But as far as I can tell, the flag is simply accepted without >> having any effect (including in

Re: commit 5c672ab3f0ee0f78f: fuse: serialize dirops by default

On Nov 10 2016, Miklos Szeredi wrote: > On Thu, Nov 10, 2016 at 11:21 PM, Nikolaus Rath wrote: >> Hi Miklos, >> >> In commit 5c672ab3f0ee0f78f7acad183f34db0f8781a200 you introduced a new >> FUSE_PARALLEL_DIROPS capability and bumped the kernel interface no

Re: commit 5c672ab3f0ee0f78f: fuse: serialize dirops by default

On Nov 10 2016, Miklos Szeredi wrote: > On Thu, Nov 10, 2016 at 11:21 PM, Nikolaus Rath wrote: >> Hi Miklos, >> >> In commit 5c672ab3f0ee0f78f7acad183f34db0f8781a200 you introduced a new >> FUSE_PARALLEL_DIROPS capability and bumped the kernel interface no to >> 25 - but there have been no

Re: [PATCH 1/3] tuntap: rx batching

On 16-11-10 08:28 PM, Jason Wang wrote: > > > On 2016年11月11日 12:17, John Fastabend wrote: >> On 16-11-10 07:31 PM, Michael S. Tsirkin wrote: >>> >On Fri, Nov 11, 2016 at 10:07:44AM +0800, Jason Wang wrote: >> >> >>On 2016年11月10日 00:38, Michael S. Tsirkin wrote: > >>>On Wed,

Re: [PATCH 1/3] tuntap: rx batching

On 16-11-10 08:28 PM, Jason Wang wrote: > > > On 2016年11月11日 12:17, John Fastabend wrote: >> On 16-11-10 07:31 PM, Michael S. Tsirkin wrote: >>> >On Fri, Nov 11, 2016 at 10:07:44AM +0800, Jason Wang wrote: >> >> >>On 2016年11月10日 00:38, Michael S. Tsirkin wrote: > >>>On Wed,

[RFC PATCH 1/2] net: use cmpxchg instead of spinlock in ptr rings

--- include/linux/ptr_ring_ll.h | 136 +++ include/linux/skb_array.h | 25 2 files changed, 161 insertions(+) create mode 100644 include/linux/ptr_ring_ll.h diff --git a/include/linux/ptr_ring_ll.h b/include/linux/ptr_ring_ll.h new file

[RFC PATCH 2/2] ptr_ring_ll: pop/push multiple objects at once

Signed-off-by: John Fastabend --- include/linux/ptr_ring_ll.h | 22 -- include/linux/skb_array.h | 11 +-- net/sched/sch_generic.c |2 +- 3 files changed, 26 insertions(+), 9 deletions(-) diff --git

[RFC PATCH 1/2] net: use cmpxchg instead of spinlock in ptr rings

--- include/linux/ptr_ring_ll.h | 136 +++ include/linux/skb_array.h | 25 2 files changed, 161 insertions(+) create mode 100644 include/linux/ptr_ring_ll.h diff --git a/include/linux/ptr_ring_ll.h b/include/linux/ptr_ring_ll.h new file

[RFC PATCH 2/2] ptr_ring_ll: pop/push multiple objects at once

Signed-off-by: John Fastabend --- include/linux/ptr_ring_ll.h | 22 -- include/linux/skb_array.h | 11 +-- net/sched/sch_generic.c |2 +- 3 files changed, 26 insertions(+), 9 deletions(-) diff --git a/include/linux/ptr_ring_ll.h

[RFC PATCH 0/2] illustrate cmpxchg ring for tap/tun and qdisc

This is a cmpxchg ring that could potentially be used to replace the spinlock variant of skb_array. Couple comments its missing a resize operator which would need to be added before it could be a drop in replacement. And although I tested the first patch with my latest set of qdisc updates the

[RFC PATCH 0/2] illustrate cmpxchg ring for tap/tun and qdisc

This is a cmpxchg ring that could potentially be used to replace the spinlock variant of skb_array. Couple comments its missing a resize operator which would need to be added before it could be a drop in replacement. And although I tested the first patch with my latest set of qdisc updates the

Re: [PATCH RFC 0/2] Generalize tpm2_get_tpm_pt to tpm2_get_cap

On 11/04/2016 12:58 PM, Jarkko Sakkinen wrote: Nayna, I've already sent these earlier this month as we had this discussion. Please look up your emails. I can apply these if they look good for you. Please review them. Sure, I replied just now. I am sorry if delay in response. I was off

Re: [PATCH RFC 0/2] Generalize tpm2_get_tpm_pt to tpm2_get_cap

On 11/04/2016 12:58 PM, Jarkko Sakkinen wrote: Nayna, I've already sent these earlier this month as we had this discussion. Please look up your emails. I can apply these if they look good for you. Please review them. Sure, I replied just now. I am sorry if delay in response. I was off

Re: [PATCH v5 02/23] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

Hello ChenYu On Fri, Nov 11, 2016 at 12:01 AM, Chen-Yu Tsai wrote: > On Fri, Nov 11, 2016 at 5:42 AM, Rob Herring wrote: [snip] >> >> Do you have patches using this already. If not, it is starting to get >> a bit late for v4.10. >> >> I can apply this, but then

Re: [PATCH v5 02/23] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

Hello ChenYu On Fri, Nov 11, 2016 at 12:01 AM, Chen-Yu Tsai wrote: > On Fri, Nov 11, 2016 at 5:42 AM, Rob Herring wrote: [snip] >> >> Do you have patches using this already. If not, it is starting to get >> a bit late for v4.10. >> >> I can apply this, but then you'll just be pulling in other

Re: [PATCH 05/35] staging: lustre: llog: fix wrong offset in llog_process_thread()

Hi Mikhail, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20161110] [cannot apply to v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/James-Simmons

Re: [PATCH 05/35] staging: lustre: llog: fix wrong offset in llog_process_thread()

Hi Mikhail, [auto build test ERROR on staging/staging-testing] [also build test ERROR on next-20161110] [cannot apply to v4.9-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/James-Simmons

Re: [kernel-hardening] Re: [RFC v4 PATCH 00/13] HARDENED_ATOMIC

On Thu, 2016-11-10 at 13:23 -0800, Kees Cook wrote: > If we don't use opt-out for atomics, we're going to be in the same > situation where we have to constantly review every commit with an > atomic for exploitable refcount flaws. Kicking this down from > "privilege escalation" to "DoS" is a

Re: [kernel-hardening] Re: [RFC v4 PATCH 00/13] HARDENED_ATOMIC

On Thu, 2016-11-10 at 13:23 -0800, Kees Cook wrote: > If we don't use opt-out for atomics, we're going to be in the same > situation where we have to constantly review every commit with an > atomic for exploitable refcount flaws. Kicking this down from > "privilege escalation" to "DoS" is a

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

On 2016-11-10 10:29, Vladimir Zapolskiy wrote: > Hi Stefan, Philipp, > > On 11/09/2016 02:50 AM, Stefan Agner wrote: >> On 2016-11-08 09:33, maitysancha...@gmail.com wrote: >>> Hello Shawn, >>> >>> On 16-10-22 15:43:04, Vladimir Zapolskiy wrote: Hi Shawn, On 10/22/2016 06:25 AM,

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

On 2016-11-10 10:29, Vladimir Zapolskiy wrote: > Hi Stefan, Philipp, > > On 11/09/2016 02:50 AM, Stefan Agner wrote: >> On 2016-11-08 09:33, maitysancha...@gmail.com wrote: >>> Hello Shawn, >>> >>> On 16-10-22 15:43:04, Vladimir Zapolskiy wrote: Hi Shawn, On 10/22/2016 06:25 AM,

Re: [PATCH v4 1/4] usb: dbc: early driver for xhci debug capability

Hi Peter, On 11/10/2016 07:44 PM, Peter Zijlstra wrote: > On Thu, Nov 10, 2016 at 09:56:41AM +0100, Thomas Gleixner wrote: >> On Thu, 10 Nov 2016, Lu Baolu wrote: >>> This seems to be a common issue for all early printk drivers. >> No. The other early printk drivers like serial do not have that

Re: [PATCH v4 1/4] usb: dbc: early driver for xhci debug capability

Hi Peter, On 11/10/2016 07:44 PM, Peter Zijlstra wrote: > On Thu, Nov 10, 2016 at 09:56:41AM +0100, Thomas Gleixner wrote: >> On Thu, 10 Nov 2016, Lu Baolu wrote: >>> This seems to be a common issue for all early printk drivers. >> No. The other early printk drivers like serial do not have that

  1   2   3   4   5   6   7   8   9   10   >