Re: [PATCH 2/2] tools lib traceevent: Use USECS_PER_SEC instead of hardcoded number

On Fri, 18 Nov 2016 20:40:22 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Nov 18, 2016 at 05:54:01PM -0500, Steven Rostedt escreveu: > > From: "Steven Rostedt (Red Hat)" > > > > Instead of using 100, define a USECS_PER_SEC macro and use that > >

Re: [PATCH 2/2] tools lib traceevent: Use USECS_PER_SEC instead of hardcoded number

On Fri, 18 Nov 2016 20:40:22 -0300 Arnaldo Carvalho de Melo wrote: > Em Fri, Nov 18, 2016 at 05:54:01PM -0500, Steven Rostedt escreveu: > > From: "Steven Rostedt (Red Hat)" > > > > Instead of using 100, define a USECS_PER_SEC macro and use that > > instead. > > We already have it in

Re: [PATCH] mfd: cpcap: Add minimal support

On Mon, Nov 21, 2016 at 11:45:58AM +, Lee Jones wrote: > On Fri, 18 Nov 2016, Tony Lindgren wrote: > > > Many Motorola phones like droid 4 are using a custom PMIC called CPCAP > > or 6556002. We can support it's core features quite easily with regmap_spi > > and regmap_irq. > > > > The

Re: [PATCH] mfd: cpcap: Add minimal support

On Mon, Nov 21, 2016 at 11:45:58AM +, Lee Jones wrote: > On Fri, 18 Nov 2016, Tony Lindgren wrote: > > > Many Motorola phones like droid 4 are using a custom PMIC called CPCAP > > or 6556002. We can support it's core features quite easily with regmap_spi > > and regmap_irq. > > > > The

Re: [PATCH 4.4 00/37] 4.4.34-stable review

On 11/19/2016 02:20 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.34 release. > There are 37 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 know. > > Responses

Re: [PATCH 4.4 00/37] 4.4.34-stable review

On 11/19/2016 02:20 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.34 release. > There are 37 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 know. > > Responses

[PATCH] binfmt_elf: use vmalloc() for allocation of vma_filesz

We have observed page allocations failures of order 4 during core dump while trying to allocate vma_filesz. This results in a useless core file of size 0. To improve reliability use vmalloc(). Note that the vmalloc() allocation is bounded by sysctl_max_map_count, which is 65,530 by default. So

[PATCH v6 3/5] USB: ohci: da8xx: Allow a regulator to handle VBUS

Using a regulator to handle VBUS will eliminate the need for platform data and callbacks, and make the driver more generic allowing different types of regulators to handle VBUS. The regulator equivalents to the platform callbacks are: set_power -> regulator_enable/regulator_disable

[PATCH v6 2/5] USB: ohci: da8xx: Add wrappers for platform callbacks

To migrate to a DT based boot, we will remove the use of platform callbacks, in favor of using the regulator framework to handle vbus and over current. In preparation to use a regulator instead of callbacks, move the platform data callbacks into separate functions. This provides well defined

[PATCH v6 5/5] USB: ohci: da8xx: Allow probing from DT

This adds the compatible string to the ohci driver to be able to probe from DT Signed-off-by: Axel Haslam --- drivers/usb/host/ohci-da8xx.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/usb/host/ohci-da8xx.c b/drivers/usb/host/ohci-da8xx.c index

[PATCH] binfmt_elf: use vmalloc() for allocation of vma_filesz

We have observed page allocations failures of order 4 during core dump while trying to allocate vma_filesz. This results in a useless core file of size 0. To improve reliability use vmalloc(). Note that the vmalloc() allocation is bounded by sysctl_max_map_count, which is 65,530 by default. So

[PATCH v6 3/5] USB: ohci: da8xx: Allow a regulator to handle VBUS

Using a regulator to handle VBUS will eliminate the need for platform data and callbacks, and make the driver more generic allowing different types of regulators to handle VBUS. The regulator equivalents to the platform callbacks are: set_power -> regulator_enable/regulator_disable

[PATCH v6 2/5] USB: ohci: da8xx: Add wrappers for platform callbacks

To migrate to a DT based boot, we will remove the use of platform callbacks, in favor of using the regulator framework to handle vbus and over current. In preparation to use a regulator instead of callbacks, move the platform data callbacks into separate functions. This provides well defined

[PATCH v6 5/5] USB: ohci: da8xx: Allow probing from DT

This adds the compatible string to the ohci driver to be able to probe from DT Signed-off-by: Axel Haslam --- drivers/usb/host/ohci-da8xx.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/usb/host/ohci-da8xx.c b/drivers/usb/host/ohci-da8xx.c index d0eb754..8b7479b 100644 ---

