Re: [PATCH v4 3/4] KEYS: Support for inserting a certificate into x86 bzImage

2017-04-27 Thread David Howells
Mehmet Kayaalp wrote: > + /* TODO: update CRC */ Is this bit missing? David

Re: [PATCH v4 3/4] KEYS: Support for inserting a certificate into x86 bzImage

2017-04-27 Thread David Howells
Mehmet Kayaalp wrote: > + /* TODO: update CRC */ Is this bit missing? David

Re: [PATCH] um: Fix to call read_initrd after init_bootmem

2017-04-27 Thread Richard Weinberger
Masami, Am 27.04.2017 um 05:15 schrieb Masami Hiramatsu: > Since read_initrd() invokes alloc_bootmem() for allocating > memory to load initrd image, it must be called after init_bootmem. > > This makes read_initrd() called directly from setup_arch() > after init_bootmem() and mem_total_pages().

Re: [PATCH] um: Fix to call read_initrd after init_bootmem

2017-04-27 Thread Richard Weinberger
Masami, Am 27.04.2017 um 05:15 schrieb Masami Hiramatsu: > Since read_initrd() invokes alloc_bootmem() for allocating > memory to load initrd image, it must be called after init_bootmem. > > This makes read_initrd() called directly from setup_arch() > after init_bootmem() and mem_total_pages().

Re: [PATCH v2] selftests/vm/run_vmtests: Fix wrong comment

2017-04-27 Thread Shuah Khan
On 04/13/2017 05:49 PM, SeongJae Park wrote: > A comment in `run_vmtests` is wrong because it is saying `128MB + 128MB > == 258MB`. This commit fixes the comment. > > Signed-off-by: SeongJae Park > --- > tools/testing/selftests/vm/run_vmtests | 2 +- > 1 file changed, 1

Re: [PATCH v2] selftests/vm/run_vmtests: Fix wrong comment

2017-04-27 Thread Shuah Khan
On 04/13/2017 05:49 PM, SeongJae Park wrote: > A comment in `run_vmtests` is wrong because it is saying `128MB + 128MB > == 258MB`. This commit fixes the comment. > > Signed-off-by: SeongJae Park > --- > tools/testing/selftests/vm/run_vmtests | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH v2] selftests/Makefile: Add missed PHONY targets

2017-04-27 Thread Shuah Khan
On 04/13/2017 05:47 PM, SeongJae Park wrote: > `selftests/Makefile` is defining only `install` as entire PHONY target > though there are few more PHONY targets including `run_tests`. This > commit defines them as the PHONY targets. > > Signed-off-by: SeongJae Park > --- >

Re: [PATCH v2] selftests/Makefile: Add missed PHONY targets

2017-04-27 Thread Shuah Khan
On 04/13/2017 05:47 PM, SeongJae Park wrote: > `selftests/Makefile` is defining only `install` as entire PHONY target > though there are few more PHONY targets including `run_tests`. This > commit defines them as the PHONY targets. > > Signed-off-by: SeongJae Park > --- >

Re: [PATCH v2] selftests/Makefile: Add missed closing `"` in comment

2017-04-27 Thread Shuah Khan
On 04/13/2017 05:43 PM, SeongJae Park wrote: > A comment for make command usage in `selftets/Makefile` has opening `"` > but no closing `"`. This commit adds the missed `"` in the comment. > > Signed-off-by: SeongJae Park > --- > tools/testing/selftests/Makefile | 2 +- >

Re: [PATCH v2] selftests/Makefile: Add missed closing `"` in comment

2017-04-27 Thread Shuah Khan
On 04/13/2017 05:43 PM, SeongJae Park wrote: > A comment for make command usage in `selftets/Makefile` has opening `"` > but no closing `"`. This commit adds the missed `"` in the comment. > > Signed-off-by: SeongJae Park > --- > tools/testing/selftests/Makefile | 2 +- > 1 file changed, 1

Re: [PATCH v2] selftests: gpio: add config fragment for gpio-mockup

2017-04-27 Thread Shuah Khan
On 04/19/2017 11:32 AM, Fathi Boudra wrote: > gentle ping > > On 4 April 2017 at 03:52, Bamvor Zhang Jian > wrote: >> Hi, >> >> On 31 March 2017 at 16:41, Fathi Boudra wrote: >>> The gpio test requires to insert the gpio mockup module >>>

Re: [PATCH v2] selftests: gpio: add config fragment for gpio-mockup

2017-04-27 Thread Shuah Khan
On 04/19/2017 11:32 AM, Fathi Boudra wrote: > gentle ping > > On 4 April 2017 at 03:52, Bamvor Zhang Jian > wrote: >> Hi, >> >> On 31 March 2017 at 16:41, Fathi Boudra wrote: >>> The gpio test requires to insert the gpio mockup module >>> (CONFIG_GPIO_MOCKUP). >>> The gpio mockup driver

Re: [PATCH v3] libnvdimm, region: sysfs trigger for nvdimm_flush()

2017-04-27 Thread Jeff Moyer
Dan Williams writes: > On Wed, Apr 26, 2017 at 1:38 PM, Jeff Moyer wrote: >> Dan Williams writes: >> >>> The nvdimm_flush() mechanism helps to reduce the impact of an ADR >>> (asynchronous-dimm-refresh) failure. The ADR

Re: [PATCH v3] libnvdimm, region: sysfs trigger for nvdimm_flush()

