[PATCH v5 5/5] cramfs: rehabilitate it

Update documentation, pointer to latest tools, appoint myself as maintainer. Given it's been unloved for so long, I don't expect anyone will protest. Signed-off-by: Nicolas Pitre Tested-by: Chris Brandt --- Documentation/filesystems/cramfs.txt | 42

[PATCH v5 5/5] cramfs: rehabilitate it

Update documentation, pointer to latest tools, appoint myself as maintainer. Given it's been unloved for so long, I don't expect anyone will protest. Signed-off-by: Nicolas Pitre Tested-by: Chris Brandt --- Documentation/filesystems/cramfs.txt | 42

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

On Fri, Oct 6, 2017 at 9:24 AM, Rafael J. Wysocki wrote: >> On the other hand, the RP05 (root port) _PRW says it will wake up the >> system via GPE09, and the _L09 handler at least has one codepath which >> could potentially do a Notify(PXSX, 2) to indicate an ethernet wakeup.

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

On Fri, Oct 6, 2017 at 9:24 AM, Rafael J. Wysocki wrote: >> On the other hand, the RP05 (root port) _PRW says it will wake up the >> system via GPE09, and the _L09 handler at least has one codepath which >> could potentially do a Notify(PXSX, 2) to indicate an ethernet wakeup. > > Which can only

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

On Fri, Oct 6, 2017 at 8:16 AM, Francois Romieu wrote: > Daniel Drake : > [...] >> Also, is there a standard behaviour defined for ethernet drivers >> regarding wake-on-LAN? r8169 appears to enable wake-on-LAN by default >> if it believes the hardware is

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

On Fri, Oct 6, 2017 at 8:16 AM, Francois Romieu wrote: > Daniel Drake : > [...] >> Also, is there a standard behaviour defined for ethernet drivers >> regarding wake-on-LAN? r8169 appears to enable wake-on-LAN by default >> if it believes the hardware is capable of it, > > If so it isn't its

__ubsan_handle_type_mismatch converted to __ubsan_handle_type_mismatch_v1

Hi All, Based on below links __ubsan_handle_type_mismatch has been renamed to __ubsan_handle_type_mismatch_v1. https://github.com/llvm-mirror/compiler-rt/commit/56faee71af1888ba12ab076b3d1f9bbe223493df#diff-21369cc6f3917b27df3ced8de89cf134

__ubsan_handle_type_mismatch converted to __ubsan_handle_type_mismatch_v1

Hi All, Based on below links __ubsan_handle_type_mismatch has been renamed to __ubsan_handle_type_mismatch_v1. https://github.com/llvm-mirror/compiler-rt/commit/56faee71af1888ba12ab076b3d1f9bbe223493df#diff-21369cc6f3917b27df3ced8de89cf134

Re: [PATCH] md: raid10: remove VLAIS

On Thu, Oct 05 2017, Matthias Kaehlcke wrote: > Hi Neil, > > El Fri, Oct 06, 2017 at 10:58:59AM +1100 NeilBrown ha dit: > >> On Thu, Oct 05 2017, Matthias Kaehlcke wrote: >> >> > The raid10 driver can't be built with clang since it uses a variable >> > length array in a structure (VLAIS): >> >

Re: [PATCH] md: raid10: remove VLAIS

On Thu, Oct 05 2017, Matthias Kaehlcke wrote: > Hi Neil, > > El Fri, Oct 06, 2017 at 10:58:59AM +1100 NeilBrown ha dit: > >> On Thu, Oct 05 2017, Matthias Kaehlcke wrote: >> >> > The raid10 driver can't be built with clang since it uses a variable >> > length array in a structure (VLAIS): >> >

Re: [ANNOUNCE] v4.11.12-rt13

On Thu, 2017-10-05 at 17:54 +0200, Sebastian Andrzej Siewior wrote: > On 2017-10-04 18:07:59 [+0200], Mike Galbraith wrote: > > Seems combo-patch induced some ltp posix conformance test grumbling. > > > > +clock_settime_8_1 ... ... FAILED > > +clock_settime_4_2 ... ... FAILED > >

Re: [ANNOUNCE] v4.11.12-rt13

On Thu, 2017-10-05 at 17:54 +0200, Sebastian Andrzej Siewior wrote: > On 2017-10-04 18:07:59 [+0200], Mike Galbraith wrote: > > Seems combo-patch induced some ltp posix conformance test grumbling. > > > > +clock_settime_8_1 ... ... FAILED > > +clock_settime_4_2 ... ... FAILED > >