[PATCH v6 4/5] USB: ohci: da8xx: Add devicetree bindings

This patch documents the device tree bindings required for the ohci controller found in TI da8xx family of SoC's Cc: robh...@kernel.org Cc: mark.rutl...@arm.com Cc: devicet...@vger.kernel.org Acked-by: Rob Herring Signed-off-by: Axel Haslam ---

[PATCH 2/2] Add support for the Nexbox A1 board based on the Amlogic S912 SoC.

Signed-off-by: Neil Armstrong --- Documentation/devicetree/bindings/arm/amlogic.txt | 1 + arch/arm64/boot/dts/amlogic/Makefile | 1 + .../arm64/boot/dts/amlogic/meson-gxm-nexbox-a1.dts | 169 + 3 files changed, 171 insertions(+)

[PATCH v6 4/5] USB: ohci: da8xx: Add devicetree bindings

This patch documents the device tree bindings required for the ohci controller found in TI da8xx family of SoC's Cc: robh...@kernel.org Cc: mark.rutl...@arm.com Cc: devicet...@vger.kernel.org Acked-by: Rob Herring Signed-off-by: Axel Haslam --- .../devicetree/bindings/usb/ohci-da8xx.txt

[PATCH 2/2] Add support for the Nexbox A1 board based on the Amlogic S912 SoC.

Signed-off-by: Neil Armstrong --- Documentation/devicetree/bindings/arm/amlogic.txt | 1 + arch/arm64/boot/dts/amlogic/Makefile | 1 + .../arm64/boot/dts/amlogic/meson-gxm-nexbox-a1.dts | 169 + 3 files changed, 171 insertions(+) create mode 100644

[PATCH v6 0/5] USB: ohci-da8xx: Add device tree support

When booting using device tree, we can not make use of platform callbacks to handle vbus and over current gpios. This series allows the ohci-da8xx driver to use a regulator instead of the platform callbacks to control vbus and adds the device tree bindings to be able to probe using DT. Once all

[PATCH v6 1/5] USB: ohci: da8xx: use ohci priv data instead of globals

Instead of global variables, use the extra_priv_size of the ohci driver. We cannot yet move the ocic mask because this is used on the interrupt handler which is registerded through platform data and does not have an hcd pointer. This will be moved on a later patch. Signed-off-by: Axel Haslam

[PATCH 1/2] ARM64: dts: Add support for Meson GXM

Following the Amlogic Linux kernel, it seem the only differences between the GXL and GXM SoCs are the CPU Clusters. This commit renames the gxl-s905d-p23x DTSI in a common file for S905D p20x and S912 q20x boards. Then adds a meson-gxm dtsi and reproduce the P23x to Q20x boards dts files since

[PATCH v6 0/5] USB: ohci-da8xx: Add device tree support

When booting using device tree, we can not make use of platform callbacks to handle vbus and over current gpios. This series allows the ohci-da8xx driver to use a regulator instead of the platform callbacks to control vbus and adds the device tree bindings to be able to probe using DT. Once all

[PATCH v6 1/5] USB: ohci: da8xx: use ohci priv data instead of globals

Instead of global variables, use the extra_priv_size of the ohci driver. We cannot yet move the ocic mask because this is used on the interrupt handler which is registerded through platform data and does not have an hcd pointer. This will be moved on a later patch. Signed-off-by: Axel Haslam

[PATCH 1/2] ARM64: dts: Add support for Meson GXM

Following the Amlogic Linux kernel, it seem the only differences between the GXL and GXM SoCs are the CPU Clusters. This commit renames the gxl-s905d-p23x DTSI in a common file for S905D p20x and S912 q20x boards. Then adds a meson-gxm dtsi and reproduce the P23x to Q20x boards dts files since

[PATCH 0/2] ARM64: dts: Add support for Meson GXM

The new Amlogic GXM SoC (S912) is part of the Meson GX family and is nearly identical to GXM but with a second Quad-A53 core cluster. The GXM dtsi includes the GXL dtsi and the p20x dtsi is refactored in a common p20x/q20x to support the GXM Q200 and Q201 board that uses the exact same board

[PATCH 0/2] ARM64: dts: Add support for Meson GXM

The new Amlogic GXM SoC (S912) is part of the Meson GX family and is nearly identical to GXM but with a second Quad-A53 core cluster. The GXM dtsi includes the GXL dtsi and the p20x dtsi is refactored in a common p20x/q20x to support the GXM Q200 and Q201 board that uses the exact same board