2017-04-27 Thread Jeff Moyer
Dan Williams writes: > On Wed, Apr 26, 2017 at 1:38 PM, Jeff Moyer wrote: >> Dan Williams writes: >> >>> The nvdimm_flush() mechanism helps to reduce the impact of an ADR >>> (asynchronous-dimm-refresh) failure. The ADR mechanism handles flushing >>> platform WPQ (write-pending-queue) buffers

Re: [PATCH 1/1] selftests: breakpoints: allow to cross-compile for aarch64/arm64

2017-04-27 Thread Shuah Khan
On 04/19/2017 11:31 AM, Fathi Boudra wrote: > gentle ping > > On 22 March 2017 at 20:04, Fathi Boudra wrote: >> To build breakpoint_test_arm64, ARCH value is only tested for "aarch64". >> It covers only the native build because it's computed from uname -m output. >> For

Re: [PATCH 1/1] selftests: breakpoints: allow to cross-compile for aarch64/arm64

2017-04-27 Thread Shuah Khan
On 04/19/2017 11:31 AM, Fathi Boudra wrote: > gentle ping > > On 22 March 2017 at 20:04, Fathi Boudra wrote: >> To build breakpoint_test_arm64, ARCH value is only tested for "aarch64". >> It covers only the native build because it's computed from uname -m output. >> For cross-compilation, ARCH

Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks

2017-04-27 Thread Michal Hocko
On Wed 26-04-17 18:29:08, Igor Stoppa wrote: [...] > If you prefer to have this patch only as part of the larger patchset, > I'm also fine with it. I agree that the situation is not ideal. If a larger set of changes would benefit from this change then it would clearly add arguments... > Also, if

Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks

2017-04-27 Thread Michal Hocko
On Wed 26-04-17 18:29:08, Igor Stoppa wrote: [...] > If you prefer to have this patch only as part of the larger patchset, > I'm also fine with it. I agree that the situation is not ideal. If a larger set of changes would benefit from this change then it would clearly add arguments... > Also, if

Re: [PATCH 0/3] Cavium ThunderX2 SMMUv3 errata workarounds

2017-04-27 Thread Robert Richter
On 27.04.17 17:16:21, Geetha sowjanya wrote: > From: Geetha > > Cavium CN99xx SMMUv3 implementation has two Silicon Erratas. > 1. Errata ID #74 >SMMU register alias Page 1 is not implemented > 2. Errata ID #126 >SMMU doesnt support unique IRQ lines for gerror, eventq

Re: [PATCH 0/3] Cavium ThunderX2 SMMUv3 errata workarounds

2017-04-27 Thread Robert Richter
On 27.04.17 17:16:21, Geetha sowjanya wrote: > From: Geetha > > Cavium CN99xx SMMUv3 implementation has two Silicon Erratas. > 1. Errata ID #74 >SMMU register alias Page 1 is not implemented > 2. Errata ID #126 >SMMU doesnt support unique IRQ lines for gerror, eventq and cmdq-sync > >

Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI

2017-04-27 Thread Petr Mladek
On Mon 2017-04-24 11:17:47, Sergey Senozhatsky wrote: > On (04/21/17 14:06), Petr Mladek wrote: > [..] > > > I agree that this_cpu_read(printk_context) covers slightly more than > > > logbuf_lock scope, so we may get positive this_cpu_read(printk_context) > > > with unlocked logbuf_lock, but I

Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI

2017-04-27 Thread Petr Mladek
On Mon 2017-04-24 11:17:47, Sergey Senozhatsky wrote: > On (04/21/17 14:06), Petr Mladek wrote: > [..] > > > I agree that this_cpu_read(printk_context) covers slightly more than > > > logbuf_lock scope, so we may get positive this_cpu_read(printk_context) > > > with unlocked logbuf_lock, but I

Re: [PATCH -mm -v10 1/3] mm, THP, swap: Delay splitting THP during swap out

2017-04-27 Thread Johannes Weiner
On Thu, Apr 27, 2017 at 03:12:34PM +0800, Huang, Ying wrote: > Minchan Kim writes: > > On Tue, Apr 25, 2017 at 08:56:56PM +0800, Huang, Ying wrote: > >> @@ -178,20 +192,12 @@ int add_to_swap(struct page *page, struct list_head > >> *list) > >>

Re: [PATCH -mm -v10 1/3] mm, THP, swap: Delay splitting THP during swap out

2017-04-27 Thread Johannes Weiner
On Thu, Apr 27, 2017 at 03:12:34PM +0800, Huang, Ying wrote: > Minchan Kim writes: > > On Tue, Apr 25, 2017 at 08:56:56PM +0800, Huang, Ying wrote: > >> @@ -178,20 +192,12 @@ int add_to_swap(struct page *page, struct list_head > >> *list) > >>VM_BUG_ON_PAGE(!PageLocked(page), page); > >>

Re: Question on ___GFP_NOLOCKDEP - Was: Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks

2017-04-27 Thread Michal Hocko
On Thu 27-04-17 15:16:47, Igor Stoppa wrote: > On 26/04/17 18:29, Igor Stoppa wrote: > > > On 26/04/17 17:47, Michal Hocko wrote: > > [...] > > >> Also the current mm tree has ___GFP_NOLOCKDEP which is not addressed > >> here so I suspect you have based your change on the Linus tree. > > > I

Re: Question on ___GFP_NOLOCKDEP - Was: Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks

2017-04-27 Thread Michal Hocko
On Thu 27-04-17 15:16:47, Igor Stoppa wrote: > On 26/04/17 18:29, Igor Stoppa wrote: > > > On 26/04/17 17:47, Michal Hocko wrote: > > [...] > > >> Also the current mm tree has ___GFP_NOLOCKDEP which is not addressed > >> here so I suspect you have based your change on the Linus tree. > > > I

Re: [REGRESSION next-20170426] Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices") causes oops in mvneta

2017-04-27 Thread Sricharan R
Hi, On 4/26/2017 9:45 PM, Ralph Sennhauser wrote: > Hi Sricharan R, > > Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time > for platform/amba/pci bus devices") causes a kernel panic as in the log > below on an armada-385. Reverting the commit fixes the issue. > > Regards >

Re: [REGRESSION next-20170426] Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices") causes oops in mvneta

2017-04-27 Thread Sricharan R
Hi, On 4/26/2017 9:45 PM, Ralph Sennhauser wrote: > Hi Sricharan R, > > Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time > for platform/amba/pci bus devices") causes a kernel panic as in the log > below on an armada-385. Reverting the commit fixes the issue. > > Regards >

Re: [PATCH 1/3] ARM: at91: pm: Add sama5d2 backup mode

2017-04-27 Thread Romain Izard
Hello Alexandre, This series might also be of interest for the linux-pm mailing list. 2017-04-26 18:04 GMT+02:00 Alexandre Belloni : > The sama5d2 has a mode were it is possible to cut power to the SoC while > keeping the RAM in self refresh. > Resuming from

Re: [PATCH 1/3] ARM: at91: pm: Add sama5d2 backup mode

2017-04-27 Thread Romain Izard
Hello Alexandre, This series might also be of interest for the linux-pm mailing list. 2017-04-26 18:04 GMT+02:00 Alexandre Belloni : > The sama5d2 has a mode were it is possible to cut power to the SoC while > keeping the RAM in self refresh. > Resuming from that mode needs support in the

Re: [PATCH v2 2/2] dmaengine: Add DW AXI DMAC driver

2017-04-27 Thread Andy Shevchenko
On Thu, 2017-04-27 at 13:21 +, Eugeniy Paltsev wrote: > On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote: > > On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote: > > > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote: > > > > On Mon, 2017-04-24 at 19:56 +0300, Andy

Re: [PATCH v2 2/2] dmaengine: Add DW AXI DMAC driver

2017-04-27 Thread Andy Shevchenko
On Thu, 2017-04-27 at 13:21 +, Eugeniy Paltsev wrote: > On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote: > > On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote: > > > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote: > > > > On Mon, 2017-04-24 at 19:56 +0300, Andy

[PATCH 1/2] iio: add hardware triggered operating mode

2017-04-27 Thread Benjamin Gaignard
Devices, like stm32 timer, could be triggered by hardware events which are not buffer or software events. However it could be necessary to validate the triggers like it is done for buffer or event triggered modes. This patch add a new INDIO_HARDWARE_TRIGGERED operating mode for this kind of

[PATCH 1/2] iio: add hardware triggered operating mode

2017-04-27 Thread Benjamin Gaignard
Devices, like stm32 timer, could be triggered by hardware events which are not buffer or software events. However it could be necessary to validate the triggers like it is done for buffer or event triggered modes. This patch add a new INDIO_HARDWARE_TRIGGERED operating mode for this kind of

[PATCH 2/2] iio: make stm32 trigger driver use INDIO_HARDWARE_TRIGGERED mode

2017-04-27 Thread Benjamin Gaignard
Add validate function to be use to use the correct trigger. Add an attribute to configure device mode like for quadrature and enable modes Signed-off-by: Benjamin Gaignard --- .../ABI/testing/sysfs-bus-iio-timer-stm32 | 15 ++

[PATCH 2/2] iio: make stm32 trigger driver use INDIO_HARDWARE_TRIGGERED mode

2017-04-27 Thread Benjamin Gaignard
Add validate function to be use to use the correct trigger. Add an attribute to configure device mode like for quadrature and enable modes Signed-off-by: Benjamin Gaignard --- .../ABI/testing/sysfs-bus-iio-timer-stm32 | 15 ++ drivers/iio/trigger/stm32-timer-trigger.c | 61

[PATCH 0/2]

2017-04-27 Thread Benjamin Gaignard
Those patches aim to complete stm32 timer features support. The last missing part is to be able to chain to timer blocks which mean that one of timerX's trigger could be used as clock for timerY. Since this operating is neither event or buffer triggered mode I would like to introduce a hardware

[PATCH 0/2]

2017-04-27 Thread Benjamin Gaignard
Those patches aim to complete stm32 timer features support. The last missing part is to be able to chain to timer blocks which mean that one of timerX's trigger could be used as clock for timerY. Since this operating is neither event or buffer triggered mode I would like to introduce a hardware

Re: [PATCH v5 01/10] arm64: allwinner: a64: enable RSB on A64

2017-04-27 Thread Maxime Ripard
On Wed, Apr 26, 2017 at 11:20:14PM +0800, Icenowy Zheng wrote: > Allwinner A64 have a RSB controller like the one on A23/A33 SoCs. > > Add it and its pinmux. > > Signed-off-by: Icenowy Zheng > Acked-by: Chen-Yu Tsai > --- > Changes in v2: > - Removed bonus

Re: [PATCH v5 01/10] arm64: allwinner: a64: enable RSB on A64