RE: [PATCH v3 0/4] phy: rcar-gen3-usb2: add support for r8a77995

Hi Kishon, Would you review this patch set? I checked this can apply your latest linux-phy.git / next branch (the commit id = 415060b21f31). Best regards, Yoshihiro Shimoda > -Original Message- > From: Yoshihiro Shimoda > Sent: Friday, September 1, 2017 11:41 AM > To: kis...@ti.com >

RE: [PATCH v3 0/4] phy: rcar-gen3-usb2: add support for r8a77995

Hi Kishon, Would you review this patch set? I checked this can apply your latest linux-phy.git / next branch (the commit id = 415060b21f31). Best regards, Yoshihiro Shimoda > -Original Message- > From: Yoshihiro Shimoda > Sent: Friday, September 1, 2017 11:41 AM > To: kis...@ti.com >

Re: [PATCH] vfs: hard-ban creating files with control characters in the name

On Thu, Oct 05, 2017 at 12:16:19PM -0400, J. Bruce Fields wrote: > This kind of restriction sounds more like a permanent feature of the > filesystem--something you'd set at mkfs time. > > We already have filesystems with these kinds of restrictions, don't we? In general, no. Filename storage

Re: [PATCH] vfs: hard-ban creating files with control characters in the name

On Thu, Oct 05, 2017 at 12:16:19PM -0400, J. Bruce Fields wrote: > This kind of restriction sounds more like a permanent feature of the > filesystem--something you'd set at mkfs time. > > We already have filesystems with these kinds of restrictions, don't we? In general, no. Filename storage

[git pull] drm fixes for 4.14-rc4

Hi Linus, Some i915 fixes from last two weeks (as they were on a strange base and I just waited for rc3), also a single sun4i hdmi fix. Dave. The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff: Linux 4.14-rc3 (2017-10-01 14:54:54 -0700) are available in the git

[git pull] drm fixes for 4.14-rc4

Hi Linus, Some i915 fixes from last two weeks (as they were on a strange base and I just waited for rc3), also a single sun4i hdmi fix. Dave. The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff: Linux 4.14-rc3 (2017-10-01 14:54:54 -0700) are available in the git

Re: [PATCH 1/2] powerpc/platforms/cell: Delete an error message for a failed memory allocation in three functions

On Thu, 2017-10-05 at 22:29 +0200, Michal Suchánek wrote: > I do not expect the kernel to generate a > stack trace every time memory allocation fails. With all the hooks in > the code it is hard to tell, though. All [kv].alloc failures without __GFP_NOWARN call dump_stack()

Re: [PATCH 1/2] powerpc/platforms/cell: Delete an error message for a failed memory allocation in three functions

On Thu, 2017-10-05 at 22:29 +0200, Michal Suchánek wrote: > I do not expect the kernel to generate a > stack trace every time memory allocation fails. With all the hooks in > the code it is hard to tell, though. All [kv].alloc failures without __GFP_NOWARN call dump_stack()

[PATCH 2/2] perf, tools, stat: Reset ids counter when retrying events

From: Andi Kleen perf stat can retry opening events. After opening an file descriptor it adds the ids to the ecsel. Each event keeps a running count of ids. When we decide to close an evsel and retry with a different configuration this count needs to be reset, otherwise it

[PATCH 2/2] perf, tools, stat: Reset ids counter when retrying events

From: Andi Kleen perf stat can retry opening events. After opening an file descriptor it adds the ids to the ecsel. Each event keeps a running count of ids. When we decide to close an evsel and retry with a different configuration this count needs to be reset, otherwise it can overflow the

[PATCH 1/2] perf, tools, stat: Use xyarray dimensions to iterate fds

From: Andi Kleen Now that the xyarray stores the dimensions we can use those to iterate over the FDs for a evsel. Signed-off-by: Andi Kleen --- tools/perf/builtin-stat.c | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) diff --git

[PATCH 1/2] perf, tools, stat: Use xyarray dimensions to iterate fds

From: Andi Kleen Now that the xyarray stores the dimensions we can use those to iterate over the FDs for a evsel. Signed-off-by: Andi Kleen --- tools/perf/builtin-stat.c | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/tools/perf/builtin-stat.c

[PATCH v6 3/3] KVM: LAPIC: Apply change to TDCR right away to the timer

