Re: [PATCH v3 0/8] try to reduce fragmenting fallbacks

On Fri, Mar 17, 2017 at 07:29:54PM +0100, Vlastimil Babka wrote: > On 03/16/2017 07:34 PM, Johannes Weiner wrote: > > The patched kernel also consistently beats vanilla in terms of peak > > job throughput. > > > > Overall very cool! > > Thanks a lot! So that means it's worth the increased

Re: [PATCH v3 0/8] try to reduce fragmenting fallbacks

On Fri, Mar 17, 2017 at 07:29:54PM +0100, Vlastimil Babka wrote: > On 03/16/2017 07:34 PM, Johannes Weiner wrote: > > The patched kernel also consistently beats vanilla in terms of peak > > job throughput. > > > > Overall very cool! > > Thanks a lot! So that means it's worth the increased

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

On Mon, Mar 20, 2017 at 2:13 AM, Jonathan Cameron wrote: > On 19/03/17 17:14, Gargi Sharma wrote: >> On Sun, Mar 19, 2017 at 6:20 PM, simran singhal >> wrote: >>> The IIO subsystem is redefining iio_dev->mlock to be used by >>> the IIO core only for

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

On Mon, Mar 20, 2017 at 2:13 AM, Jonathan Cameron wrote: > On 19/03/17 17:14, Gargi Sharma wrote: >> On Sun, Mar 19, 2017 at 6:20 PM, simran singhal >> wrote: >>> The IIO subsystem is redefining iio_dev->mlock to be used by >>> the IIO core only for protecting device operating mode changes. >>>

Re: [PATCHv5] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

On Sat, Mar 04, 2017 at 02:02:17PM +0100, Rabin Vincent wrote: > On Sat, Mar 04, 2017 at 12:51:12AM +, Abel Vesa wrote: > > diff --git a/arch/arm/kernel/entry-ftrace.S b/arch/arm/kernel/entry-ftrace.S > > index c73c403..93f9abb 100644 > > --- a/arch/arm/kernel/entry-ftrace.S > > +++

Re: [PATCHv5] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

On Sat, Mar 04, 2017 at 02:02:17PM +0100, Rabin Vincent wrote: > On Sat, Mar 04, 2017 at 12:51:12AM +, Abel Vesa wrote: > > diff --git a/arch/arm/kernel/entry-ftrace.S b/arch/arm/kernel/entry-ftrace.S > > index c73c403..93f9abb 100644 > > --- a/arch/arm/kernel/entry-ftrace.S > > +++

[PATCH v6] staging: Use buf_lock instead of mlock and Refactor code

The IIO subsystem is redefining iio_dev->mlock to be used by the IIO core only for protecting device operating mode changes. ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. In this driver, mlock was being used to protect hardware state changes. Replace it with buf_lock in the devices

[PATCH v6] staging: Use buf_lock instead of mlock and Refactor code

The IIO subsystem is redefining iio_dev->mlock to be used by the IIO core only for protecting device operating mode changes. ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. In this driver, mlock was being used to protect hardware state changes. Replace it with buf_lock in the devices

Re: [PATCH] ARM: wire up statx syscall

On 20/03/17 09:47, Russell King - ARM Linux wrote: > On Sun, Mar 19, 2017 at 08:12:48PM +, Chris Packham wrote: >> On 17/03/17 23:00, Russell King - ARM Linux wrote: >>> You obviously have not looked in linux-next. >> >> No I haven't. But even now I see nothing in >>

Re: [PATCH] ARM: wire up statx syscall

On 20/03/17 09:47, Russell King - ARM Linux wrote: > On Sun, Mar 19, 2017 at 08:12:48PM +, Chris Packham wrote: >> On 17/03/17 23:00, Russell King - ARM Linux wrote: >>> You obviously have not looked in linux-next. >> >> No I haven't. But even now I see nothing in >>

Re: [PATCH 2/4] ubifs: Fix unlink code wrt. double hash lookups

Hyunchul, Am 09.03.2017 um 08:04 schrieb Hyunchul Lee: >> -int n, err, type = key_type(c, key); >> -struct ubifs_znode *znode; >> +int err; > > i guess that err should be initialized with -ENOENT to avoid the first call > of > tnc_next(c, , n). Yes. err is used unitialized.