2017-04-27 Thread Maxime Ripard
On Wed, Apr 26, 2017 at 11:20:14PM +0800, Icenowy Zheng wrote: > Allwinner A64 have a RSB controller like the one on A23/A33 SoCs. > > Add it and its pinmux. > > Signed-off-by: Icenowy Zheng > Acked-by: Chen-Yu Tsai > --- > Changes in v2: > - Removed bonus properties in pio node. > - Added

Re: hwmon-NCT: Fine-tuning for four function implementations

2017-04-27 Thread SF Markus Elfring
Am 27.04.2017 um 14:50 schrieb Jean Delvare: > On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote: >> From: Markus Elfring >> Date: Thu, 27 Apr 2017 11:18:22 +0200 >> >> A few update suggestions were taken into account >> from static source code analysis.

Re: hwmon-NCT: Fine-tuning for four function implementations

2017-04-27 Thread SF Markus Elfring
Am 27.04.2017 um 14:50 schrieb Jean Delvare: > On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote: >> From: Markus Elfring >> Date: Thu, 27 Apr 2017 11:18:22 +0200 >> >> A few update suggestions were taken into account >> from static source code analysis. >> >> Markus Elfring (4): >>

Re: [PATCH v2 2/2] dmaengine: Add DW AXI DMAC driver

2017-04-27 Thread Eugeniy Paltsev
On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote: > On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote: > > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote: > > > On Mon, 2017-04-24 at 19:56 +0300, Andy Shevchenko wrote: > > > > On Mon, 2017-04-24 at 15:55 +, Eugeniy

Re: [PATCH v2 2/2] dmaengine: Add DW AXI DMAC driver

2017-04-27 Thread Eugeniy Paltsev
On Wed, 2017-04-26 at 18:04 +0300, Andy Shevchenko wrote: > On Tue, 2017-04-25 at 21:12 +0300, Andy Shevchenko wrote: > > On Tue, 2017-04-25 at 15:16 +, Eugeniy Paltsev wrote: > > > On Mon, 2017-04-24 at 19:56 +0300, Andy Shevchenko wrote: > > > > On Mon, 2017-04-24 at 15:55 +, Eugeniy

Re: xen_exit_mmap() questions

2017-04-27 Thread Boris Ostrovsky
> Also, this code in drop_other_mm_ref() looks dubious to me: > > /* If this cpu still has a stale cr3 reference, then make sure >it has been flushed. */ > if (this_cpu_read(xen_current_cr3) == __pa(mm->pgd)) > load_cr3(swapper_pg_dir); >

Re: xen_exit_mmap() questions

2017-04-27 Thread Boris Ostrovsky
> Also, this code in drop_other_mm_ref() looks dubious to me: > > /* If this cpu still has a stale cr3 reference, then make sure >it has been flushed. */ > if (this_cpu_read(xen_current_cr3) == __pa(mm->pgd)) > load_cr3(swapper_pg_dir); >

Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction

2017-04-27 Thread Djalal Harouni
On Thu, Apr 27, 2017 at 4:07 AM, Rusty Russell wrote: > Djalal Harouni writes: >> Hi Rusty, >> >> On Mon, Apr 24, 2017 at 6:29 AM, Rusty Russell wrote: >>> Djalal Harouni writes: When value is (1), task must

Re: [PATCH v3 2/2] modules:capabilities: add a per-task modules autoload restriction

2017-04-27 Thread Djalal Harouni
On Thu, Apr 27, 2017 at 4:07 AM, Rusty Russell wrote: > Djalal Harouni writes: >> Hi Rusty, >> >> On Mon, Apr 24, 2017 at 6:29 AM, Rusty Russell wrote: >>> Djalal Harouni writes: When value is (1), task must have CAP_SYS_MODULE to be able to trigger a module auto-load operation, or

Re: [PATCH net-next] mlx5: work around unused function warning

2017-04-27 Thread Leon Romanovsky
On Thu, Apr 27, 2017 at 02:04:15PM +0200, Arnd Bergmann wrote: > On Thu, Apr 27, 2017 at 1:55 PM, Leon Romanovsky wrote: > > On Thu, Apr 27, 2017 at 01:04:02PM +0200, Arnd Bergmann wrote: > >> The previous patch addressed a sparse warning but replaced it with a > >> compiler

Re: [PATCH net-next] mlx5: work around unused function warning

2017-04-27 Thread Leon Romanovsky
On Thu, Apr 27, 2017 at 02:04:15PM +0200, Arnd Bergmann wrote: > On Thu, Apr 27, 2017 at 1:55 PM, Leon Romanovsky wrote: > > On Thu, Apr 27, 2017 at 01:04:02PM +0200, Arnd Bergmann wrote: > >> The previous patch addressed a sparse warning but replaced it with a > >> compiler warning when

Re: [PATCH] drm/rockchip: Set line flag config register in vop_crtc_enable

2017-04-27 Thread Sean Paul
On Thu, Apr 27, 2017 at 03:00:29PM +0800, Mark yao wrote: > On 2017年04月27日 14:54, Jeffy Chen wrote: > > We need to set vop config done after update line flag config, it's a > > new requirement for chips newer than rk3368. > > > > Since we would only use line flag irq for vact_end, let's move it

Re: [PATCH] drm/rockchip: Set line flag config register in vop_crtc_enable

2017-04-27 Thread Sean Paul
On Thu, Apr 27, 2017 at 03:00:29PM +0800, Mark yao wrote: > On 2017年04月27日 14:54, Jeffy Chen wrote: > > We need to set vop config done after update line flag config, it's a > > new requirement for chips newer than rk3368. > > > > Since we would only use line flag irq for vact_end, let's move it