From: Wanpeng Li The description in the Intel SDM of how the divide configuration register is used: "The APIC timer frequency will be the processor's bus clock or core crystal clock frequency divided by the value specified in the divide configuration register."

[PATCH v6 3/3] KVM: LAPIC: Apply change to TDCR right away to the timer

From: Wanpeng Li The description in the Intel SDM of how the divide configuration register is used: "The APIC timer frequency will be the processor's bus clock or core crystal clock frequency divided by the value specified in the divide configuration register." Observation of baremetal shown

[PATCH v6 1/3] KVM: LAPIC: Introduce limit_periodic_timer_frequency

From: Wanpeng Li Extract the logic of limit lapic periodic timer frequency to a new function, this function will be used by later patches. Cc: Paolo Bonzini Cc: Radim Krčmář Signed-off-by: Wanpeng Li

[PATCH v6 2/3] KVM: LAPIC: Keep timer running when switching between one-shot and periodic mode

From: Wanpeng Li If we take TSC-deadline mode timer out of the picture, the Intel SDM does not say that the timer is disable when the timer mode is change, either from one-shot to periodic or vice versa. After this patch, the timer is no longer disarmed on change of

[PATCH v6 0/3] KVM: LAPIC: Rework lapic timer to behave more like real-hardware

The issue is reported in xen community. Anthony PERARD pointed out: https://www.mail-archive.com/xen-devel@lists.xen.org/msg117283.html# | When developing PVH for OVMF, I've used the lapic timer. It turns out that the | way it is used by OVMF did not work with Xen [1]. I tried to find out

[PATCH v6 1/3] KVM: LAPIC: Introduce limit_periodic_timer_frequency

From: Wanpeng Li Extract the logic of limit lapic periodic timer frequency to a new function, this function will be used by later patches. Cc: Paolo Bonzini Cc: Radim Krčmář Signed-off-by: Wanpeng Li --- arch/x86/kvm/lapic.c | 39 ++- 1 file changed, 22

[PATCH v6 2/3] KVM: LAPIC: Keep timer running when switching between one-shot and periodic mode

From: Wanpeng Li If we take TSC-deadline mode timer out of the picture, the Intel SDM does not say that the timer is disable when the timer mode is change, either from one-shot to periodic or vice versa. After this patch, the timer is no longer disarmed on change of mode, so the counter (TMCCT)

[PATCH v6 0/3] KVM: LAPIC: Rework lapic timer to behave more like real-hardware

The issue is reported in xen community. Anthony PERARD pointed out: https://www.mail-archive.com/xen-devel@lists.xen.org/msg117283.html# | When developing PVH for OVMF, I've used the lapic timer. It turns out that the | way it is used by OVMF did not work with Xen [1]. I tried to find out

Re: [PATCH] arch_topology: Fix section miss match warning due to free_raw_capacity()

On 2017-09-25 16:20, Viresh Kumar wrote: On 25-09-17, 15:51, Prasad Sodagudi wrote: Remove the __init annotation from free_raw_capacity() to avoid the following warning. The function init_cpu_capacity_callback() references the function __init free_raw_capacity(). WARNING:

Re: [PATCH] arch_topology: Fix section miss match warning due to free_raw_capacity()

On 2017-09-25 16:20, Viresh Kumar wrote: On 25-09-17, 15:51, Prasad Sodagudi wrote: Remove the __init annotation from free_raw_capacity() to avoid the following warning. The function init_cpu_capacity_callback() references the function __init free_raw_capacity(). WARNING:

Hi There

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your

Hi There

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your

Re: [PATCH] kvm/x86: Avoid async PF to end RCU read-side critical section early in PREEMPT=n kernel

On Tue, Oct 03, 2017 at 02:11:08PM +, Paolo Bonzini wrote: > I'd prefer a slight change in subject and topic: > > --- 8< > Subject: [PATCH] kvm/x86: Avoid async PF preempting the kernel incorrectly > > Currently, in PREEMPT_COUNT=n kernel, kvm_async_pf_task_wait() could call >

Re: [PATCH] kvm/x86: Avoid async PF to end RCU read-side critical section early in PREEMPT=n kernel

On Tue, Oct 03, 2017 at 02:11:08PM +, Paolo Bonzini wrote: > I'd prefer a slight change in subject and topic: > > --- 8< > Subject: [PATCH] kvm/x86: Avoid async PF preempting the kernel incorrectly > > Currently, in PREEMPT_COUNT=n kernel, kvm_async_pf_task_wait() could call >