Re: [PATCH 2/4] ubifs: Fix unlink code wrt. double hash lookups

Hyunchul, Am 09.03.2017 um 08:04 schrieb Hyunchul Lee: >> -int n, err, type = key_type(c, key); >> -struct ubifs_znode *znode; >> +int err; > > i guess that err should be initialized with -ENOENT to avoid the first call > of > tnc_next(c, , n). Yes. err is used unitialized.

Re: [PATCH] ARM: wire up statx syscall

On Sun, Mar 19, 2017 at 08:12:48PM +, Chris Packham wrote: > On 17/03/17 23:00, Russell King - ARM Linux wrote: > > You obviously have not looked in linux-next. > > No I haven't. But even now I see nothing in > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master Hmm,

Re: [PATCH] ARM: wire up statx syscall

On Sun, Mar 19, 2017 at 08:12:48PM +, Chris Packham wrote: > On 17/03/17 23:00, Russell King - ARM Linux wrote: > > You obviously have not looked in linux-next. > > No I haven't. But even now I see nothing in > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master Hmm,

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

On 19/03/17 17:14, Gargi Sharma wrote: > On Sun, Mar 19, 2017 at 6:20 PM, simran singhal > wrote: >> The IIO subsystem is redefining iio_dev->mlock to be used by >> the IIO core only for protecting device operating mode changes. >> ie. Changes between INDIO_DIRECT_MODE,

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

On 19/03/17 17:14, Gargi Sharma wrote: > On Sun, Mar 19, 2017 at 6:20 PM, simran singhal > wrote: >> The IIO subsystem is redefining iio_dev->mlock to be used by >> the IIO core only for protecting device operating mode changes. >> ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. >>

Re: [PATCH 1/3] ubifs: remove filename from debug messages in ubifs_readdir

Hyunchul, Am 15.03.2017 um 02:31 schrieb Hyunchul Lee: > if filename is encrypted, filename could have no printable characters. > so remove it. thanks for cleaning this up! All three patches look good to me. Thanks, //richard

Re: [PATCH 1/3] ubifs: remove filename from debug messages in ubifs_readdir

Hyunchul, Am 15.03.2017 um 02:31 schrieb Hyunchul Lee: > if filename is encrypted, filename could have no printable characters. > so remove it. thanks for cleaning this up! All three patches look good to me. Thanks, //richard

Re: [HMM 00/16] HMM (Heterogeneous Memory Management) v18

On Thu, Mar 16, 2017 at 12:05:19PM -0400, J?r?me Glisse wrote: > Cliff note: HMM offers 2 things (each standing on its own). First > it allows to use device memory transparently inside any process > without any modifications to process program code. Second it allows > to mirror process address

Re: [HMM 00/16] HMM (Heterogeneous Memory Management) v18

On Thu, Mar 16, 2017 at 12:05:19PM -0400, J?r?me Glisse wrote: > Cliff note: HMM offers 2 things (each standing on its own). First > it allows to use device memory transparently inside any process > without any modifications to process program code. Second it allows > to mirror process address

Re: [PATCH] ARM: wire up statx syscall

On 17/03/17 23:00, Russell King - ARM Linux wrote: > You obviously have not looked in linux-next. No I haven't. But even now I see nothing in git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master I did do a search of the ARM mailing list.

Re: [PATCH] ARM: wire up statx syscall

On 17/03/17 23:00, Russell King - ARM Linux wrote: > You obviously have not looked in linux-next. No I haven't. But even now I see nothing in git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master I did do a search of the ARM mailing list.

Re: [HMM 11/16] mm/hmm/mirror: helper to snapshot CPU page table v2

On Thu, Mar 16, 2017 at 12:05:30PM -0400, J?r?me Glisse wrote: > This does not use existing page table walker because we want to share > same code for our page fault handler. > > Changes since v1: > - Use spinlock instead of rcu synchronized list traversal > Didn't look too closely here

Re: [HMM 10/16] mm/hmm/mirror: mirror process address space on device with HMM helpers

