Re: [PATCH net-next 0/5] refine virtio-net XDP

On Tue, Jul 18, 2017 at 11:24:42AM -0700, David Miller wrote: > From: Jason Wang > Date: Mon, 17 Jul 2017 20:43:56 +0800 > > > This series brings two optimizations for virtio-net XDP: > > > > - avoid reset during XDP set > > - turn off offloads on demand > > > > Please

Re: [PATCH net-next 0/5] refine virtio-net XDP

On Tue, Jul 18, 2017 at 11:24:42AM -0700, David Miller wrote: > From: Jason Wang > Date: Mon, 17 Jul 2017 20:43:56 +0800 > > > This series brings two optimizations for virtio-net XDP: > > > > - avoid reset during XDP set > > - turn off offloads on demand > > > > Please review. > > Michael,

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On Tue, Jul 18, 2017 at 01:54:56PM -0400, Tejun Heo wrote: > Okay, we're kinda off the rails now. Just to verify that we're on the > same page, are you also saying that the following should be a valid > configuration? > > R (D) > | > A (D and has processes in it and

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On Tue, Jul 18, 2017 at 01:54:56PM -0400, Tejun Heo wrote: > Okay, we're kinda off the rails now. Just to verify that we're on the > same page, are you also saying that the following should be a valid > configuration? > > R (D) > | > A (D and has processes in it and

Re: [PATCH] kbuild: modpost: Warn about references from rodata to __init text

2017-07-01 7:58 GMT+09:00 Stephen Boyd : > If we have a structure that's marked const it will be placed > into the .rodata section but it could reference an init section > function. Include the read only data section in the check we have > for read/write data sections

Re: [PATCH] kbuild: modpost: Warn about references from rodata to __init text

2017-07-01 7:58 GMT+09:00 Stephen Boyd : > If we have a structure that's marked const it will be placed > into the .rodata section but it could reference an init section > function. Include the read only data section in the check we have > for read/write data sections referencing init sections so

[PATCH v2] staging: wlan-ng: Fix endianness warnings

These variables were set to u16 and u32 although they always hold a little endian value. This patch fixes multiple sparse warnings like: drivers/staging/wlan-ng/prism2sta.c:375:46: warning: cast to restricted __le16 Signed-off-by: Alfonso Lima Astor --- v2:

[PATCH v2] staging: wlan-ng: Fix endianness warnings

These variables were set to u16 and u32 although they always hold a little endian value. This patch fixes multiple sparse warnings like: drivers/staging/wlan-ng/prism2sta.c:375:46: warning: cast to restricted __le16 Signed-off-by: Alfonso Lima Astor --- v2: Resubmit patch that wouldn't

Re: [PATCH] atm: zatm: Fix an error handling path in 'zatm_init_one()'

From: Christophe JAILLET Date: Mon, 17 Jul 2017 19:42:41 +0200 > If 'dma_set_mask_and_coherent()' fails, we must undo the previous > 'pci_request_regions()' call. > Adjust corresponding 'goto' to jump at the right place of the error > handling path. > >

Re: [PATCH] atm: zatm: Fix an error handling path in 'zatm_init_one()'

From: Christophe JAILLET Date: Mon, 17 Jul 2017 19:42:41 +0200 > If 'dma_set_mask_and_coherent()' fails, we must undo the previous > 'pci_request_regions()' call. > Adjust corresponding 'goto' to jump at the right place of the error > handling path. > > Signed-off-by: Christophe JAILLET

Re: [PATCH] workqueue: doc change for ST behavior on NUMA systems

On Tue, Jul 18, 2017 at 11:12:53AM -0700, Alexei Potashnik wrote: > NUMA rework of workqueue made the combination of max_active of 1 and > WQ_UNBOUND insufficient to guarantee ST behavior system wide. > > alloc_ordered_queue should now be used instead. > > Signed-off-by: Alexei Potashnik

Re: [PATCH] workqueue: doc change for ST behavior on NUMA systems

On Tue, Jul 18, 2017 at 11:12:53AM -0700, Alexei Potashnik wrote: > NUMA rework of workqueue made the combination of max_active of 1 and > WQ_UNBOUND insufficient to guarantee ST behavior system wide. > > alloc_ordered_queue should now be used instead. > > Signed-off-by: Alexei Potashnik Patch

[tip:x86/mm] x86/mm: Add support to make use of Secure Memory Encryption

Commit-ID: aca20d5462149333ba8b24a4a352be5b7a00dfd2 Gitweb: http://git.kernel.org/tip/aca20d5462149333ba8b24a4a352be5b7a00dfd2 Author: Tom Lendacky AuthorDate: Mon, 17 Jul 2017 16:10:35 -0500 Committer: Ingo Molnar CommitDate: Tue, 18 Jul 2017

[tip:x86/mm] x86/mm: Add support to make use of Secure Memory Encryption

Commit-ID: aca20d5462149333ba8b24a4a352be5b7a00dfd2 Gitweb: http://git.kernel.org/tip/aca20d5462149333ba8b24a4a352be5b7a00dfd2 Author: Tom Lendacky AuthorDate: Mon, 17 Jul 2017 16:10:35 -0500 Committer: Ingo Molnar CommitDate: Tue, 18 Jul 2017 20:23:26 +0200 x86/mm: Add support to

[tip:x86/mm] compiler-gcc.h: Introduce __nostackprotector function attribute

Commit-ID: 7375ae3a0b79ea072f4c672039f08f5db633b9e1 Gitweb: http://git.kernel.org/tip/7375ae3a0b79ea072f4c672039f08f5db633b9e1 Author: Tom Lendacky AuthorDate: Mon, 17 Jul 2017 16:10:34 -0500 Committer: Ingo Molnar CommitDate: Tue, 18 Jul 2017

[tip:x86/mm] compiler-gcc.h: Introduce __nostackprotector function attribute

Commit-ID: 7375ae3a0b79ea072f4c672039f08f5db633b9e1 Gitweb: http://git.kernel.org/tip/7375ae3a0b79ea072f4c672039f08f5db633b9e1 Author: Tom Lendacky AuthorDate: Mon, 17 Jul 2017 16:10:34 -0500 Committer: Ingo Molnar CommitDate: Tue, 18 Jul 2017 20:23:20 +0200 compiler-gcc.h: Introduce

[PATCH v6] MIPS: NI 169445 board support

Support the National Instruments 169445 board. Signed-off-by: Nathan Sullivan --- Changes since v5: - make device tree addresses on the internal bus relative, and compile with W=2 to be sure they are in the right format. Documentation/devicetree/bindings/mips/ni.txt

[PATCH v6] MIPS: NI 169445 board support

Support the National Instruments 169445 board. Signed-off-by: Nathan Sullivan --- Changes since v5: - make device tree addresses on the internal bus relative, and compile with W=2 to be sure they are in the right format. Documentation/devicetree/bindings/mips/ni.txt | 7 ++ MAINTAINERS

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Tue, 2017-07-18 at 20:55 +0300, Andy Shevchenko wrote: > On Tue, 2017-07-18 at 10:50 -0700, Joe Perches wrote: > > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > > > Recently I have noticed too many users of struct rtc_time that > > > printing > > > its content field by field. > >

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Tue, 2017-07-18 at 20:55 +0300, Andy Shevchenko wrote: > On Tue, 2017-07-18 at 10:50 -0700, Joe Perches wrote: > > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > > > Recently I have noticed too many users of struct rtc_time that > > > printing > > > its content field by field. > >

Re: [PATCH] bcma: gpio: Correct number of GPIOs for BCM53573

On 06/30/2017 02:37 PM, Rafał Miłecki wrote: > On 30 June 2017 at 21:02, Florian Fainelli wrote: >> Broadcom BCM53573 SoCs actually have 32 GPIOs, and not 16. >> >> Fixes: 3f37ec79dd21 ("bcma: support BCM53573 series of wireless SoCs") >> Signed-off-by: Florian Fainelli

Re: [PATCH] bcma: gpio: Correct number of GPIOs for BCM53573

On 06/30/2017 02:37 PM, Rafał Miłecki wrote: > On 30 June 2017 at 21:02, Florian Fainelli wrote: >> Broadcom BCM53573 SoCs actually have 32 GPIOs, and not 16. >> >> Fixes: 3f37ec79dd21 ("bcma: support BCM53573 series of wireless SoCs") >> Signed-off-by: Florian Fainelli > > Looks good. Is

Re: [PATCH net-next 0/5] refine virtio-net XDP

From: Jason Wang Date: Mon, 17 Jul 2017 20:43:56 +0800 > This series brings two optimizations for virtio-net XDP: > > - avoid reset during XDP set > - turn off offloads on demand > > Please review. Michael, please review Jason's changes. Thanks.

Re: [PATCH net-next 0/5] refine virtio-net XDP

From: Jason Wang Date: Mon, 17 Jul 2017 20:43:56 +0800 > This series brings two optimizations for virtio-net XDP: > > - avoid reset during XDP set > - turn off offloads on demand > > Please review. Michael, please review Jason's changes. Thanks.

Re: [PATCH] ipv4: ipv6: initialize treq->txhash in cookie_v[46]_check()

From: Alexander Potapenko Date: Mon, 17 Jul 2017 12:35:58 +0200 > KMSAN reported use of uninitialized memory in skb_set_hash_from_sk(), > which originated from the TCP request socket created in > cookie_v6_check(): ... > Similar error is reported for cookie_v4_check(). > >

Re: [PATCH] ipv4: ipv6: initialize treq->txhash in cookie_v[46]_check()

From: Alexander Potapenko Date: Mon, 17 Jul 2017 12:35:58 +0200 > KMSAN reported use of uninitialized memory in skb_set_hash_from_sk(), > which originated from the TCP request socket created in > cookie_v6_check(): ... > Similar error is reported for cookie_v4_check(). > > Signed-off-by:

Re: [PATCH 1/7] signal/alpha: Document a conflict with SI_USER for SIGTRAP

On 07/18/2017 04:06 AM, Eric W. Biederman wrote: Setting si_code to __SI_FAULT results in a userspace seeing an si_code of 0. This is the same si_code as SI_USER. Posix and common sense requires that SI_USER not be a signal specific si_code. As such this use of 0 for the si_code is a pretty

Re: [PATCH 1/7] signal/alpha: Document a conflict with SI_USER for SIGTRAP

On 07/18/2017 04:06 AM, Eric W. Biederman wrote: Setting si_code to __SI_FAULT results in a userspace seeing an si_code of 0. This is the same si_code as SI_USER. Posix and common sense requires that SI_USER not be a signal specific si_code. As such this use of 0 for the si_code is a pretty

Re: [PATCH v2 3/4] btrfs: Add zstd support

On Thu, Jun 29, 2017 at 12:41:07PM -0700, Nick Terrell wrote: > +static void zstd_free_workspace(struct list_head *ws) > +{ > + struct workspace *workspace = list_entry(ws, struct workspace, list); > + > + vfree(workspace->mem); > + kfree(workspace->buf); > + kfree(workspace); > +}

Re: [PATCH v2 3/4] btrfs: Add zstd support

On Thu, Jun 29, 2017 at 12:41:07PM -0700, Nick Terrell wrote: > +static void zstd_free_workspace(struct list_head *ws) > +{ > + struct workspace *workspace = list_entry(ws, struct workspace, list); > + > + vfree(workspace->mem); > + kfree(workspace->buf); > + kfree(workspace); > +}

Re: [BUG] x86/mm: Found insecure W+X mapping at address ffff88000005f000/0xffff88000005f000

On Tue, Jul 18, 2017 at 02:11:35PM +0200, Thomas Gleixner wrote: > On Tue, 18 Jul 2017, Piotr Gregor wrote: > > > > Dmesg reports insecure W+X mapping found at address > > 8805f000/0x8805f000 > > > > on 4.4.70 kernel patched with -rt83 patch: > > Does the same problem happen

Re: [BUG] x86/mm: Found insecure W+X mapping at address ffff88000005f000/0xffff88000005f000

On Tue, Jul 18, 2017 at 02:11:35PM +0200, Thomas Gleixner wrote: > On Tue, 18 Jul 2017, Piotr Gregor wrote: > > > > Dmesg reports insecure W+X mapping found at address > > 8805f000/0x8805f000 > > > > on 4.4.70 kernel patched with -rt83 patch: > > Does the same problem happen

Re: [RFC 0/4] perf script python: Provide perf_sample dict to all handlers

Thank you for taking a look into it. I don't see the garbled output. Can you please send me the perf.data file or a way to reproduce it? On Tue, Jul 18, 2017 at 1:35 AM, Jiri Olsa wrote: > On Mon, Jul 17, 2017 at 03:10:36PM -0700, Arun Kalyanasundaram wrote: >> The

Re: [RFC 0/4] perf script python: Provide perf_sample dict to all handlers

Thank you for taking a look into it. I don't see the garbled output. Can you please send me the perf.data file or a way to reproduce it? On Tue, Jul 18, 2017 at 1:35 AM, Jiri Olsa wrote: > On Mon, Jul 17, 2017 at 03:10:36PM -0700, Arun Kalyanasundaram wrote: >> The process_event python hook

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

On Tue, 18 Jul 2017 10:42:40 -0700 Feng Kan wrote: > On Mon, Jul 17, 2017 at 7:23 PM, Alex Williamson > wrote: > > On Mon, 17 Jul 2017 17:45:52 -0700 > > Feng Kan wrote: > > > >> The APM X-Gene PCIe root port does not support ACS at

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

On Tue, 18 Jul 2017 10:42:40 -0700 Feng Kan wrote: > On Mon, Jul 17, 2017 at 7:23 PM, Alex Williamson > wrote: > > On Mon, 17 Jul 2017 17:45:52 -0700 > > Feng Kan wrote: > > > >> The APM X-Gene PCIe root port does not support ACS at this point. > >> Since the root does not allow peer to peer

[PATCH] workqueue: doc change for ST behavior on NUMA systems

NUMA rework of workqueue made the combination of max_active of 1 and WQ_UNBOUND insufficient to guarantee ST behavior system wide. alloc_ordered_queue should now be used instead. Signed-off-by: Alexei Potashnik --- Documentation/core-api/workqueue.rst | 10 +++--- 1

[PATCH] workqueue: doc change for ST behavior on NUMA systems

NUMA rework of workqueue made the combination of max_active of 1 and WQ_UNBOUND insufficient to guarantee ST behavior system wide. alloc_ordered_queue should now be used instead. Signed-off-by: Alexei Potashnik --- Documentation/core-api/workqueue.rst | 10 +++--- 1 file changed, 7

Re: [PATCH net-next 00/12] net: dsa: mv88e6xxx: cleanup capabilities

From: Vivien Didelot Date: Mon, 17 Jul 2017 13:03:34 -0400 > This patch series removes the remaining capabilities as well as the > flags bitmap in the info structures. Most of them are turned into ops, > or new info members. > > There is no mv88e6xxx_cap

Re: [PATCH net-next 00/12] net: dsa: mv88e6xxx: cleanup capabilities

From: Vivien Didelot Date: Mon, 17 Jul 2017 13:03:34 -0400 > This patch series removes the remaining capabilities as well as the > flags bitmap in the info structures. Most of them are turned into ops, > or new info members. > > There is no mv88e6xxx_cap enum or bitmap flags anymore, only >

Re: [PATCH v2 00/16] Switchtec NTB Support

On 18/07/17 11:51 AM, Allen Hubbe wrote: > Acked-by: Allen Hubbe Thanks. > Should the order of 6 and 7 be swapped? Hmm, yes. I'll make the change for a v3 after more feedback comes. > 6 - I think just the comment is best. Rather than prohibit the use of >

Re: [PATCH v2 00/16] Switchtec NTB Support

On 18/07/17 11:51 AM, Allen Hubbe wrote: > Acked-by: Allen Hubbe Thanks. > Should the order of 6 and 7 be swapped? Hmm, yes. I'll make the change for a v3 after more feedback comes. > 6 - I think just the comment is best. Rather than prohibit the use of > functionality for hardware that

Re: [PATCH] ALSA: hda: constify pci_device_id.

On Tue, 18 Jul 2017 19:05:06 +0200, Arvind Yadav wrote: > > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >text data bss

Re: [PATCH] ALSA: hda: constify pci_device_id.

On Tue, 18 Jul 2017 19:05:06 +0200, Arvind Yadav wrote: > > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >text data bss

[RFC][PATCH v3] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

Currently the hikey dsi logic cannot generate accurate byte clocks values for all pixel clock values. Thus if a mode clock is selected that cannot match the calculated byte clock, the device will boot with a blank screen. This patch uses the new mode_valid callback (many thanks to Jose Abreu for

[RFC][PATCH v3] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

Currently the hikey dsi logic cannot generate accurate byte clocks values for all pixel clock values. Thus if a mode clock is selected that cannot match the calculated byte clock, the device will boot with a blank screen. This patch uses the new mode_valid callback (many thanks to Jose Abreu for

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Tue, 2017-07-18 at 10:50 -0700, Joe Perches wrote: > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > > Recently I have noticed too many users of struct rtc_time that > > printing > > its content field by field. > > > > In this series I introduce %pt[dt][rv] specifier to make life a

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Tue, 2017-07-18 at 10:50 -0700, Joe Perches wrote: > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > > Recently I have noticed too many users of struct rtc_time that > > printing > > its content field by field. > > > > In this series I introduce %pt[dt][rv] specifier to make life a

[PATCH v2 0/2] ZII RAVE platform driver

Hi everyone, This patch series is v2 of the driver for supervisory processor found on RAVE series of devices from ZII. Supervisory processor is a PIC microcontroller connected to various electrical subsystems on RAVE devices whose firmware implements protocol to command/qery them. Changes since

[PATCH v2 0/2] ZII RAVE platform driver

Hi everyone, This patch series is v2 of the driver for supervisory processor found on RAVE series of devices from ZII. Supervisory processor is a PIC microcontroller connected to various electrical subsystems on RAVE devices whose firmware implements protocol to command/qery them. Changes since

[PATCH v2 2/2] dt-bindings: mfd: Add bindings for ZII RAVE devices

Cc: cphe...@gmail.com Cc: Lucas Stach Cc: Nikita Yushchenko Cc: Rob Herring Cc: Mark Rutland Cc: devicet...@vger.kernel.org Acked-by: Rob Herring Signed-off-by: Andrey Smirnov

[PATCH v2 2/2] dt-bindings: mfd: Add bindings for ZII RAVE devices

Cc: cphe...@gmail.com Cc: Lucas Stach Cc: Nikita Yushchenko Cc: Rob Herring Cc: Mark Rutland Cc: devicet...@vger.kernel.org Acked-by: Rob Herring Signed-off-by: Andrey Smirnov --- .../devicetree/bindings/mfd/zii,rave-sp.txt| 39 ++ 1 file changed, 39

[PATCH v2 1/2] platform: Add driver for RAVE Supervisory Processor

Add a driver for RAVE Supervisory Processor, an MCU implementing varoius bits of housekeeping functionality (watchdoging, backlight control, LED control, etc) on RAVE family of products by Zodiac Inflight Innovations. This driver implementes core MFD/serdev device as well as communication

[PATCH v2 1/2] platform: Add driver for RAVE Supervisory Processor

Add a driver for RAVE Supervisory Processor, an MCU implementing varoius bits of housekeeping functionality (watchdoging, backlight control, LED control, etc) on RAVE family of products by Zodiac Inflight Innovations. This driver implementes core MFD/serdev device as well as communication

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

Hello, Peter. On Tue, Jul 18, 2017 at 07:28:01PM +0200, Peter Zijlstra wrote: > > And now try to create another child C, should that be a domain or > > threaded? > > Domain of course, as R must be a domain, and hence all its children > start out as such. I don't think it's a matter of course as

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

Hello, Peter. On Tue, Jul 18, 2017 at 07:28:01PM +0200, Peter Zijlstra wrote: > > And now try to create another child C, should that be a domain or > > threaded? > > Domain of course, as R must be a domain, and hence all its children > start out as such. I don't think it's a matter of course as

RE: [PATCH v2 00/16] Switchtec NTB Support

From: Logan Gunthorpe > Changes since v1: > > - Rebased onto latest ntb-next branch (with v4.13-rc1) > - Reworked ntb_mw_count() function so that it can be called all the > time (per discussion with Allen) > - Various spelling and formatting cleanups from Bjorn > - Added request_module() call

RE: [PATCH v2 00/16] Switchtec NTB Support

From: Logan Gunthorpe > Changes since v1: > > - Rebased onto latest ntb-next branch (with v4.13-rc1) > - Reworked ntb_mw_count() function so that it can be called all the > time (per discussion with Allen) > - Various spelling and formatting cleanups from Bjorn > - Added request_module() call

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

Hi, On 18/07/2017 at 10:25:23 -0700, Mark Salyzyn wrote: > Go directly to the rtc for persistent wall clock time and print. > Useful if REALTIME is required to be logged in a low level power > management function or when clock activities are suspended. An > aid to permit user space alignment of

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

Hi, On 18/07/2017 at 10:25:23 -0700, Mark Salyzyn wrote: > Go directly to the rtc for persistent wall clock time and print. > Useful if REALTIME is required to be logged in a low level power > management function or when clock activities are suspended. An > aid to permit user space alignment of

Re: [PATCH 0/5] earlycon hang under some conditions

Hi Jeffy, On Tue, Jul 18, 2017 at 02:02:53PM +0800, Jeffy Chen wrote: > I was testing earlycon with 8250 dw serial console. And it hangs in > these cases: > 1/ kernel hang when calling early write function after free_initmem: > a) the earlycon not disabled after the init code(due to keep_bootcon

Re: [PATCH 0/5] earlycon hang under some conditions

Hi Jeffy, On Tue, Jul 18, 2017 at 02:02:53PM +0800, Jeffy Chen wrote: > I was testing earlycon with 8250 dw serial console. And it hangs in > these cases: > 1/ kernel hang when calling early write function after free_initmem: > a) the earlycon not disabled after the init code(due to keep_bootcon

RE: [PATCH v4 4/5] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks

From: Logan Gunthorpe > Now that ioread64 and iowrite64 are available in io-64-nonatomic, > we can remove the hack at the top of ntb_hw_intel.c and replace it > with an include. > > Signed-off-by: Logan Gunthorpe > Cc: Jon Mason > Cc: Allen Hubbe

RE: [PATCH v4 4/5] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks

From: Logan Gunthorpe > Now that ioread64 and iowrite64 are available in io-64-nonatomic, > we can remove the hack at the top of ntb_hw_intel.c and replace it > with an include. > > Signed-off-by: Logan Gunthorpe > Cc: Jon Mason > Cc: Allen Hubbe > Acked-by: Dave Jiang Acked-by: Allen Hubbe

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > Recently I have noticed too many users of struct rtc_time that printing > its content field by field. > > In this series I introduce %pt[dt][rv] specifier to make life a bit > easier. Hey Andy. I just saw a patch with a printk for rtc

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > Recently I have noticed too many users of struct rtc_time that printing > its content field by field. > > In this series I introduce %pt[dt][rv] specifier to make life a bit > easier. Hey Andy. I just saw a patch with a printk for rtc

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

On Tue, Jul 18, 2017 at 8:46 PM, Andy Shevchenko wrote: > On Tue, Jul 18, 2017 at 8:25 PM, Mark Salyzyn wrote: >> Go directly to the rtc for persistent wall clock time and print. >> Useful if REALTIME is required to be logged in a low level power

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Tuesday 18 July 2017 05:01 PM, Sekhar Nori wrote: > Hi Keerthy, > > On Tuesday 18 July 2017 04:27 PM, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy >> --- >> Documentation/devicetree/bindings/gpio/gpio-davinci.txt | 3 ++- >>

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

On Tue, Jul 18, 2017 at 8:46 PM, Andy Shevchenko wrote: > On Tue, Jul 18, 2017 at 8:25 PM, Mark Salyzyn wrote: >> Go directly to the rtc for persistent wall clock time and print. >> Useful if REALTIME is required to be logged in a low level power >> management function or when clock activities

Re: [PATCH 3/4] gpio: davinci: Add a separate compatible for keystone-k2g soc

On Tuesday 18 July 2017 05:01 PM, Sekhar Nori wrote: > Hi Keerthy, > > On Tuesday 18 July 2017 04:27 PM, Keerthy wrote: >> Add a separate compatible for keystone-k2g soc >> >> Signed-off-by: Keerthy >> --- >> Documentation/devicetree/bindings/gpio/gpio-davinci.txt | 3 ++- >>

Re: [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops

From: Florian Fainelli Date: Tue, 18 Jul 2017 09:01:01 -0700 > On 07/17/2017 02:10 PM, David Miller wrote: >> From: Andrew Lunn >> Date: Mon, 17 Jul 2017 23:04:05 +0200 >> >>> On Mon, Jul 17, 2017 at 01:45:49PM -0700, David Miller wrote: From: Vivien

Re: [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops

From: Florian Fainelli Date: Tue, 18 Jul 2017 09:01:01 -0700 > On 07/17/2017 02:10 PM, David Miller wrote: >> From: Andrew Lunn >> Date: Mon, 17 Jul 2017 23:04:05 +0200 >> >>> On Mon, Jul 17, 2017 at 01:45:49PM -0700, David Miller wrote: From: Vivien Didelot Date: Mon, 17 Jul 2017

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Tuesday 18 July 2017 10:24 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Currently davinci_gpio_irq_setup return value is ignored. Handle the >> return value appropriately. >> >> Signed-off-by: Keerthy >> --- >>

Re: [PATCH 2/4] gpio: davinci: Handle the return value of davinci_gpio_irq_setup function

On Tuesday 18 July 2017 10:24 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Currently davinci_gpio_irq_setup return value is ignored. Handle the >> return value appropriately. >> >> Signed-off-by: Keerthy >> --- >> drivers/gpio/gpio-davinci.c | 18

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

On Tue, Jul 18, 2017 at 8:25 PM, Mark Salyzyn wrote: > Go directly to the rtc for persistent wall clock time and print. > Useful if REALTIME is required to be logged in a low level power > management function or when clock activities are suspended. An > aid to permit user

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

On Tue, Jul 18, 2017 at 8:25 PM, Mark Salyzyn wrote: > Go directly to the rtc for persistent wall clock time and print. > Useful if REALTIME is required to be logged in a low level power > management function or when clock activities are suspended. An > aid to permit user space alignment of

Re: [PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

On Tuesday 18 July 2017 10:20 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Use the devm version of gpiochip_add_data and pass on the >> return value. Reset the static variables to 0 before returning. >> >> Signed-off-by: Keerthy >> --- >>

Re: [PATCH 1/4] gpio: davinci: Use devm_gpiochip_add_data in place of gpiochip_add_data

On Tuesday 18 July 2017 10:20 PM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> Use the devm version of gpiochip_add_data and pass on the >> return value. Reset the static variables to 0 before returning. >> >> Signed-off-by: Keerthy >> --- >>

[PATCH] pinctrl: samsung: Remove unneeded local variable initialization

Two local variables (shift and reg_con) were initialized to unused values - they were overwritten just few lines after. Getting rid of this unused initialization allows dropping other variables and compacting slightly the code. Signed-off-by: Krzysztof Kozlowski ---

[PATCH] pinctrl: samsung: Remove unneeded local variable initialization

Two local variables (shift and reg_con) were initialized to unused values - they were overwritten just few lines after. Getting rid of this unused initialization allows dropping other variables and compacting slightly the code. Signed-off-by: Krzysztof Kozlowski ---

Re: [PATCH 1/3] ACPI / blacklist: add acpi_match_oemlist() interface

On Tue, Jul 18, 2017 at 05:24:50PM +, Kani, Toshimitsu wrote: > Well, a list does not need to be a black-list. But this one *is* a blacklist. > So, I tried to avoid putting any usage to the structure name. So OEM is a usage. The moment you need to use it for something else besides an OEM,

Re: [PATCH 1/3] ACPI / blacklist: add acpi_match_oemlist() interface

On Tue, Jul 18, 2017 at 05:24:50PM +, Kani, Toshimitsu wrote: > Well, a list does not need to be a black-list. But this one *is* a blacklist. > So, I tried to avoid putting any usage to the structure name. So OEM is a usage. The moment you need to use it for something else besides an OEM,

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

On Mon, Jul 17, 2017 at 7:23 PM, Alex Williamson wrote: > On Mon, 17 Jul 2017 17:45:52 -0700 > Feng Kan wrote: > >> The APM X-Gene PCIe root port does not support ACS at this point. >> Since the root does not allow peer to peer transactions, mask out >>

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

On Mon, Jul 17, 2017 at 7:23 PM, Alex Williamson wrote: > On Mon, 17 Jul 2017 17:45:52 -0700 > Feng Kan wrote: > >> The APM X-Gene PCIe root port does not support ACS at this point. >> Since the root does not allow peer to peer transactions, mask out >> ACS capability flag bits. >> >>

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

On Tue, 2017-07-18 at 10:25 -0700, Mark Salyzyn wrote: > Go directly to the rtc for persistent wall clock time and print. > Useful if REALTIME is required to be logged in a low level power > management function or when clock activities are suspended. An > aid to permit user space alignment of

Re: [PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

On Tue, 2017-07-18 at 10:25 -0700, Mark Salyzyn wrote: > Go directly to the rtc for persistent wall clock time and print. > Useful if REALTIME is required to be logged in a low level power > management function or when clock activities are suspended. An > aid to permit user space alignment of

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On 07/18/2017 01:28 PM, Peter Zijlstra wrote: > On Mon, Jul 17, 2017 at 10:26:09AM -0400, Tejun Heo wrote: >> Hello, Peter. >> >> On Mon, Jul 17, 2017 at 04:14:09PM +0200, Peter Zijlstra wrote: >>> AFAICT this is not in fact what I suggested... :/ >> Heh, sorry about misattributing that. I was

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On 07/18/2017 01:28 PM, Peter Zijlstra wrote: > On Mon, Jul 17, 2017 at 10:26:09AM -0400, Tejun Heo wrote: >> Hello, Peter. >> >> On Mon, Jul 17, 2017 at 04:14:09PM +0200, Peter Zijlstra wrote: >>> AFAICT this is not in fact what I suggested... :/ >> Heh, sorry about misattributing that. I was

Re: [PATCH 7/7] signal: Remove kernel interal si_code magic

Linus Torvalds writes: > On Tue, Jul 18, 2017 at 7:06 AM, Eric W. Biederman > wrote: >> struct siginfo is a union and the kernel since 2.4 has been hiding a union >> tag in the high 16bits of si_code using the values: >> __SI_KILL >>

Re: [PATCH 7/7] signal: Remove kernel interal si_code magic

Linus Torvalds writes: > On Tue, Jul 18, 2017 at 7:06 AM, Eric W. Biederman > wrote: >> struct siginfo is a union and the kernel since 2.4 has been hiding a union >> tag in the high 16bits of si_code using the values: >> __SI_KILL >> __SI_TIMER >> __SI_POLL >> __SI_FAULT >> __SI_CHLD >> __SI_RT

Re: [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control

I have verified that building a clean v4.12 with 68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47 cherry picked on top still shows the problem: [root@backup2 ~]# mtx -f /dev/sg7 next 0 Unloading drive 0 into Storage Element 45...mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no

Re: [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control

I have verified that building a clean v4.12 with 68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47 cherry picked on top still shows the problem: [root@backup2 ~]# mtx -f /dev/sg7 next 0 Unloading drive 0 into Storage Element 45...mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no

[PATCH] ARC: reset: introduce HSDKv1 reset driver

The HSDK v1 periphery IPs can be reset by accessing some registers from the CGU block. The list of available reset lines is documented in the DT bindings. Signed-off-by: Eugeniy Paltsev --- .../bindings/reset/snps,hsdk-v1-reset.txt | 28 MAINTAINERS

[PATCH] ARC: reset: introduce HSDKv1 reset driver

The HSDK v1 periphery IPs can be reset by accessing some registers from the CGU block. The list of available reset lines is documented in the DT bindings. Signed-off-by: Eugeniy Paltsev --- .../bindings/reset/snps,hsdk-v1-reset.txt | 28 MAINTAINERS

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On Mon, Jul 17, 2017 at 10:26:09AM -0400, Tejun Heo wrote: > Hello, Peter. > > On Mon, Jul 17, 2017 at 04:14:09PM +0200, Peter Zijlstra wrote: > > AFAICT this is not in fact what I suggested... :/ > > Heh, sorry about misattributing that. I was mostly referring to the > overall idea of marking

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On Mon, Jul 17, 2017 at 10:26:09AM -0400, Tejun Heo wrote: > Hello, Peter. > > On Mon, Jul 17, 2017 at 04:14:09PM +0200, Peter Zijlstra wrote: > > AFAICT this is not in fact what I suggested... :/ > > Heh, sorry about misattributing that. I was mostly referring to the > overall idea of marking

[PATCH 4/4] PM: Print wall time at hibernate entry and exit

Permits power state and battery life diagnosis. Feature activated by CONFIG_RTC_SHOW_TIME. Signed-off-by: Mark Salyzyn --- kernel/power/hibernate.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c

[PATCH 4/4] PM: Print wall time at hibernate entry and exit

Permits power state and battery life diagnosis. Feature activated by CONFIG_RTC_SHOW_TIME. Signed-off-by: Mark Salyzyn --- kernel/power/hibernate.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c index

[PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

Go directly to the rtc for persistent wall clock time and print. Useful if REALTIME is required to be logged in a low level power management function or when clock activities are suspended. An aid to permit user space alignment of kernel activities. Feature activated by CONFIG_RTC_SHOW_TIME.

[PATCH 1/4] rtc-lib: Add rtc_show_time(const char *prefix_msg)

Go directly to the rtc for persistent wall clock time and print. Useful if REALTIME is required to be logged in a low level power management function or when clock activities are suspended. An aid to permit user space alignment of kernel activities. Feature activated by CONFIG_RTC_SHOW_TIME.

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