Re: [PATCH] vfs: fix statfs64() returning impossible EOVERFLOW for 64-bit f_files

On Thu, Oct 5, 2017 at 4:06 PM, Al Viro wrote: > > Just to make sure we are on the same page: out of kstatfs fields > we have 5 u64 ones (see above; all of them are u64 is struct statfs64 > on all architectures), an opaque 64bit f_fsid and 5 fields that > are long: f_type

Re: [PATCH] vfs: fix statfs64() returning impossible EOVERFLOW for 64-bit f_files

On Thu, Oct 5, 2017 at 4:06 PM, Al Viro wrote: > > Just to make sure we are on the same page: out of kstatfs fields > we have 5 u64 ones (see above; all of them are u64 is struct statfs64 > on all architectures), an opaque 64bit f_fsid and 5 fields that > are long: f_type (magic numbers, all

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

On Thu, Oct 5, 2017 at 10:57 AM, Daniel Drake wrote: > Hi, > > On the Acer laptop models Aspire ES1-533, Aspire ES1-732, PackardBell > ENTE69AP and Gateway NE533, we are seeing a problem where the system > immediately wakes up after being put into S3 suspend. > > This problem

Re: r8169 Wake-on-LAN causes immediate ACPI GPE wakeup

On Thu, Oct 5, 2017 at 10:57 AM, Daniel Drake wrote: > Hi, > > On the Acer laptop models Aspire ES1-533, Aspire ES1-732, PackardBell > ENTE69AP and Gateway NE533, we are seeing a problem where the system > immediately wakes up after being put into S3 suspend. > > This problem has been seen on all

[PATCH 1/7] Delete unnecessary structure

From: Masaki Ota -Delete "struct u1_dev devInfo" structure, because u1_dev structure is already declared as "struct u1_dev *data", and this structure is used for getting U1 data in [PATCH 2/7]. Signed-off-by: Masaki Ota ---

[PATCH 1/7] Delete unnecessary structure

From: Masaki Ota -Delete "struct u1_dev devInfo" structure, because u1_dev structure is already declared as "struct u1_dev *data", and this structure is used for getting U1 data in [PATCH 2/7]. Signed-off-by: Masaki Ota --- drivers/hid/hid-alps.c | 69

[PATCH 6/7] Add new U1 device ID

From: Masaki Ota -Add new U1 device Product ID -This device is used on HP Elite book x360 series Signed-off-by: Masaki Ota --- drivers/hid/hid-alps.c | 3 +++ drivers/hid/hid-core.c | 1 + drivers/hid/hid-ids.h | 1 + 3 files changed, 5

[PATCH 6/7] Add new U1 device ID

From: Masaki Ota -Add new U1 device Product ID -This device is used on HP Elite book x360 series Signed-off-by: Masaki Ota --- drivers/hid/hid-alps.c | 3 +++ drivers/hid/hid-core.c | 1 + drivers/hid/hid-ids.h | 1 + 3 files changed, 5 insertions(+) diff --git a/drivers/hid/hid-alps.c

[PATCH 3/7] Add some variables

From: Masaki Ota -Create x_min, y_min and max_fingers variables for set correct XY minimum value and the number of max finger on each devices. -Move the Button pad checking code to U1 init function, because this checking code is for U1 device. Signed-off-by: Masaki Ota

[PATCH]Support new Alps HID Touchpad device

I have modified the Patch. About __maybe_unused annotation, it was specified by Benjamin in previous review. So I added this annotation. Best Regards, Masaki OTa

[PATCH 4/7] replace some variables

From: Masaki Ota -Move some variables(dev_ctrl, dev_type, sen_line_num_x, sen_line_num_y, pitch_x, pitch_y, resolution, btn_info) from u1_dev structure to "u1_init()", because these variables are only used in "u1_init()" function. Signed-off-by: Masaki Ota

[PATCH 2/7] Separate U1 device code

From: Masaki Ota -Create "static int u1_init()" function for separate U1 device initialization code from Main initialization. -Create "has_sp" variable for checking whether it has SP device or not. Signed-off-by: Masaki Ota ---

[PATCH 3/7] Add some variables

From: Masaki Ota -Create x_min, y_min and max_fingers variables for set correct XY minimum value and the number of max finger on each devices. -Move the Button pad checking code to U1 init function, because this checking code is for U1 device. Signed-off-by: Masaki Ota ---

[PATCH]Support new Alps HID Touchpad device

I have modified the Patch. About __maybe_unused annotation, it was specified by Benjamin in previous review. So I added this annotation. Best Regards, Masaki OTa

[PATCH 4/7] replace some variables

From: Masaki Ota -Move some variables(dev_ctrl, dev_type, sen_line_num_x, sen_line_num_y, pitch_x, pitch_y, resolution, btn_info) from u1_dev structure to "u1_init()", because these variables are only used in "u1_init()" function. Signed-off-by: Masaki Ota --- drivers/hid/hid-alps.c | 67

[PATCH 2/7] Separate U1 device code

From: Masaki Ota -Create "static int u1_init()" function for separate U1 device initialization code from Main initialization. -Create "has_sp" variable for checking whether it has SP device or not. Signed-off-by: Masaki Ota --- drivers/hid/hid-alps.c | 120

[PATCH 7/7] Support Alps U1 USB Touchpad device

From: Masaki Ota -Add T4 USB device Product ID. (0x1216) -Separate T4 USB device initialization code from T4 Standard device code. -T4 USB device is used on HP Elite x2 series Signed-off-by: Masaki Ota --- drivers/hid/hid-alps.c | 35

[PATCH 7/7] Support Alps U1 USB Touchpad device

From: Masaki Ota -Add T4 USB device Product ID. (0x1216) -Separate T4 USB device initialization code from T4 Standard device code. -T4 USB device is used on HP Elite x2 series Signed-off-by: Masaki Ota --- drivers/hid/hid-alps.c | 35 +-- drivers/hid/hid-core.c

[PATCH 5/7] Support Alps T4 Touchpad device

From: Masaki Ota -Define T4 device specification value for support T4 device. -Create "t4_contact_data" and "t4_input_report" structure for decode T4 data and store it. -Create "t4_calc_check_sum()" function for calculate checksum value to send the device. T4 needs to

[PATCH 5/7] Support Alps T4 Touchpad device

From: Masaki Ota -Define T4 device specification value for support T4 device. -Create "t4_contact_data" and "t4_input_report" structure for decode T4 data and store it. -Create "t4_calc_check_sum()" function for calculate checksum value to send the device. T4 needs to send this value when

[PATCH net v2 3/9] net/mac89x0: Fix and modernize log messages

Fix misplaced newlines in conditional log messages. Add missing printk severity levels. Log the MAC address after the interface gets a meaningful name. Drop deprecated "out of memory" message as per checkpatch advice. Signed-off-by: Finn Thain ---

[PATCH net v2 3/9] net/mac89x0: Fix and modernize log messages

Fix misplaced newlines in conditional log messages. Add missing printk severity levels. Log the MAC address after the interface gets a meaningful name. Drop deprecated "out of memory" message as per checkpatch advice. Signed-off-by: Finn Thain --- drivers/net/ethernet/cirrus/mac89x0.c | 26

[PATCH net v2 1/9] net/smc9194: Remove bogus CONFIG_MAC reference

The only version of smc9194.c with Mac support is the one in the linux-mac68k CVS repo. AFAIK that driver never made it to the mainline. Despite that, as of v2.3.45, arch/m68k/config.in listed CONFIG_SMC9194 under CONFIG_MAC. This mistake got carried over into Kconfig in v2.5.55. (See pre-git era

[PATCH net v2 1/9] net/smc9194: Remove bogus CONFIG_MAC reference

The only version of smc9194.c with Mac support is the one in the linux-mac68k CVS repo. AFAIK that driver never made it to the mainline. Despite that, as of v2.3.45, arch/m68k/config.in listed CONFIG_SMC9194 under CONFIG_MAC. This mistake got carried over into Kconfig in v2.5.55. (See pre-git era

[PATCH net v2 4/9] net/mac89x0: Replace custom debug logging with netif_* calls

Signed-off-by: Finn Thain --- drivers/net/ethernet/cirrus/mac89x0.c | 47 --- 1 file changed, 16 insertions(+), 31 deletions(-) diff --git a/drivers/net/ethernet/cirrus/mac89x0.c b/drivers/net/ethernet/cirrus/mac89x0.c index

[PATCH net v2 4/9] net/mac89x0: Replace custom debug logging with netif_* calls

Signed-off-by: Finn Thain --- drivers/net/ethernet/cirrus/mac89x0.c | 47 --- 1 file changed, 16 insertions(+), 31 deletions(-) diff --git a/drivers/net/ethernet/cirrus/mac89x0.c b/drivers/net/ethernet/cirrus/mac89x0.c index fa4b6968afd5..d331c8344b96 100644 ---

[PATCH net v2 6/9] net/sonic: Cleanup and modernize log messages

Add missing printk severity levels. Don't print the valid silicon revision number (it's in the source). Avoid KERN_CONT usage as per advice from checkpatch. Avoid ifdef around printk calls. Cc: Thomas Bogendoerfer Cc: Chris Zankel Signed-off-by: Finn

[PATCH net v2 5/9] net/macmace: Fix and cleanup log messages

Log the MAC address after the interface gets a meaningful name and in doing so, make the registration error path more idiomatic. Drop redundant debug messages for FIFO events recorded in the interface statistics (consistent with mace.c). Signed-off-by: Finn Thain

[PATCH net v2 5/9] net/macmace: Fix and cleanup log messages

Log the MAC address after the interface gets a meaningful name and in doing so, make the registration error path more idiomatic. Drop redundant debug messages for FIFO events recorded in the interface statistics (consistent with mace.c). Signed-off-by: Finn Thain Tested-by: Stan Johnson ---

[PATCH net v2 6/9] net/sonic: Cleanup and modernize log messages

Add missing printk severity levels. Don't print the valid silicon revision number (it's in the source). Avoid KERN_CONT usage as per advice from checkpatch. Avoid ifdef around printk calls. Cc: Thomas Bogendoerfer Cc: Chris Zankel Signed-off-by: Finn Thain --- Only the macsonic.c changes have

[PATCH net v2 8/9] net/8390: Fix redundant code

The patch which introduced the 8390 core module parameter 'msg_enable' failed to do anything useful with it: it merely causes an ancient version string to be logged. Remove the other code that logs the same string. Use the msg_enable module parameter as the default value for ei_local->msg_enable.

[PATCH net v2 8/9] net/8390: Fix redundant code

The patch which introduced the 8390 core module parameter 'msg_enable' failed to do anything useful with it: it merely causes an ancient version string to be logged. Remove the other code that logs the same string. Use the msg_enable module parameter as the default value for ei_local->msg_enable.

[PATCH net v2 9/9] net/mac8390: Fix log messages

Before expansion, dev->name is "eth%d", so log the slot number instead. Log the MAC address after the interface gets a meaningful name. Disambiguate the two identical "Card type %s is unsupported" messages. Fix the duplicated driver name in the pr_warn() message. Fixes: 3a3a7f3b7fbd ("net:

[PATCH net v2 9/9] net/mac8390: Fix log messages

Before expansion, dev->name is "eth%d", so log the slot number instead. Log the MAC address after the interface gets a meaningful name. Disambiguate the two identical "Card type %s is unsupported" messages. Fix the duplicated driver name in the pr_warn() message. Fixes: 3a3a7f3b7fbd ("net:

[PATCH net v2 7/9] net/sonic: Replace custom debug logging with netif_* calls

Also eliminate duplicated debug code by moving it into the core driver. Cc: Thomas Bogendoerfer Cc: Chris Zankel Signed-off-by: Finn Thain --- Only the sonic.[ch] and macsonic.c changes have been tested. The other changes

[PATCH net v2 7/9] net/sonic: Replace custom debug logging with netif_* calls

Also eliminate duplicated debug code by moving it into the core driver. Cc: Thomas Bogendoerfer Cc: Chris Zankel Signed-off-by: Finn Thain --- Only the sonic.[ch] and macsonic.c changes have been tested. The other changes are similar but untested. --- drivers/net/ethernet/natsemi/jazzsonic.c

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Fri, 6 Oct 2017 09:32:52 +0900 Masami Hiramatsu wrote: > I think using ftrace gives you lower latency, but you need to depend on > CONFIG_FUNCTION_TRACER instead of CONFIG_KPROBES. Which shouldn't be an issue, since all distros now have that enabled. -- Steve

Re: [RFC PATCH -tip 0/5] kprobes: Abolish jprobe APIs

On Fri, 6 Oct 2017 09:32:52 +0900 Masami Hiramatsu wrote: > I think using ftrace gives you lower latency, but you need to depend on > CONFIG_FUNCTION_TRACER instead of CONFIG_KPROBES. Which shouldn't be an issue, since all distros now have that enabled. -- Steve

Re: [PATCH V2] PCI: AER: fix deadlock in do_recovery

On Thu, Oct 05, 2017 at 01:42:09PM -0500, Bjorn Helgaas wrote: >On Thu, Oct 05, 2017 at 11:05:12PM +0800, Wei Yang wrote: >> On Wed, Oct 4, 2017 at 5:15 AM, Bjorn Helgaas wrote: >> > [+cc Alex, Gavin, Wei] >> > >> > On Fri, Sep 29, 2017 at 10:49:38PM -0700, Govindarajulu

Re: [PATCH V2] PCI: AER: fix deadlock in do_recovery

On Thu, Oct 05, 2017 at 01:42:09PM -0500, Bjorn Helgaas wrote: >On Thu, Oct 05, 2017 at 11:05:12PM +0800, Wei Yang wrote: >> On Wed, Oct 4, 2017 at 5:15 AM, Bjorn Helgaas wrote: >> > [+cc Alex, Gavin, Wei] >> > >> > On Fri, Sep 29, 2017 at 10:49:38PM -0700, Govindarajulu Varadarajan wrote: >> >>

[PATCH net v2 2/9] net/mac89x0: Remove dead or unreachable code

Signed-off-by: Finn Thain --- drivers/net/ethernet/cirrus/mac89x0.c | 31 --- 1 file changed, 31 deletions(-) diff --git a/drivers/net/ethernet/cirrus/mac89x0.c b/drivers/net/ethernet/cirrus/mac89x0.c index f910f0f386d6..4fd72c1a69f5

[PATCH net v2 2/9] net/mac89x0: Remove dead or unreachable code

Signed-off-by: Finn Thain --- drivers/net/ethernet/cirrus/mac89x0.c | 31 --- 1 file changed, 31 deletions(-) diff --git a/drivers/net/ethernet/cirrus/mac89x0.c b/drivers/net/ethernet/cirrus/mac89x0.c index f910f0f386d6..4fd72c1a69f5 100644 ---

[PATCH net v2 0/9] Fixes, cleanup and modernization for some legacy ethernet NIC drivers

This patch series fixes some logging bugs and adds some missing message severity levels. There are also cleanup patches for dead code and some Kconfig cruft. Custom debug message logging is converted to netif_* calls to reduce code duplication. All up, about 150 lines of code are eliminated.

[PATCH net v2 0/9] Fixes, cleanup and modernization for some legacy ethernet NIC drivers

This patch series fixes some logging bugs and adds some missing message severity levels. There are also cleanup patches for dead code and some Kconfig cruft. Custom debug message logging is converted to netif_* calls to reduce code duplication. All up, about 150 lines of code are eliminated.

Re: mptsas driver cannot detect hotplugging disk with the LSI SCSI SAS1068 controller in Ubuntu guest on VMware

On Mon, Oct 2, 2017 at 10:32 PM, Hannes Reinecke wrote: > On 09/27/2017 09:33 AM, Gavin Guo wrote: >> There is a problem in the latest upstream kernel with the device: >> >> $ grep -i lsi lspci >> 03:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios >> Logic SAS1068

Re: mptsas driver cannot detect hotplugging disk with the LSI SCSI SAS1068 controller in Ubuntu guest on VMware

On Mon, Oct 2, 2017 at 10:32 PM, Hannes Reinecke wrote: > On 09/27/2017 09:33 AM, Gavin Guo wrote: >> There is a problem in the latest upstream kernel with the device: >> >> $ grep -i lsi lspci >> 03:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios >> Logic SAS1068 PCI-X

[PATCH] kvm, mm: account kvm related kmem slabs to kmemcg

The kvm slabs can consume a significant amount of system memory and indeed in our production environment we have observed that a lot of machines are spending significant amount of memory that can not be left as system memory overhead. Also the allocations from these slabs can be triggered directly

[PATCH] kvm, mm: account kvm related kmem slabs to kmemcg

The kvm slabs can consume a significant amount of system memory and indeed in our production environment we have observed that a lot of machines are spending significant amount of memory that can not be left as system memory overhead. Also the allocations from these slabs can be triggered directly

Re: [RESEND PATCH 7/7] net: qrtr: Support decoding incoming v2 packets

From: Bjorn Andersson Date: Wed, 4 Oct 2017 20:51:05 -0700 > +/** > + * struct qrtr_hdr_v2 - (I|R)PCrouter packet header later versions > + * @version: protocol version > + * @type: packet type; one of QRTR_TYPE_* > + * @flags: bitmask of QRTR_FLAGS_* > + * @optlen:

Re: [RESEND PATCH 7/7] net: qrtr: Support decoding incoming v2 packets

From: Bjorn Andersson Date: Wed, 4 Oct 2017 20:51:05 -0700 > +/** > + * struct qrtr_hdr_v2 - (I|R)PCrouter packet header later versions > + * @version: protocol version > + * @type: packet type; one of QRTR_TYPE_* > + * @flags: bitmask of QRTR_FLAGS_* > + * @optlen: length of optional header

[PATCH v8 1/2] tracing: Prepare to add preempt and irq trace events

In preparation of adding irqsoff and preemptsoff enable and disable trace events, move required functions and code to make it easier to add these events in a later patch. This patch is just code movement and no functional change. Cc: Steven Rostedt Cc: Peter Zijlstra

[PATCH v8 1/2] tracing: Prepare to add preempt and irq trace events

In preparation of adding irqsoff and preemptsoff enable and disable trace events, move required functions and code to make it easier to add these events in a later patch. This patch is just code movement and no functional change. Cc: Steven Rostedt Cc: Peter Zijlstra Cc: kernel-t...@android.com

[PATCH v8 2/2] tracing: Add support for preempt and irq enable/disable events

Preempt and irq trace events can be used for tracing the start and end of an atomic section which can be used by a trace viewer like systrace to graphically view the start and end of an atomic section and correlate them with latencies and scheduling issues. This also serves as a prelude to using

[PATCH v8 2/2] tracing: Add support for preempt and irq enable/disable events

Preempt and irq trace events can be used for tracing the start and end of an atomic section which can be used by a trace viewer like systrace to graphically view the start and end of an atomic section and correlate them with latencies and scheduling issues. This also serves as a prelude to using

[PATCH v8 0/2] tracing: Add trace events for preemption and irq disable/enable

These patches add trace events support for preempt and irq disable/enable events. Here's an example of how Android's systrace will be using it to show atomic sections as a gantt chart: http://imgur.com/download/TZplEVp Other advantages of this initial work could be rewriting of preemptirqs off

[PATCH v8 0/2] tracing: Add trace events for preemption and irq disable/enable

These patches add trace events support for preempt and irq disable/enable events. Here's an example of how Android's systrace will be using it to show atomic sections as a gantt chart: http://imgur.com/download/TZplEVp Other advantages of this initial work could be rewriting of preemptirqs off

[PATCH 1/3] Drivers: hv: vmbus: Expose per-channel interrupts and events counters

From: Stephen Hemminger When investigating performance, it is useful to be able to look at the number of host and guest events per-channel. This is equivalent to per-device interrupt statistics. Signed-off-by: Stephen Hemminger Signed-off-by:

[PATCH 2/3] vmbus: initialize reserved fields in messages

From: Stephen Hemminger Make sure and initialize reserved fields in messages to host, rather than passing stack junk. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/channel.c | 2 ++ 1

[PATCH 1/3] Drivers: hv: vmbus: Expose per-channel interrupts and events counters

From: Stephen Hemminger When investigating performance, it is useful to be able to look at the number of host and guest events per-channel. This is equivalent to per-device interrupt statistics. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan ---

[PATCH 2/3] vmbus: initialize reserved fields in messages

From: Stephen Hemminger Make sure and initialize reserved fields in messages to host, rather than passing stack junk. Signed-off-by: Stephen Hemminger Signed-off-by: K. Y. Srinivasan --- drivers/hv/channel.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/hv/channel.c

[PATCH 3/3] Drivers: hv: vmbus: Make pannic reporting to be more useful

From: "K. Y. Srinivasan" Hyper-V allows the guest to report panic and the guest can pass additional information. All this is logged on the host. Currently Linux is passing back information that is not particularly useful. Make the following changes: 1. Windows uses crash MSR

[PATCH 3/3] Drivers: hv: vmbus: Make pannic reporting to be more useful

From: "K. Y. Srinivasan" Hyper-V allows the guest to report panic and the guest can pass additional information. All this is logged on the host. Currently Linux is passing back information that is not particularly useful. Make the following changes: 1. Windows uses crash MSR P0 to report

<    1   2   3   4   5   6   7   8   9   10   >