On Thu, Mar 16, 2017 at 12:05:29PM -0400, J?r?me Glisse wrote: > This is useful for NVidia GPU >= Pascal, Mellanox IB >= mlx5 and more > hardware in the future. > Insert boiler plate comment about in kernel user being ready here. > +#if IS_ENABLED(CONFIG_HMM_MIRROR) > > + */ > +struct

Re: [HMM 11/16] mm/hmm/mirror: helper to snapshot CPU page table v2

On Thu, Mar 16, 2017 at 12:05:30PM -0400, J?r?me Glisse wrote: > This does not use existing page table walker because we want to share > same code for our page fault handler. > > Changes since v1: > - Use spinlock instead of rcu synchronized list traversal > Didn't look too closely here

Re: [HMM 10/16] mm/hmm/mirror: mirror process address space on device with HMM helpers

On Thu, Mar 16, 2017 at 12:05:29PM -0400, J?r?me Glisse wrote: > This is useful for NVidia GPU >= Pascal, Mellanox IB >= mlx5 and more > hardware in the future. > Insert boiler plate comment about in kernel user being ready here. > +#if IS_ENABLED(CONFIG_HMM_MIRROR) > > + */ > +struct

Re: [HMM 06/16] mm/migrate: add new boolean copy flag to migratepage() callback

On Thu, Mar 16, 2017 at 12:05:25PM -0400, J?r?me Glisse wrote: > Allow migration without copy in case destination page already have > source page content. This is usefull for new dma capable migration > where use device dma engine to copy pages. > > This feature need carefull audit of filesystem

Re: [HMM 09/16] mm/hmm: heterogeneous memory management (HMM for short)

On Thu, Mar 16, 2017 at 12:05:28PM -0400, J?r?me Glisse wrote: > HMM provides 3 separate types of functionality: > - Mirroring: synchronize CPU page table and device page table > - Device memory: allocating struct page for device memory > - Migration: migrating regular memory to device

Re: [HMM 06/16] mm/migrate: add new boolean copy flag to migratepage() callback

On Thu, Mar 16, 2017 at 12:05:25PM -0400, J?r?me Glisse wrote: > Allow migration without copy in case destination page already have > source page content. This is usefull for new dma capable migration > where use device dma engine to copy pages. > > This feature need carefull audit of filesystem

Re: [HMM 09/16] mm/hmm: heterogeneous memory management (HMM for short)

On Thu, Mar 16, 2017 at 12:05:28PM -0400, J?r?me Glisse wrote: > HMM provides 3 separate types of functionality: > - Mirroring: synchronize CPU page table and device page table > - Device memory: allocating struct page for device memory > - Migration: migrating regular memory to device

Re: [HMM 03/16] mm/ZONE_DEVICE/free-page: callback when page is freed v3

On Thu, Mar 16, 2017 at 12:05:22PM -0400, J?r?me Glisse wrote: > When a ZONE_DEVICE page refcount reach 1 it means it is free and nobody > is holding a reference on it (only device to which the memory belong do). > Add a callback and call it when that happen so device driver can implement > their

Re: [HMM 04/16] mm/ZONE_DEVICE/unaddressable: add support for un-addressable device memory v3

Nits mainly On Thu, Mar 16, 2017 at 12:05:23PM -0400, J?r?me Glisse wrote: > This add support for un-addressable device memory. Such memory is hotpluged hotplugged > only so we can have struct page but we should never map them as such memory > can not be accessed by CPU. For that reason it uses

Re: [HMM 03/16] mm/ZONE_DEVICE/free-page: callback when page is freed v3

On Thu, Mar 16, 2017 at 12:05:22PM -0400, J?r?me Glisse wrote: > When a ZONE_DEVICE page refcount reach 1 it means it is free and nobody > is holding a reference on it (only device to which the memory belong do). > Add a callback and call it when that happen so device driver can implement > their

Re: [HMM 04/16] mm/ZONE_DEVICE/unaddressable: add support for un-addressable device memory v3

Nits mainly On Thu, Mar 16, 2017 at 12:05:23PM -0400, J?r?me Glisse wrote: > This add support for un-addressable device memory. Such memory is hotpluged hotplugged > only so we can have struct page but we should never map them as such memory > can not be accessed by CPU. For that reason it uses

Re: [HMM 02/16] mm/put_page: move ref decrement to put_zone_device_page()