Re: [PATCH 00/36] cputime: Convert core use of cputime_t to nsecs

On Mon, Nov 21, 2016 at 10:49:23AM +0100, Ingo Molnar wrote: > > * Frederic Weisbecker wrote: > > > > But I am still not happy about the approach. What is the compelling > > > reason for > > > this change except for the "but it looks ugly"? > > > > The diffstat (600 lines

Re: [PATCH 00/36] cputime: Convert core use of cputime_t to nsecs

On Mon, Nov 21, 2016 at 10:49:23AM +0100, Ingo Molnar wrote: > > * Frederic Weisbecker wrote: > > > > But I am still not happy about the approach. What is the compelling > > > reason for > > > this change except for the "but it looks ugly"? > > > > The diffstat (600 lines removed). Also the

Re: [PATCH 1/2] of: base: add support to get machine model name

On 21/11/16 16:05, Frank Rowand wrote: Hi Sudeep, On 11/18/16 12:22, Frank Rowand wrote: On 11/18/16 02:41, Sudeep Holla wrote: On 17/11/16 21:00, Frank Rowand wrote: On 11/17/16 07:32, Sudeep Holla wrote: Currently platforms/drivers needing to get the machine model name are replicating

Re: [PATCH 1/2] of: base: add support to get machine model name

On 21/11/16 16:05, Frank Rowand wrote: Hi Sudeep, On 11/18/16 12:22, Frank Rowand wrote: On 11/18/16 02:41, Sudeep Holla wrote: On 17/11/16 21:00, Frank Rowand wrote: On 11/17/16 07:32, Sudeep Holla wrote: Currently platforms/drivers needing to get the machine model name are replicating

Re: [PATCH 9/9] MODSIGN: Allow the "db" UEFI variable to be suppressed

On Mon, Nov 21, 2016 at 11:18 AM, Ard Biesheuvel wrote: > On 16 November 2016 at 18:11, David Howells wrote: >> From: Josh Boyer >> >> If a user tells shim to not use the certs/hashes in the UEFI db variable >> for

Re: [PATCH 9/9] MODSIGN: Allow the "db" UEFI variable to be suppressed

On Mon, Nov 21, 2016 at 11:18 AM, Ard Biesheuvel wrote: > On 16 November 2016 at 18:11, David Howells wrote: >> From: Josh Boyer >> >> If a user tells shim to not use the certs/hashes in the UEFI db variable >> for verification purposes, shim will set a UEFI variable called >> MokIgnoreDB.

Re: [PATCH 8/9] MODSIGN: Import certificates from UEFI Secure Boot

On Mon, Nov 21, 2016 at 11:16 AM, Ard Biesheuvel wrote: > On 16 November 2016 at 18:11, David Howells wrote: >> From: Josh Boyer >> >> Secure Boot stores a list of allowed certificates in the 'db' variable. >> This

Re: [PATCH 8/9] MODSIGN: Import certificates from UEFI Secure Boot

On Mon, Nov 21, 2016 at 11:16 AM, Ard Biesheuvel wrote: > On 16 November 2016 at 18:11, David Howells wrote: >> From: Josh Boyer >> >> Secure Boot stores a list of allowed certificates in the 'db' variable. >> This imports those certificates into the system trusted keyring. This >> allows for

Re: [PATCH 4/9] KEYS: Allow unrestricted boot-time addition of keys to secondary keyring

On Mon, 2016-11-21 at 15:17 +, David Howells wrote: > Mimi Zohar wrote: > > > > > > This allows keys in the UEFI database to be added in secure boot mode > > > > > for the purposes of module signing. > > > > > > > > The key import should not be automatic, it should

Re: [PATCH 4/9] KEYS: Allow unrestricted boot-time addition of keys to secondary keyring

On Mon, 2016-11-21 at 15:17 +, David Howells wrote: > Mimi Zohar wrote: > > > > > > This allows keys in the UEFI database to be added in secure boot mode > > > > > for the purposes of module signing. > > > > > > > > The key import should not be automatic, it should be optional. > > > > > >

Re: [PATCH net 07/18] net/ena: refactor ena_get_stats64 to be atomic context safe

Hi Netanel, [auto build test WARNING on net/master] url: https://github.com/0day-ci/linux/commits/Netanel-Belgazal/Update-ENA-driver-to-version-1-1-2/20161120-165649 config: i386-randconfig-h1-11212236 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: #

Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits

On 21-Nov 16:26, Peter Zijlstra wrote: > On Mon, Nov 21, 2016 at 02:59:19PM +, Patrick Bellasi wrote: > > > A fundamental problem in IMO is that we are trying to use a "dynamic > > metric" to act as a "predictor". > > > > PELT is a "dynamic metric" since it continuously change while a task >

Re: [PATCH net 07/18] net/ena: refactor ena_get_stats64 to be atomic context safe

Hi Netanel, [auto build test WARNING on net/master] url: https://github.com/0day-ci/linux/commits/Netanel-Belgazal/Update-ENA-driver-to-version-1-1-2/20161120-165649 config: i386-randconfig-h1-11212236 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: #

Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits

On 21-Nov 16:26, Peter Zijlstra wrote: > On Mon, Nov 21, 2016 at 02:59:19PM +, Patrick Bellasi wrote: > > > A fundamental problem in IMO is that we are trying to use a "dynamic > > metric" to act as a "predictor". > > > > PELT is a "dynamic metric" since it continuously change while a task >

[PATCH 3/3] ARM: davinci: hawk: use gpio descriptor for card detect

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio with the mmc core with API's designed for this purpose. This has the advantage that an irq will be registered,

[PATCH 3/3] ARM: davinci: hawk: use gpio descriptor for card detect

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio with the mmc core with API's designed for this purpose. This has the advantage that an irq will be registered,

Re: [mm PATCH v3 21/23] mm: Add support for releasing multiple instances of a page

On Fri, Nov 18, 2016 at 3:27 PM, Andrew Morton wrote: > On Thu, 10 Nov 2016 06:36:06 -0500 Alexander Duyck > wrote: > >> This patch adds a function that allows us to batch free a page that has >> multiple references outstanding.

Re: [mm PATCH v3 21/23] mm: Add support for releasing multiple instances of a page

On Fri, Nov 18, 2016 at 3:27 PM, Andrew Morton wrote: > On Thu, 10 Nov 2016 06:36:06 -0500 Alexander Duyck > wrote: > >> This patch adds a function that allows us to batch free a page that has >> multiple references outstanding. Specifically this function can be used to >> drop a page being

[PATCH 1/3] ARM: davinci: hawk: fix mmc card detect gpio

The card detect gpio on the hawk board is gpio4_0 and not gpio3_12 Signed-off-by: Axel Haslam --- arch/arm/mach-davinci/board-omapl138-hawk.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-davinci/board-omapl138-hawk.c

[PATCH 1/3] ARM: davinci: hawk: fix mmc card detect gpio

The card detect gpio on the hawk board is gpio4_0 and not gpio3_12 Signed-off-by: Axel Haslam --- arch/arm/mach-davinci/board-omapl138-hawk.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-davinci/board-omapl138-hawk.c

Re: [PATCH 1/2] of: base: add support to get machine model name

On 18/11/16 20:22, Frank Rowand wrote: On 11/18/16 02:41, Sudeep Holla wrote: On 17/11/16 21:00, Frank Rowand wrote: On 11/17/16 07:32, Sudeep Holla wrote: Currently platforms/drivers needing to get the machine model name are replicating the same snippet of code. In some case, the OF

Re: [PATCH 1/2] of: base: add support to get machine model name

On 18/11/16 20:22, Frank Rowand wrote: On 11/18/16 02:41, Sudeep Holla wrote: On 17/11/16 21:00, Frank Rowand wrote: On 11/17/16 07:32, Sudeep Holla wrote: Currently platforms/drivers needing to get the machine model name are replicating the same snippet of code. In some case, the OF

Re: [PATCH 00/36] cputime: Convert core use of cputime_t to nsecs

On Mon, Nov 21, 2016 at 07:59:56AM +0100, Martin Schwidefsky wrote: > On Fri, 18 Nov 2016 15:47:02 +0100 > Frederic Weisbecker wrote: > > Just because some code isn't too complex doesn't mean we really want to > > keep it. > > I get regular questions about what unit does

Re: [PATCH 00/36] cputime: Convert core use of cputime_t to nsecs

On Mon, Nov 21, 2016 at 07:59:56AM +0100, Martin Schwidefsky wrote: > On Fri, 18 Nov 2016 15:47:02 +0100 > Frederic Weisbecker wrote: > > Just because some code isn't too complex doesn't mean we really want to > > keep it. > > I get regular questions about what unit does cputime_t map to on a

Re: [PATCH v2] clk: qcom: smd-rpmcc: Add msm8974 clocks

On Fri, Nov 18, 2016 at 08:33:25AM -0800, Bjorn Andersson wrote: > This adds all RPM based clocks for msm8974, except cxo and > gfx3d_clk_src. > > Tested-by: Georgi Djakov > Signed-off-by: Bjorn Andersson > --- > > Changes since v1: > -

Re: [PATCH v2] clk: qcom: smd-rpmcc: Add msm8974 clocks

On Fri, Nov 18, 2016 at 08:33:25AM -0800, Bjorn Andersson wrote: > This adds all RPM based clocks for msm8974, except cxo and > gfx3d_clk_src. > > Tested-by: Georgi Djakov > Signed-off-by: Bjorn Andersson > --- > > Changes since v1: > - Fixed the screwed up indentation > >

Re: [PATCH 9/9] MODSIGN: Allow the "db" UEFI variable to be suppressed

On 16 November 2016 at 18:11, David Howells wrote: > From: Josh Boyer > > If a user tells shim to not use the certs/hashes in the UEFI db variable > for verification purposes, shim will set a UEFI variable called > MokIgnoreDB. Have the uefi

Re: [PATCH 9/9] MODSIGN: Allow the "db" UEFI variable to be suppressed

On 16 November 2016 at 18:11, David Howells wrote: > From: Josh Boyer > > If a user tells shim to not use the certs/hashes in the UEFI db variable > for verification purposes, shim will set a UEFI variable called > MokIgnoreDB. Have the uefi import code look for this and ignore the db >

RE: Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hello Mr. Torokhov, >> static void __evdev_queue_syn_dropped(struct evdev_client *client) >> { >> struct input_event ev; >> +struct input_event *last_ev; >> ktime_t time; >> +unsigned int mask = client->bufsize - 1; >> + >> +/* capture last event

RE: Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hello Mr. Torokhov, >> static void __evdev_queue_syn_dropped(struct evdev_client *client) >> { >> struct input_event ev; >> +struct input_event *last_ev; >> ktime_t time; >> +unsigned int mask = client->bufsize - 1; >> + >> +/* capture last event

Re: [PATCH V2 1/2] regulator: pwm: DT: Add ramp delay for exponential voltage transition

On Fri, Nov 18, 2016 at 08:05:55PM +0530, Laxman Dewangan wrote: > Some PWM regulator has the exponential transition in voltage change as > opposite to fixed slew-rate linear transition on other regulators. > For such PWM regulators, add the property to tell that voltage change > is exponential

Re: [PATCH V2 1/2] regulator: pwm: DT: Add ramp delay for exponential voltage transition

On Fri, Nov 18, 2016 at 08:05:55PM +0530, Laxman Dewangan wrote: > Some PWM regulator has the exponential transition in voltage change as > opposite to fixed slew-rate linear transition on other regulators. > For such PWM regulators, add the property to tell that voltage change > is exponential

Re: [RFC PATCH net v2 2/3] dt: bindings: add ethernet phy eee-disable-advert option documentation

On Mon, 2016-11-21 at 17:01 +0100, Andrew Lunn wrote: > On Mon, Nov 21, 2016 at 04:35:23PM +0100, Jerome Brunet wrote: > > > > Signed-off-by: Jerome Brunet > > --- > >  Documentation/devicetree/bindings/net/phy.txt | 5 + > >  1 file changed, 5 insertions(+) > > > >

Re: [RFC PATCH net v2 2/3] dt: bindings: add ethernet phy eee-disable-advert option documentation

On Mon, 2016-11-21 at 17:01 +0100, Andrew Lunn wrote: > On Mon, Nov 21, 2016 at 04:35:23PM +0100, Jerome Brunet wrote: > > > > Signed-off-by: Jerome Brunet > > --- > >  Documentation/devicetree/bindings/net/phy.txt | 5 + > >  1 file changed, 5 insertions(+) > > > > diff --git

Re: [PATCH 8/9] MODSIGN: Import certificates from UEFI Secure Boot

On 16 November 2016 at 18:11, David Howells wrote: > From: Josh Boyer > > Secure Boot stores a list of allowed certificates in the 'db' variable. > This imports those certificates into the system trusted keyring. This > allows for a third party

Re: [PATCH 8/9] MODSIGN: Import certificates from UEFI Secure Boot

On 16 November 2016 at 18:11, David Howells wrote: > From: Josh Boyer > > Secure Boot stores a list of allowed certificates in the 'db' variable. > This imports those certificates into the system trusted keyring. This > allows for a third party signing certificate to be used in conjunction >

[PATCH 2/3] ARM: davinci: hawk: remove mmc ro pin

The hawk board does not have a write protect pin to read the card write protect status. So remove un-needed platform data declaration for this gpio. Signed-off-by: Axel Haslam --- arch/arm/mach-davinci/board-omapl138-hawk.c | 19 +-- 1 file changed, 1

[PATCH 2/3] ARM: davinci: hawk: remove mmc ro pin

The hawk board does not have a write protect pin to read the card write protect status. So remove un-needed platform data declaration for this gpio. Signed-off-by: Axel Haslam --- arch/arm/mach-davinci/board-omapl138-hawk.c | 19 +-- 1 file changed, 1 insertion(+), 18

[PATCH 0/3] ARM: davinci: hawk: fix mmc gpio declaration

The hawk board does not have a write protect gpio, so remove it form the platform data. Also the card detect gpio is declared on the wrong pin. fix it. After fixing the platform data bugs, change to use a gpio descriptor, so we can take advantage of the drivers recent updates, and have card

[PATCH 0/3] ARM: davinci: hawk: fix mmc gpio declaration

The hawk board does not have a write protect gpio, so remove it form the platform data. Also the card detect gpio is declared on the wrong pin. fix it. After fixing the platform data bugs, change to use a gpio descriptor, so we can take advantage of the drivers recent updates, and have card

Re: [RFC PATCH v2 3/7] iio: inkern: api for manipulating ext_info of iio channels

On 2016-11-21 16:45, Lars-Peter Clausen wrote: > On 11/19/2016 04:38 PM, Jonathan Cameron wrote: >> On 17/11/16 21:48, Peter Rosin wrote: >>> Extend the inkern api with functions for reading and writing ext_info >>> of iio channels. >> I'd like Lars' feedback on this one. >> >> Superficially looks

Re: [RFC PATCH v2 3/7] iio: inkern: api for manipulating ext_info of iio channels

On 2016-11-21 16:45, Lars-Peter Clausen wrote: > On 11/19/2016 04:38 PM, Jonathan Cameron wrote: >> On 17/11/16 21:48, Peter Rosin wrote: >>> Extend the inkern api with functions for reading and writing ext_info >>> of iio channels. >> I'd like Lars' feedback on this one. >> >> Superficially looks

RE: [PATCH for-next 03/11] IB/hns: Optimize the logic of allocating memory using APIs

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Wednesday, November 16, 2016 8:36 AM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; > mehta.salil@gmail.com; linux-r...@vger.kernel.org; > net...@vger.kernel.org;

RE: [PATCH for-next 03/11] IB/hns: Optimize the logic of allocating memory using APIs

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Wednesday, November 16, 2016 8:36 AM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; > mehta.salil@gmail.com; linux-r...@vger.kernel.org; > net...@vger.kernel.org;

Re: Synopsys Ethernet QoS Driver

On 21-11-2016 15:43, Lars Persson wrote: > > >> 21 nov. 2016 kl. 16:06 skrev Joao Pinto : >> >>> On 21-11-2016 14:25, Giuseppe CAVALLARO wrote: On 11/21/2016 2:28 PM, Lars Persson wrote: > 21 nov. 2016 kl. 13:53 skrev Giuseppe CAVALLARO

Re: Synopsys Ethernet QoS Driver

On 21-11-2016 15:43, Lars Persson wrote: > > >> 21 nov. 2016 kl. 16:06 skrev Joao Pinto : >> >>> On 21-11-2016 14:25, Giuseppe CAVALLARO wrote: On 11/21/2016 2:28 PM, Lars Persson wrote: > 21 nov. 2016 kl. 13:53 skrev Giuseppe CAVALLARO : > > Hello Joao > >> On

Re: Formal description of system call interface

Hi! > Description of "returns fd or this set of errors" looks simple and useful. > Any test system or fuzzer will be able to verify that kernel actually returns > claimed return values. Also Carlos expressed interested in errno values > in the context of glibc. > I would do it from day one. > >

Re: Formal description of system call interface

Hi! > Description of "returns fd or this set of errors" looks simple and useful. > Any test system or fuzzer will be able to verify that kernel actually returns > claimed return values. Also Carlos expressed interested in errno values > in the context of glibc. > I would do it from day one. > >

Re: [PATCH v3 4/9] media: venus: vdec: add video decoder files

On 11/21/2016 05:33 PM, Hans Verkuil wrote: > On 21/11/16 16:29, Stanimir Varbanov wrote: >> Hi Hans, >> >> On 11/21/2016 05:04 PM, Hans Verkuil wrote: >>> On 18/11/16 10:11, Stanimir Varbanov wrote: Hi Hans, >>> + >>> +static int >>> +vdec_reqbufs(struct file *file, void

Re: [PATCH v3 4/9] media: venus: vdec: add video decoder files

On 11/21/2016 05:33 PM, Hans Verkuil wrote: > On 21/11/16 16:29, Stanimir Varbanov wrote: >> Hi Hans, >> >> On 11/21/2016 05:04 PM, Hans Verkuil wrote: >>> On 18/11/16 10:11, Stanimir Varbanov wrote: Hi Hans, >>> + >>> +static int >>> +vdec_reqbufs(struct file *file, void

[tip:smp/hotplug 5/20] arch/x86/kernel/msr.c:220:27: error: 'CPUHP_X86_MSR_PREPARE' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug head: 73f4f6f5ab9a069037b8e98663193accaf18bd5c commit: 216a5d1b866538a021af00bfb7c5dcd1da8ff884 [5/20] x86/msr: Convert to hotplug state machine config: x86_64-randconfig-x011-201647 (attached as .config) compiler:

[tip:smp/hotplug 5/20] arch/x86/kernel/msr.c:220:27: error: 'CPUHP_X86_MSR_PREPARE' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug head: 73f4f6f5ab9a069037b8e98663193accaf18bd5c commit: 216a5d1b866538a021af00bfb7c5dcd1da8ff884 [5/20] x86/msr: Convert to hotplug state machine config: x86_64-randconfig-x011-201647 (attached as .config) compiler:

Re: [PATCH 6/9] efi: Add EFI signature data types

On 17 November 2016 at 09:44, David Howells wrote: > Mat Martineau wrote: > >> The trailing ';' on EFI_CERT_X509_SHA256_GUID could trip someone up later. As >> long as you're fixing that, the spaces before the closing parens are >>

Re: [PATCH 6/9] efi: Add EFI signature data types

On 17 November 2016 at 09:44, David Howells wrote: > Mat Martineau wrote: > >> The trailing ';' on EFI_CERT_X509_SHA256_GUID could trip someone up later. As >> long as you're fixing that, the spaces before the closing parens are >> inconsistent with the other GUID definitions in this file. > >

Re: [PATCH 5/9] efi: Add SHIM and image security database GUID definitions

On 16 November 2016 at 18:11, David Howells wrote: > Add the definitions for shim and image security database, both of which > are used widely in various Linux distros. > > Signed-off-by: Josh Boyer > Signed-off-by: David Howells

Re: [PATCH 5/9] efi: Add SHIM and image security database GUID definitions

On 16 November 2016 at 18:11, David Howells wrote: > Add the definitions for shim and image security database, both of which > are used widely in various Linux distros. > > Signed-off-by: Josh Boyer > Signed-off-by: David Howells This patch Reviewed-by: Ard Biesheuvel but I do have a

Re: [BUG] msr-trace.h:42 suspicious rcu_dereference_check() usage!

+ tglx. On Mon, Nov 21, 2016 at 04:41:04PM +0100, Peter Zijlstra wrote: > Right, I just wondered about the !c1e present case. In that case we'll > forever read the msr in the hope of finding that bit set, and we never > will. Well, erratum 400 flag is set on everything F10h from model 0x2

Re: [BUG] msr-trace.h:42 suspicious rcu_dereference_check() usage!

+ tglx. On Mon, Nov 21, 2016 at 04:41:04PM +0100, Peter Zijlstra wrote: > Right, I just wondered about the !c1e present case. In that case we'll > forever read the msr in the hope of finding that bit set, and we never > will. Well, erratum 400 flag is set on everything F10h from model 0x2

Re: [PATCH 1/2] of: base: add support to get machine model name

Hi Sudeep, On 11/18/16 12:22, Frank Rowand wrote: > On 11/18/16 02:41, Sudeep Holla wrote: >> >> >> On 17/11/16 21:00, Frank Rowand wrote: >>> On 11/17/16 07:32, Sudeep Holla wrote: Currently platforms/drivers needing to get the machine model name are replicating the same snippet of

Re: [PATCH 1/2] of: base: add support to get machine model name

Hi Sudeep, On 11/18/16 12:22, Frank Rowand wrote: > On 11/18/16 02:41, Sudeep Holla wrote: >> >> >> On 17/11/16 21:00, Frank Rowand wrote: >>> On 11/17/16 07:32, Sudeep Holla wrote: Currently platforms/drivers needing to get the machine model name are replicating the same snippet of

[PATCH v2] ARM: dts: qcom: Add apq8064 CoreSight components

From: "Ivan T. Ivanov" Add initial set of CoreSight components found on Qualcomm apq8064 based platforms, including the IFC6410 board. Signed-off-by: Ivan T. Ivanov Acked-by: Mathieu Poirier Signed-off-by: Georgi

[PATCH v2] ARM: dts: qcom: Add apq8064 CoreSight components

From: "Ivan T. Ivanov" Add initial set of CoreSight components found on Qualcomm apq8064 based platforms, including the IFC6410 board. Signed-off-by: Ivan T. Ivanov Acked-by: Mathieu Poirier Signed-off-by: Georgi Djakov --- Changes since v1 (https://lkml.org/lkml/2016/11/17/474) * Moved

[PATCH v5] arm64: dts: qcom: Add msm8916 CoreSight components

From: "Ivan T. Ivanov" Add initial set of CoreSight components found on Qualcomm msm8916 and apq8016 based platforms, including the DragonBoard 410c board. Signed-off-by: Ivan T. Ivanov Acked-by: Mathieu Poirier

[PATCH v5] arm64: dts: qcom: Add msm8916 CoreSight components

From: "Ivan T. Ivanov" Add initial set of CoreSight components found on Qualcomm msm8916 and apq8016 based platforms, including the DragonBoard 410c board. Signed-off-by: Ivan T. Ivanov Acked-by: Mathieu Poirier Signed-off-by: Georgi Djakov --- Changes since v4:

Re: What exactly do 32-bit x86 exceptions push on the stack in the CS slot?

On 11/20/16 20:54, h...@zytor.com wrote: > > I believe i686+ writes zero, older CPUs leave unchanged. > I should point out that, at least from my memory, the same applies to instructions like "movl ". I can't even remember for sure how the behavior differs between "movl ," and "movl ,"; I'd

Re: What exactly do 32-bit x86 exceptions push on the stack in the CS slot?

On 11/20/16 20:54, h...@zytor.com wrote: > > I believe i686+ writes zero, older CPUs leave unchanged. > I should point out that, at least from my memory, the same applies to instructions like "movl ". I can't even remember for sure how the behavior differs between "movl ," and "movl ,"; I'd

Re: [RFC PATCH net v2 2/3] dt: bindings: add ethernet phy eee-disable-advert option documentation

On Mon, Nov 21, 2016 at 04:35:23PM +0100, Jerome Brunet wrote: > Signed-off-by: Jerome Brunet > --- > Documentation/devicetree/bindings/net/phy.txt | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/phy.txt >

Re: [RFC PATCH net v2 2/3] dt: bindings: add ethernet phy eee-disable-advert option documentation

On Mon, Nov 21, 2016 at 04:35:23PM +0100, Jerome Brunet wrote: > Signed-off-by: Jerome Brunet > --- > Documentation/devicetree/bindings/net/phy.txt | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/phy.txt >

[tip:smp/hotplug 4/20] arch/x86/kernel/cpuid.c:161:2: error: 'cpuhp_cpuid_state' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug head: 73f4f6f5ab9a069037b8e98663193accaf18bd5c commit: 22fbf682c20b8c51a7fbe51d43bc9833b26c2cc4 [4/20] x86/cpuid: Move the hotplug callbacks to online config: x86_64-randconfig-x011-201647 (attached as .config)

[tip:smp/hotplug 4/20] arch/x86/kernel/cpuid.c:161:2: error: 'cpuhp_cpuid_state' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug head: 73f4f6f5ab9a069037b8e98663193accaf18bd5c commit: 22fbf682c20b8c51a7fbe51d43bc9833b26c2cc4 [4/20] x86/cpuid: Move the hotplug callbacks to online config: x86_64-randconfig-x011-201647 (attached as .config)

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Mon, Nov 21, 2016 at 04:49:15PM +0100, Peter Zijlstra wrote: > > Speaking of non-fitting patterns. This one is quite common in > > networking code for refcounters: > > > > if (atomic_cmpxchg(>refcnt, 1, 0) == 1) {} This is from > > net/netfilter/nfnetlink_acct.c, but there are similar ones in

Re: [RFC][PATCH 2/7] kref: Add kref_read()

On Mon, Nov 21, 2016 at 04:49:15PM +0100, Peter Zijlstra wrote: > > Speaking of non-fitting patterns. This one is quite common in > > networking code for refcounters: > > > > if (atomic_cmpxchg(>refcnt, 1, 0) == 1) {} This is from > > net/netfilter/nfnetlink_acct.c, but there are similar ones in

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: > > > Nov 17 15:07:51 localhost kernel: Check point 10 > > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer > > dereference at 0249 > > Nov 17

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote: > On Thu, 2016-11-17 at 17:11 +0100, Wim Osterholt wrote: > > > Nov 17 15:07:51 localhost kernel: Check point 10 > > Nov 17 15:07:51 localhost kernel: BUG: unable to handle kernel NULL pointer > > dereference at 0249 > > Nov 17

<    4   5   6   7   8   9   10   11   12   13   >