Re: [PATCH v1 8/8] ACPI: Use recently introduced uuid_le_cmp_p{p}() helpers

2017-04-27 Thread Andy Shevchenko
On Thu, 2017-04-27 at 14:46 +0200, Borislav Petkov wrote: > On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote: > > >  #ifdef CONFIG_ACPI_APEI_PCIEAER > > > - else if (!uuid_le_cmp(*(uuid_le *)gdata- > > > >section_type, > > > -   CPER_SEC_PCIE))

Re: [PATCH v1 8/8] ACPI: Use recently introduced uuid_le_cmp_p{p}() helpers

2017-04-27 Thread Andy Shevchenko
On Thu, 2017-04-27 at 14:46 +0200, Borislav Petkov wrote: > On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote: > > >  #ifdef CONFIG_ACPI_APEI_PCIEAER > > > - else if (!uuid_le_cmp(*(uuid_le *)gdata- > > > >section_type, > > > -   CPER_SEC_PCIE))

[PATCH 2/2] usb: dwc2: Use common polling function.

2017-04-27 Thread Sevak Arakelyan
Replace all the parts of register polling code with dwc2_hsotg_wait_bit_set function calls. Signed-off-by: Sevak Arakelyan --- drivers/usb/dwc2/core.c | 61 +-- drivers/usb/dwc2/gadget.c | 24 ---

[PATCH 2/2] usb: dwc2: Use common polling function.

2017-04-27 Thread Sevak Arakelyan
Replace all the parts of register polling code with dwc2_hsotg_wait_bit_set function calls. Signed-off-by: Sevak Arakelyan --- drivers/usb/dwc2/core.c | 61 +-- drivers/usb/dwc2/gadget.c | 24 --- drivers/usb/dwc2/hcd.c| 18

[PATCH 1/2] usb: dwc2: Move polling function to core.c.

2017-04-27 Thread Sevak Arakelyan
Move polling function to core.c so it can be used anywhere in the code. Signed-off-by: Sevak Arakelyan --- drivers/usb/dwc2/core.c | 23 +++ drivers/usb/dwc2/core.h | 4 drivers/usb/dwc2/gadget.c | 14 -- 3 files changed, 27

[PATCH 1/2] usb: dwc2: Move polling function to core.c.

2017-04-27 Thread Sevak Arakelyan
Move polling function to core.c so it can be used anywhere in the code. Signed-off-by: Sevak Arakelyan --- drivers/usb/dwc2/core.c | 23 +++ drivers/usb/dwc2/core.h | 4 drivers/usb/dwc2/gadget.c | 14 -- 3 files changed, 27 insertions(+), 14

[PATCH 0/2] usb: dwc2: Replace polling code with function calls

2017-04-27 Thread Sevak Arakelyan
This series moves dwc2_hsotg_wait_bit_set polling function to core.c and replaces all the register polling parts of code with function calls Tested on HAPS platform with DWC_hsotg IP version 3.30a. Sevak Arakelyan (2): usb: dwc2: Move polling function to core.c. usb: dwc2: Use common

[PATCH 0/2] usb: dwc2: Replace polling code with function calls

2017-04-27 Thread Sevak Arakelyan
This series moves dwc2_hsotg_wait_bit_set polling function to core.c and replaces all the register polling parts of code with function calls Tested on HAPS platform with DWC_hsotg IP version 3.30a. Sevak Arakelyan (2): usb: dwc2: Move polling function to core.c. usb: dwc2: Use common

Re: [PATCH 1/3] arm64: Add MIDR values for Cavium cn99xx SoCs

2017-04-27 Thread Jayachandran C.
On Thu, Apr 27, 2017 at 5:16 PM, Geetha sowjanya wrote: > From: Geetha > > Add MIDR values for Cavium cn99xx SoCs > > Signed-off-by: Geetha > --- > arch/arm64/include/asm/cputype.h | 3 +++ > 1 file changed, 3 insertions(+) > >

Re: [PATCH 1/3] arm64: Add MIDR values for Cavium cn99xx SoCs

2017-04-27 Thread Jayachandran C.
On Thu, Apr 27, 2017 at 5:16 PM, Geetha sowjanya wrote: > From: Geetha > > Add MIDR values for Cavium cn99xx SoCs > > Signed-off-by: Geetha > --- > arch/arm64/include/asm/cputype.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/arch/arm64/include/asm/cputype.h >

Re: [PATCH] plugin python: Adjust the handling after PyRun_String() failed

2017-04-27 Thread Taeung Song
On 04/27/2017 08:30 PM, Steven Rostedt wrote: On Thu, 27 Apr 2017 11:52:14 +0900 Taeung Song wrote: On 04/27/2017 11:47 AM, Steven Rostedt wrote: On Thu, 27 Apr 2017 08:46:21 +0900 Taeung Song wrote: Even though PyRun_String() failed,

Re: [PATCH] plugin python: Adjust the handling after PyRun_String() failed

2017-04-27 Thread Taeung Song
On 04/27/2017 08:30 PM, Steven Rostedt wrote: On Thu, 27 Apr 2017 11:52:14 +0900 Taeung Song wrote: On 04/27/2017 11:47 AM, Steven Rostedt wrote: On Thu, 27 Apr 2017 08:46:21 +0900 Taeung Song wrote: Even though PyRun_String() failed, just 0 will be returned but we need to return -1