On Thu, Mar 16, 2017 at 12:05:21PM -0400, J?r?me Glisse wrote: > This does not affect non ZONE_DEVICE page. In order to allow > ZONE_DEVICE page to be tracked we need to detect when refcount > of a ZONE_DEVICE page reach 1 (not 0 as non ZONE_DEVICE page). > > This patch just move

Re: [HMM 02/16] mm/put_page: move ref decrement to put_zone_device_page()

On Thu, Mar 16, 2017 at 12:05:21PM -0400, J?r?me Glisse wrote: > This does not affect non ZONE_DEVICE page. In order to allow > ZONE_DEVICE page to be tracked we need to detect when refcount > of a ZONE_DEVICE page reach 1 (not 0 as non ZONE_DEVICE page). > > This patch just move

Re: [HMM 01/16] mm/memory/hotplug: convert device bool to int to allow for more flags v3

On Thu, Mar 16, 2017 at 12:05:20PM -0400, J?r?me Glisse wrote: > When hotpluging memory we want more informations on the type of memory and > its properties. Replace the device boolean flag by an int and define a set > of flags. > > New property for device memory is an opt-in flag to allow page

Re: [HMM 01/16] mm/memory/hotplug: convert device bool to int to allow for more flags v3

On Thu, Mar 16, 2017 at 12:05:20PM -0400, J?r?me Glisse wrote: > When hotpluging memory we want more informations on the type of memory and > its properties. Replace the device boolean flag by an int and define a set > of flags. > > New property for device memory is an opt-in flag to allow page

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/19/2017 11:51 AM, Russell King - ARM Linux wrote: On Sun, Mar 19, 2017 at 11:37:15AM -0700, Steve Longerbeam wrote: On 03/19/2017 05:14 AM, Russell King - ARM Linux wrote: Right now, CSI doesn't do that - it only looks at the width, height, code, and field. Correct, there is currently

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/19/2017 11:51 AM, Russell King - ARM Linux wrote: On Sun, Mar 19, 2017 at 11:37:15AM -0700, Steve Longerbeam wrote: On 03/19/2017 05:14 AM, Russell King - ARM Linux wrote: Right now, CSI doesn't do that - it only looks at the width, height, code, and field. Correct, there is currently

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/19/2017 05:14 AM, Russell King - ARM Linux wrote: On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: On 03/18/2017 12:22 PM, Russell King - ARM Linux wrote: 0:00:01.955927879 20954 0x15ffe90 INFOv4l2 gstv4l2object.c:3811:gst_v4l2_object_get_caps:

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/19/2017 05:14 AM, Russell King - ARM Linux wrote: On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: On 03/18/2017 12:22 PM, Russell King - ARM Linux wrote: 0:00:01.955927879 20954 0x15ffe90 INFOv4l2 gstv4l2object.c:3811:gst_v4l2_object_get_caps:

Re: [PATCH v5 38/39] media: imx: csi: fix crop rectangle reset in sink set_fmt

On 03/19/2017 08:22 AM, Russell King - ARM Linux wrote: On Thu, Mar 09, 2017 at 08:53:18PM -0800, Steve Longerbeam wrote: From: Philipp Zabel The csi_try_crop call in set_fmt should compare the cropping rectangle to the currently set input format, not to the previous

Re: [PATCH v5 38/39] media: imx: csi: fix crop rectangle reset in sink set_fmt

On 03/19/2017 08:22 AM, Russell King - ARM Linux wrote: On Thu, Mar 09, 2017 at 08:53:18PM -0800, Steve Longerbeam wrote: From: Philipp Zabel The csi_try_crop call in set_fmt should compare the cropping rectangle to the currently set input format, not to the previous input format. Are we

Re: [PATCH v5 00/39] i.MX Media Driver

On Sun, Mar 19, 2017 at 11:37:15AM -0700, Steve Longerbeam wrote: > On 03/19/2017 05:14 AM, Russell King - ARM Linux wrote: > >Right now, CSI doesn't do that - it only looks at the width, height, > >code, and field. > > Correct, there is currently no propagation of the colorimetry > parameters

Re: [PATCH v5 00/39] i.MX Media Driver

On Sun, Mar 19, 2017 at 11:37:15AM -0700, Steve Longerbeam wrote: > On 03/19/2017 05:14 AM, Russell King - ARM Linux wrote: > >Right now, CSI doesn't do that - it only looks at the width, height, > >code, and field. > > Correct, there is currently no propagation of the colorimetry > parameters

Re: [PATCH] extcon: Allow registering a single notifier for all cables on an extcon_dev

/0day-ci/linux/commits/Hans-de-Goede/extcon-Allow-registering-a-single-notifier-for-all-cables-on-an-extcon_dev/20170319-204610 base: https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git extcon-next config: i386-randconfig-x072-201712 (attached as .config) compiler: gcc-6 (Debian

Re: [PATCH] extcon: Allow registering a single notifier for all cables on an extcon_dev

/0day-ci/linux/commits/Hans-de-Goede/extcon-Allow-registering-a-single-notifier-for-all-cables-on-an-extcon_dev/20170319-204610 base: https://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git extcon-next config: i386-randconfig-x072-201712 (attached as .config) compiler: gcc-6 (Debian

[PATCH v2] extcon: Allow registering a single notifier for all cables on an extcon_dev

In some cases a driver may want to monitor multiple cables on a single extcon. For example a charger driver will typically want to monitor all of EXTCON_CHG_USB_SDP, EXTCON_CHG_USB_CDP, EXTCON_CHG_USB_DCP to configure the max. current it can sink while charging. Due to the signature of the

[PATCH v2] extcon: Allow registering a single notifier for all cables on an extcon_dev

In some cases a driver may want to monitor multiple cables on a single extcon. For example a charger driver will typically want to monitor all of EXTCON_CHG_USB_SDP, EXTCON_CHG_USB_CDP, EXTCON_CHG_USB_DCP to configure the max. current it can sink while charging. Due to the signature of the

Re: [Outreachy kernel] [PATCH] staging: impedance-analyzer: ad5933: Remove unnecessary goto

On Sun, Mar 19, 2017 at 11:26 PM, Julia Lawall wrote: > > > On Sun, 19 Mar 2017, simran singhal wrote: > >> Remove unnecessary goto. >> >> Signed-off-by: simran singhal >> --- >> drivers/staging/iio/impedance-analyzer/ad5933.c | 10 -- >>

Re: [Outreachy kernel] [PATCH] staging: impedance-analyzer: ad5933: Remove unnecessary goto

On Sun, Mar 19, 2017 at 11:26 PM, Julia Lawall wrote: > > > On Sun, 19 Mar 2017, simran singhal wrote: > >> Remove unnecessary goto. >> >> Signed-off-by: simran singhal >> --- >> drivers/staging/iio/impedance-analyzer/ad5933.c | 10 -- >> 1 file changed, 4 insertions(+), 6 deletions(-)

Re: [Outreachy kernel] Re: [PATCH] staging: iio: ade7753: replace mlock with driver private lock

On Mon, Mar 13, 2017 at 5:30 PM, Lars-Peter Clausen wrote: > On 03/12/2017 02:32 PM, simran singhal wrote: >> The IIO subsystem is redefining iio_dev->mlock to be used by >> the IIO core only for protecting device operating mode changes. >> ie. Changes between INDIO_DIRECT_MODE,

Re: [Outreachy kernel] Re: [PATCH] staging: iio: ade7753: replace mlock with driver private lock

On Mon, Mar 13, 2017 at 5:30 PM, Lars-Peter Clausen wrote: > On 03/12/2017 02:32 PM, simran singhal wrote: >> The IIO subsystem is redefining iio_dev->mlock to be used by >> the IIO core only for protecting device operating mode changes. >> ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_*

Re: [RESEND PATCH 2/7] time: Change posix clocks ops interfaces to use timespec64

On Sat, Mar 18, 2017 at 10:17:41PM -0700, Deepa Dinamani wrote: > struct timespec is not y2038 safe. > Replace the posix_clock ops interfaces to use > struct timespec64. > The patch also changes struct itimerspec interfaces to > struct itimerspec64 as itimerspec internally uses timespec >

Re: [RESEND PATCH 2/7] time: Change posix clocks ops interfaces to use timespec64

On Sat, Mar 18, 2017 at 10:17:41PM -0700, Deepa Dinamani wrote: > struct timespec is not y2038 safe. > Replace the posix_clock ops interfaces to use > struct timespec64. > The patch also changes struct itimerspec interfaces to > struct itimerspec64 as itimerspec internally uses timespec >

Re: [PATCH v5 00/39] i.MX Media Driver

On Sun, Mar 19, 2017 at 10:54:22AM -0700, Steve Longerbeam wrote: > > > On 03/19/2017 03:38 AM, Russell King - ARM Linux wrote: > >On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: > >>Right, imx-media-capture.c (the "standard" v4l2 user interface module) > >>is not implementing

Re: [PATCH v5 00/39] i.MX Media Driver

On Sun, Mar 19, 2017 at 10:54:22AM -0700, Steve Longerbeam wrote: > > > On 03/19/2017 03:38 AM, Russell King - ARM Linux wrote: > >On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: > >>Right, imx-media-capture.c (the "standard" v4l2 user interface module) > >>is not implementing

Re: [Outreachy kernel] [PATCH] staging: impedance-analyzer: ad5933: Remove unnecessary goto

On Sun, 19 Mar 2017, simran singhal wrote: > Remove unnecessary goto. > > Signed-off-by: simran singhal > --- > drivers/staging/iio/impedance-analyzer/ad5933.c | 10 -- > 1 file changed, 4 insertions(+), 6 deletions(-) > > diff --git

Re: [Outreachy kernel] [PATCH] staging: impedance-analyzer: ad5933: Remove unnecessary goto

On Sun, 19 Mar 2017, simran singhal wrote: > Remove unnecessary goto. > > Signed-off-by: simran singhal > --- > drivers/staging/iio/impedance-analyzer/ad5933.c | 10 -- > 1 file changed, 4 insertions(+), 6 deletions(-) > > diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c

[PATCH] staging: impedance-analyzer: ad5933: Remove unnecessary goto

Remove unnecessary goto. Signed-off-by: simran singhal --- drivers/staging/iio/impedance-analyzer/ad5933.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c

[PATCH] staging: impedance-analyzer: ad5933: Remove unnecessary goto

Remove unnecessary goto. Signed-off-by: simran singhal --- drivers/staging/iio/impedance-analyzer/ad5933.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c b/drivers/staging/iio/impedance-analyzer/ad5933.c index

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/19/2017 03:38 AM, Russell King - ARM Linux wrote: On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: Right, imx-media-capture.c (the "standard" v4l2 user interface module) is not implementing VIDIOC_ENUM_FRAMESIZES. It should, but it can only return the single frame size

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/19/2017 03:38 AM, Russell King - ARM Linux wrote: On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: Right, imx-media-capture.c (the "standard" v4l2 user interface module) is not implementing VIDIOC_ENUM_FRAMESIZES. It should, but it can only return the single frame size

Re: [PATCH v2 2/2] fpga: Add support for Xilinx LogiCORE PR Decoupler

Hi Moritz, [auto build test WARNING on linus/master] [also build test WARNING on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 2/2] fpga: Add support for Xilinx LogiCORE PR Decoupler

Hi Moritz, [auto build test WARNING on linus/master] [also build test WARNING on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 2/2] fpga: Add support for Xilinx LogiCORE PR Decoupler

Hi Moritz, [auto build test WARNING on linus/master] [also build test WARNING on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 2/2] fpga: Add support for Xilinx LogiCORE PR Decoupler

Hi Moritz, [auto build test WARNING on linus/master] [also build test WARNING on v4.11-rc2 next-20170310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] staging: speakup: Removed Unnecessary parentheses.

Unnecessary parentheses are removed to improve readability. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/kobjects.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/speakup/kobjects.c

[PATCH] staging: speakup: Removed Unnecessary parentheses.

Unnecessary parentheses are removed to improve readability. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/kobjects.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/speakup/kobjects.c b/drivers/staging/speakup/kobjects.c index

[PATCH] ia64: fix module loading for gcc-5.4

Starting from gcc-5.4+ gcc geperates MLX instructions in more cases to refer local symbols: https://gcc.gnu.org/bugzilla/60465 That caused ia64 module loader to choke on such instructions: fuse: invalid slot number 1 for IMM64 Linux kernel used to handle only case where relocation

[PATCH] ia64: fix module loading for gcc-5.4

Starting from gcc-5.4+ gcc geperates MLX instructions in more cases to refer local symbols: https://gcc.gnu.org/bugzilla/60465 That caused ia64 module loader to choke on such instructions: fuse: invalid slot number 1 for IMM64 Linux kernel used to handle only case where relocation

[PATCH] staging: speakup: Simplify the NULL comparisons

Fixed coding style for null comparisons in speakup driver to be more consistant with the rest of the kernel coding style. Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/fakekey.c | 2 +-

[PATCH] staging: speakup: Simplify the NULL comparisons

Fixed coding style for null comparisons in speakup driver to be more consistant with the rest of the kernel coding style. Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/fakekey.c | 2 +- drivers/staging/speakup/main.c| 32

[RFC] AT_NO_JUMPS/LOOKUP_NO_JUMPS

Bringing back an old conversation - what do you think about the potential usefulness of the following ...at() option: * no mountpoint crossings allowed (mount --bind included) * only relative symlinks traversals are allowed * starting point acts as a chroot boundary

[RFC] AT_NO_JUMPS/LOOKUP_NO_JUMPS

Bringing back an old conversation - what do you think about the potential usefulness of the following ...at() option: * no mountpoint crossings allowed (mount --bind included) * only relative symlinks traversals are allowed * starting point acts as a chroot boundary

Re: [PATCH] scsi: libsas: fix ata xfer length

John Garry writes: John, > The total ata xfer length may not be calculated properly, > in that we do not use the proper method to get an sg element > dma length. > > According to the code comment, sg_dma_len() should be used > after dma_map_sg() is called. > > This issue

Re: [PATCH] scsi: libsas: fix ata xfer length

John Garry writes: John, > The total ata xfer length may not be calculated properly, > in that we do not use the proper method to get an sg element > dma length. > > According to the code comment, sg_dma_len() should be used > after dma_map_sg() is called. > > This issue was found by turning on

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

On Sun, Mar 19, 2017 at 6:20 PM, simran singhal wrote: > The IIO subsystem is redefining iio_dev->mlock to be used by > the IIO core only for protecting device operating mode changes. > ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. > > In this driver,

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

On Sun, Mar 19, 2017 at 6:20 PM, simran singhal wrote: > The IIO subsystem is redefining iio_dev->mlock to be used by > the IIO core only for protecting device operating mode changes. > ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. > > In this driver, mlock was being used to

Re: [PATCH 4.4 33/35] nfit, libnvdimm: fix interleave set cookie calculation

On Thu, 2017-03-16 at 23:29 +0900, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Dan Williams > > commit 86ef58a4e35e8fa66afb5898cf6dec6a3bb29f67 upstream. > > The

Re: [PATCH 4.4 33/35] nfit, libnvdimm: fix interleave set cookie calculation

On Thu, 2017-03-16 at 23:29 +0900, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Dan Williams > > commit 86ef58a4e35e8fa66afb5898cf6dec6a3bb29f67 upstream. > > The interleave-set cookie is a sum that

Re: [PATCH net] bridge: ebtables: fix reception of frames DNAT-ed to bridge device

On Fri, Mar 17, 2017 at 02:10:44PM +0100, Pablo Neira Ayuso wrote: > Wait. > > May this break local multicast listener that are bound to the bridge > interface? Assuming the bridge interface got an IP address, and that > there is local multicast listener. > > Missing anything here? Hm, for

Re: [PATCH net] bridge: ebtables: fix reception of frames DNAT-ed to bridge device

On Fri, Mar 17, 2017 at 02:10:44PM +0100, Pablo Neira Ayuso wrote: > Wait. > > May this break local multicast listener that are bound to the bridge > interface? Assuming the bridge interface got an IP address, and that > there is local multicast listener. > > Missing anything here? Hm, for

Re: [Outreachy kernel] Re: [PATCH] staging: iio: ade7753: replace mlock with driver private lock

On 19/03/17 13:16, Gargi Sharma wrote: > On Sun, Mar 19, 2017 at 4:01 PM, Jonathan Cameron wrote: >> On 17/03/17 09:32, Gargi Sharma wrote: >>> On Mon, Mar 13, 2017 at 5:30 PM, Lars-Peter Clausen wrote: On 03/12/2017 02:32 PM, simran singhal wrote:

Re: [Outreachy kernel] Re: [PATCH] staging: iio: ade7753: replace mlock with driver private lock

On 19/03/17 13:16, Gargi Sharma wrote: > On Sun, Mar 19, 2017 at 4:01 PM, Jonathan Cameron wrote: >> On 17/03/17 09:32, Gargi Sharma wrote: >>> On Mon, Mar 13, 2017 at 5:30 PM, Lars-Peter Clausen wrote: On 03/12/2017 02:32 PM, simran singhal wrote: > The IIO subsystem is redefining

Re: [PATCH 4.4 04/35] MIPS: Update defconfigs for NF_CT_PROTO_DCCP/UDPLITE change

On Thu, 2017-03-16 at 23:29 +0900, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Arnd Bergmann > > commit 9ddc16ad8e0bc7742fc96d5aaabc5b8698512cd1 upstream. > > In linux-4.10-rc,

Re: [PATCH 4.4 04/35] MIPS: Update defconfigs for NF_CT_PROTO_DCCP/UDPLITE change

On Thu, 2017-03-16 at 23:29 +0900, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Arnd Bergmann > > commit 9ddc16ad8e0bc7742fc96d5aaabc5b8698512cd1 upstream. > > In linux-4.10-rc, NF_CT_PROTO_UDPLITE and

[PATCH v6 14/15] scsi: pmcraid: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Tested-by: Peter Senna Tschudin

[PATCH v6 14/15] scsi: pmcraid: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Tested-by: Peter Senna Tschudin --- drivers/scsi/pmcraid.c | 10 +- drivers/scsi/pmcraid.h | 2 +-

[PATCH v6 15/15] PCI: Remove PCI pool macro functions

Now that all the drivers use dma pool API, we can remove the macro functions for PCI pool. Signed-off-by: Romain Perier Reviewed-by: Peter Senna Tschudin --- include/linux/pci.h | 9 - 1 file changed, 9 deletions(-) diff --git

[PATCH v6 15/15] PCI: Remove PCI pool macro functions

Now that all the drivers use dma pool API, we can remove the macro functions for PCI pool. Signed-off-by: Romain Perier Reviewed-by: Peter Senna Tschudin --- include/linux/pci.h | 9 - 1 file changed, 9 deletions(-) diff --git a/include/linux/pci.h b/include/linux/pci.h index

[PATCH v6 00/15] Replace PCI pool by DMA pool API

The current PCI pool API are simple macro functions direct expanded to the appropriate dma pool functions. The prototypes are almost the same and semantically, they are very similar. I propose to use the DMA pool API directly and get rid of the old API. This set of patches, replaces the old API

[PATCH v6 00/15] Replace PCI pool by DMA pool API

The current PCI pool API are simple macro functions direct expanded to the appropriate dma pool functions. The prototypes are almost the same and semantically, they are very similar. I propose to use the DMA pool API directly and get rid of the old API. This set of patches, replaces the old API

[PATCH v6 06/15] mlx5: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Reviewed-by: Peter Senna Tschudin --- drivers/net/ethernet/mellanox/mlx5/core/cmd.c

[PATCH v6 06/15] mlx5: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Reviewed-by: Peter Senna Tschudin --- drivers/net/ethernet/mellanox/mlx5/core/cmd.c | 11 ++- include/linux/mlx5/driver.h

[PATCH v6 03/15] IB/mthca: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Tested-by: Peter Senna Tschudin

[PATCH v6 05/15] mlx4: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Tested-by: Peter Senna Tschudin

[PATCH v6 03/15] IB/mthca: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Tested-by: Peter Senna Tschudin --- drivers/infiniband/hw/mthca/mthca_av.c | 10 +-

[PATCH v6 05/15] mlx4: Replace PCI pool old API

The PCI pool API is deprecated. This commit replaces the PCI pool old API by the appropriate function with the DMA pool API. Signed-off-by: Romain Perier Acked-by: Peter Senna Tschudin Tested-by: Peter Senna Tschudin --- drivers/net/ethernet/mellanox/mlx4/cmd.c | 10 +-

<    1   2   3   4   5   6   >