Re: [PATCH 0/4] hwmon-NCT: Fine-tuning for four function implementations

2017-04-27 Thread Jean Delvare
On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 27 Apr 2017 11:18:22 +0200 > > A few update suggestions were taken into account > from static source code analysis. > > Markus Elfring (4): > Use devm_kcalloc() in

Re: [PATCH 0/4] hwmon-NCT: Fine-tuning for four function implementations

2017-04-27 Thread Jean Delvare
On Thu, 27 Apr 2017 11:27:21 +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 27 Apr 2017 11:18:22 +0200 > > A few update suggestions were taken into account > from static source code analysis. > > Markus Elfring (4): > Use devm_kcalloc() in nct6683_create_attr_group() >

Re: [PATCH v1 8/8] ACPI: Use recently introduced uuid_le_cmp_p{p}() helpers

2017-04-27 Thread Borislav Petkov
On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote: > > #ifdef CONFIG_ACPI_APEI_PCIEAER > > - else if (!uuid_le_cmp(*(uuid_le *)gdata->section_type, > > - CPER_SEC_PCIE)) { > > + else if (!uuid_le_cmp_p(sec_type, CPER_SEC_PCIE)) {

Re: [PATCH v1 8/8] ACPI: Use recently introduced uuid_le_cmp_p{p}() helpers

2017-04-27 Thread Borislav Petkov
On Fri, Apr 21, 2017 at 11:22:31PM +0200, Rafael J. Wysocki wrote: > > #ifdef CONFIG_ACPI_APEI_PCIEAER > > - else if (!uuid_le_cmp(*(uuid_le *)gdata->section_type, > > - CPER_SEC_PCIE)) { > > + else if (!uuid_le_cmp_p(sec_type, CPER_SEC_PCIE)) {

Re: [PATCH v3 09/29] x86: assembly, use DATA_SIMPLE for data

2017-04-27 Thread Pavel Machek
On Thu 2017-04-27 14:30:05, Jiri Slaby wrote: > Hi, > > On 04/27/2017, 01:53 PM, Pavel Machek wrote: > >> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel) > >> > >> .data > >> ALIGN > >> -ENTRY(saved_magic).long 0 > >> -ENTRY(saved_eip) .long 0 > >> +SYM_DATA_SIMPLE(saved_magic,

Re: [PATCH v3 09/29] x86: assembly, use DATA_SIMPLE for data

2017-04-27 Thread Pavel Machek
On Thu 2017-04-27 14:30:05, Jiri Slaby wrote: > Hi, > > On 04/27/2017, 01:53 PM, Pavel Machek wrote: > >> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel) > >> > >> .data > >> ALIGN > >> -ENTRY(saved_magic).long 0 > >> -ENTRY(saved_eip) .long 0 > >> +SYM_DATA_SIMPLE(saved_magic,

[PATCH 1/2] f2fs: allow cpc->reason to indicate more than one reason

2017-04-27 Thread Chao Yu
Change to use different bits of cpc->reason to indicate different status, so cpc->reason can indicate more than one reason. Signed-off-by: Chao Yu --- fs/f2fs/checkpoint.c | 14 +++--- fs/f2fs/f2fs.h | 16 +++- fs/f2fs/segment.c| 8 3

[PATCH 1/2] f2fs: allow cpc->reason to indicate more than one reason

2017-04-27 Thread Chao Yu
Change to use different bits of cpc->reason to indicate different status, so cpc->reason can indicate more than one reason. Signed-off-by: Chao Yu --- fs/f2fs/checkpoint.c | 14 +++--- fs/f2fs/f2fs.h | 16 +++- fs/f2fs/segment.c| 8 3 files changed, 18

Re: [PATCH v2 0/3] efi: add support for non-standard capsule headers

2017-04-27 Thread Ard Biesheuvel
On 27 April 2017 at 13:46, Bryan O'Donoghue wrote: > On 25/04/17 16:08, Ard Biesheuvel wrote: >> >> On 25 April 2017 at 16:07, Bryan O'Donoghue >>> >>> I'm OOO until Thursday however, I could test this out on a Galileo for >>> you with the CSH stripped out. As Jan

Re: [PATCH v2 0/3] efi: add support for non-standard capsule headers

2017-04-27 Thread Ard Biesheuvel
On 27 April 2017 at 13:46, Bryan O'Donoghue wrote: > On 25/04/17 16:08, Ard Biesheuvel wrote: >> >> On 25 April 2017 at 16:07, Bryan O'Donoghue >>> >>> I'm OOO until Thursday however, I could test this out on a Galileo for >>> you with the CSH stripped out. As Jan has pointed out Galileo aka

[PATCH 2/2] f2fs: introduce CP_TRIMMED_FLAG to avoid unneeded discard

2017-04-27 Thread Chao Yu
Introduce CP_TRIMMED_FLAG to indicate all invalid block were trimmed before umount, so once we do mount with image which contain the flag, we don't record invalid blocks as undiscard one, when fstrim is being triggered, we can avoid issuing redundant discard commands. Signed-off-by: Chao Yu

[PATCH 2/2] f2fs: introduce CP_TRIMMED_FLAG to avoid unneeded discard

2017-04-27 Thread Chao Yu
Introduce CP_TRIMMED_FLAG to indicate all invalid block were trimmed before umount, so once we do mount with image which contain the flag, we don't record invalid blocks as undiscard one, when fstrim is being triggered, we can avoid issuing redundant discard commands. Signed-off-by: Chao Yu ---

Re: [PATCH v2 0/3] efi: add support for non-standard capsule headers

2017-04-27 Thread Bryan O'Donoghue
On 25/04/17 16:08, Ard Biesheuvel wrote: On 25 April 2017 at 16:07, Bryan O'Donoghue I'm OOO until Thursday however, I could test this out on a Galileo for you with the CSH stripped out. As Jan has pointed out Galileo aka Quark x1000 non-secure (not to be called insecure) will just skips past

Re: [PATCH v2 0/3] efi: add support for non-standard capsule headers

2017-04-27 Thread Bryan O'Donoghue
On 25/04/17 16:08, Ard Biesheuvel wrote: On 25 April 2017 at 16:07, Bryan O'Donoghue I'm OOO until Thursday however, I could test this out on a Galileo for you with the CSH stripped out. As Jan has pointed out Galileo aka Quark x1000 non-secure (not to be called insecure) will just skips past

Re: TREE_SRCU slows hotplug by factor ~16

2017-04-27 Thread Paul E. McKenney
On Thu, Apr 27, 2017 at 07:44:00AM +0200, Mike Galbraith wrote: > On Wed, 2017-04-26 at 22:32 -0700, Paul E. McKenney wrote: > > On Thu, Apr 27, 2017 at 06:15:56AM +0200, Mike Galbraith wrote: > > > On Wed, 2017-04-26 at 21:11 -0700, Paul E. McKenney wrote: > > > > > > > This is with

Re: TREE_SRCU slows hotplug by factor ~16

2017-04-27 Thread Paul E. McKenney
On Thu, Apr 27, 2017 at 07:44:00AM +0200, Mike Galbraith wrote: > On Wed, 2017-04-26 at 22:32 -0700, Paul E. McKenney wrote: > > On Thu, Apr 27, 2017 at 06:15:56AM +0200, Mike Galbraith wrote: > > > On Wed, 2017-04-26 at 21:11 -0700, Paul E. McKenney wrote: > > > > > > > This is with

Re: [PATCH v8 1/3] backlight arcxcnn add arc to vendor prefix

2017-04-27 Thread Geert Uytterhoeven
On Tue, Apr 25, 2017 at 6:36 PM, Jingoo Han wrote: > On Monday, April 24, 2017 1:56 PM, Olimpiu Dejeu wrote: >> >> On Mon, April 24, 2017 11:10 AM, Rob Herring < r...@kernel.org> wrote: >> >> > On Wed, Mar 15, 2017 at 2:45 PM, Olimpiu Dejeu >> wrote:

Re: [PATCH v8 1/3] backlight arcxcnn add arc to vendor prefix

2017-04-27 Thread Geert Uytterhoeven
On Tue, Apr 25, 2017 at 6:36 PM, Jingoo Han wrote: > On Monday, April 24, 2017 1:56 PM, Olimpiu Dejeu wrote: >> >> On Mon, April 24, 2017 11:10 AM, Rob Herring < r...@kernel.org> wrote: >> >> > On Wed, Mar 15, 2017 at 2:45 PM, Olimpiu Dejeu >> wrote: >> >> backlight: Add arc to vendor prefixes

Re: [PATCH v2 9/9] KVM: mark requests that need synchronization

2017-04-27 Thread Paolo Bonzini
On 26/04/2017 22:32, Radim Krčmář wrote: > v2: replaces [v1 1/6] > Ugh, KVM_ARCH_REQ_WAIT_NO_WAKEUP looks a weird ... Yeah, let's drop patch 7 and just use bits for now. I think using KVM_ARCH_REQ_FLAGS directly should be fine, especially after the default is flipped from "no wakeup" to

Re: [PATCH v2 9/9] KVM: mark requests that need synchronization

2017-04-27 Thread Paolo Bonzini
On 26/04/2017 22:32, Radim Krčmář wrote: > v2: replaces [v1 1/6] > Ugh, KVM_ARCH_REQ_WAIT_NO_WAKEUP looks a weird ... Yeah, let's drop patch 7 and just use bits for now. I think using KVM_ARCH_REQ_FLAGS directly should be fine, especially after the default is flipped from "no wakeup" to

Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

2017-04-27 Thread One Thousand Gnomes
> > Which is the sudo case and why sudo uses a separate pty/tty pair as it's > > not just TIOCSTI that's an issue but there are a load of ioctls that do > > things like cause signals to the process or are just annoying - > > vhangup(), changing the speed etc > > > > (And for console changing the

Re: [PATCH v5 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

2017-04-27 Thread One Thousand Gnomes
> > Which is the sudo case and why sudo uses a separate pty/tty pair as it's > > not just TIOCSTI that's an issue but there are a load of ioctls that do > > things like cause signals to the process or are just annoying - > > vhangup(), changing the speed etc > > > > (And for console changing the

[PATCH] arm64: Print DT machine model in setup_machine_fdt()

2017-04-27 Thread Geert Uytterhoeven
On arm32, the machine model specified in the device tree is printed during boot-up, courtesy of of_flat_dt_match_machine(). On arm64, of_flat_dt_match_machine() is not called, and the machine model information is not available from the kernel log. Print the machine model to make it easier to

Re: [PATCH 1/2] drm: Introduce crtc->mode_valid() callback

2017-04-27 Thread Jose Abreu
Hi Andrzej, Thanks for your answer! On 27-04-2017 11:05, Andrzej Hajda wrote: > Hi Jose, > > On 26.04.2017 12:48, Jose Abreu wrote: >> Some crtc's may have restrictions in the mode they can display. In >> this patch a new callback (crtc->mode_valid()) is introduced that >> is called at the

[PATCH] arm64: Print DT machine model in setup_machine_fdt()

2017-04-27 Thread Geert Uytterhoeven
On arm32, the machine model specified in the device tree is printed during boot-up, courtesy of of_flat_dt_match_machine(). On arm64, of_flat_dt_match_machine() is not called, and the machine model information is not available from the kernel log. Print the machine model to make it easier to

Re: [PATCH 1/2] drm: Introduce crtc->mode_valid() callback

2017-04-27 Thread Jose Abreu
Hi Andrzej, Thanks for your answer! On 27-04-2017 11:05, Andrzej Hajda wrote: > Hi Jose, > > On 26.04.2017 12:48, Jose Abreu wrote: >> Some crtc's may have restrictions in the mode they can display. In >> this patch a new callback (crtc->mode_valid()) is introduced that >> is called at the

[PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy

2017-04-27 Thread Kirill Tkhai
On implementing of nested pid namespaces support in CRIU (checkpoint-restore in userspace tool) we run into the situation, that it's impossible to create a task with specific NSpid effectively. After commit 49f4d8b93ccf "pidns: Capture the user namespace and filter ns_last_pid" it is impossible to

[PATCH v3] pid_ns: Introduce ioctl to set vector of ns_last_pid's on ns hierarhy

2017-04-27 Thread Kirill Tkhai
On implementing of nested pid namespaces support in CRIU (checkpoint-restore in userspace tool) we run into the situation, that it's impossible to create a task with specific NSpid effectively. After commit 49f4d8b93ccf "pidns: Capture the user namespace and filter ns_last_pid" it is impossible to

Re: [patch V2 00/24] cpu/hotplug: Convert get_online_cpus() to a percpu_rwsem

2017-04-27 Thread Mark Rutland
On Thu, Apr 27, 2017 at 12:01:57PM +0200, Thomas Gleixner wrote: > On Thu, 27 Apr 2017, Mark Rutland wrote: > > > On Thu, Apr 27, 2017 at 10:27:20AM +0200, Sebastian Siewior wrote: > > > On 2017-04-26 11:32:36 [+0100], Mark Rutland wrote: > > > > > So we could end up calling

Re: [patch V2 00/24] cpu/hotplug: Convert get_online_cpus() to a percpu_rwsem

2017-04-27 Thread Mark Rutland
On Thu, Apr 27, 2017 at 12:01:57PM +0200, Thomas Gleixner wrote: > On Thu, 27 Apr 2017, Mark Rutland wrote: > > > On Thu, Apr 27, 2017 at 10:27:20AM +0200, Sebastian Siewior wrote: > > > On 2017-04-26 11:32:36 [+0100], Mark Rutland wrote: > > > > > So we could end up calling

Re: [PATCH v3 09/29] x86: assembly, use DATA_SIMPLE for data

2017-04-27 Thread Jiri Slaby
Hi, On 04/27/2017, 01:53 PM, Pavel Machek wrote: >> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel) >> >> .data >> ALIGN >> -ENTRY(saved_magic) .long 0 >> -ENTRY(saved_eip).long 0 >> +SYM_DATA_SIMPLE(saved_magic, .long 0) >> +SYM_DATA_SIMPLE_LOCAL(saved_eip, .long 0) >> >> #

Re: [PATCH v3 09/29] x86: assembly, use DATA_SIMPLE for data

2017-04-27 Thread Jiri Slaby
Hi, On 04/27/2017, 01:53 PM, Pavel Machek wrote: >> @@ -91,11 +91,11 @@ ENDPROC(do_suspend_lowlevel) >> >> .data >> ALIGN >> -ENTRY(saved_magic) .long 0 >> -ENTRY(saved_eip).long 0 >> +SYM_DATA_SIMPLE(saved_magic, .long 0) >> +SYM_DATA_SIMPLE_LOCAL(saved_eip, .long 0) >> >> #

[PATCH 2/2] input: touchscreen: ar1021_i2c: replace magic number with definition

2017-04-27 Thread Martin Kepplinger
We now have a few of this device's definitions. Let's avoid magic numbers and use them. Signed-off-by: Martin Kepplinger --- drivers/input/touchscreen/ar1021_i2c.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/2] input: touchscreen: ar1021_i2c: replace magic number with definition

2017-04-27 Thread Martin Kepplinger
We now have a few of this device's definitions. Let's avoid magic numbers and use them. Signed-off-by: Martin Kepplinger --- drivers/input/touchscreen/ar1021_i2c.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/touchscreen/ar1021_i2c.c

[PATCH 1/2] input: touchscreen: ar1021_i2c: enable touch mode during open

2017-04-27 Thread Martin Kepplinger
The device could as well be in command mode, in which this driver cannot handle the device. When opening the device, let's make sure the device will be in the mode we expect it to be for this driver. Signed-off-by: Martin Kepplinger ---

[PATCH 1/2] input: touchscreen: ar1021_i2c: enable touch mode during open

2017-04-27 Thread Martin Kepplinger
The device could as well be in command mode, in which this driver cannot handle the device. When opening the device, let's make sure the device will be in the mode we expect it to be for this driver. Signed-off-by: Martin Kepplinger --- drivers/input/touchscreen/ar1021_i2c.c | 15

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