[PATCH v2 4/7] staging: lustre: use proper comment blocks for libcfs_hash.h

The script checkpatch.pl reported problems with the style of the comment blocks. This patch resolves those problems. Signed-off-by: James Simmons --- .../lustre/include/linux/libcfs/libcfs_hash.h | 21 +-- 1 files changed, 14 insertions(+), 7 deletions(-) diff --git a/dri

[PATCH v2 5/7] staging: lustre: handle NULL comparisons correctly for libcfs_hash.h

Remove all direct NULL comparisons in libcfs_hash.h. Signed-off-by: James Simmons --- .../lustre/include/linux/libcfs/libcfs_hash.h |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/lustre/include/linux/libcfs/libcfs_hash.h b/drivers/staging/lustre

[PATCH v2 1/7] staging: lustre: remove white space in libcfs_hash.h

Cleanup all the unneeded white space in libcfs_hash.h. Signed-off-by: James Simmons --- .../lustre/include/linux/libcfs/libcfs_hash.h | 135 ++-- 1 files changed, 70 insertions(+), 65 deletions(-) diff --git a/drivers/staging/lustre/include/linux/libcfs/libcfs_hash.h b/dr

Re: [PATCH] bpf: convert hashtab lock to raw lock

On Mon, 02 Nov 2015 09:12:29 -0800 "Shi, Yang" wrote: > Yes, it is common practice for converting sleepable spin lock to raw > spin lock in -rt to avoid scheduling in atomic context bug. Note, in a lot of cases we don't just convert spin_locks to raw because of atomic context. There's times we

[PATCH v2 0/7] staging: lustre: second series for libcfs hash code cleanup

This patch covers more style cleanup series for the libcfs hash code. Mostly removal of white spaces and resolving the checkpath issues in libcfs_hash.h. James Simmons (7): staging: lustre: remove white space in libcfs_hash.h staging: lustre: remove obsolete comment in libcfs_hash.h staging:

RE: [PATCH v4 RFC net] i40e: Look up MAC address in Open Firmware or IDPROM

> -Original Message- > From: Sowmini Varadhan [mailto:sowmini.varad...@oracle.com] > Sent: Sunday, November 01, 2015 8:25 AM > > This is the i40e equivalent of commit c762dff24c06 ("ixgbe: Look up MAC > address in Open Firmware or IDPROM"). > > As with that fix, attempt to look up the M

Re: [PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver

On 11/02/2015 10:20 AM, Sinan Kaya wrote: Is there a good example I can look or a wiki about the device-tree naming conventions? I'm more of an ACPI person than DTS. I think Rob is talking about something like this: compatible="qcom,hidma-mgmt-1.0", "qcom,hidma-mgmt" This specifies

Re: [RFC 0/8] Add support for NVIDIA Tegra XUSB

Hi Martyn, On Mon, Nov 2, 2015 at 3:55 AM, Martyn Welch wrote: > This series is based on commits that can be found in the git tree here: > > https://github.com/thierryreding/linux/commits/staging/xhci > > I have included the patches I've used from that tree as patches 1-5. > > The above patches w

Re: [PATCH v2 1/4] clocksource: rockchip: Make the driver more compatible

On 10/31/2015 12:47 AM, Heiko Stuebner wrote: Hi Daniel, Am Freitag, 30. Oktober 2015, 11:42:29 schrieb Daniel Lezcano: On 10/30/2015 04:43 AM, Caesar Wang wrote: Hi Daniel, 在 2015年10月01日 03:14, Heiko Stübner 写道: Hi Daniel, Am Dienstag, 29. September 2015, 06:18:03 schrieb Daniel Lezcano:

Re: [PATCH] bpf: convert hashtab lock to raw lock

On 11/02/2015 06:12 PM, Shi, Yang wrote: ... If you think such info is necessary, I definitely could add it into the commit log in v2. As this is going to be documented anyway (thanks! ;)), and the discussion to this patch can be found in the archives for those wondering, I'm good: Acked-by:

Re: [PATCH] bpf: convert hashtab lock to raw lock

On 11/2/2015 9:24 AM, Steven Rostedt wrote: On Mon, 02 Nov 2015 09:12:29 -0800 "Shi, Yang" wrote: Yes, it is common practice for converting sleepable spin lock to raw spin lock in -rt to avoid scheduling in atomic context bug. Note, in a lot of cases we don't just convert spin_locks to raw b

Re: [PATCH v6 2/3] percpu: add PERCPU_ATOM_SIZE for a generic percpu area setup

On Mon, Nov 02, 2015 at 10:48:17AM -0600, Christoph Lameter wrote: > On Mon, 2 Nov 2015, Catalin Marinas wrote: > > I haven't looked at the patch 3/3 in detail but I'm pretty sure I'll NAK > > the approach (and the definition of PERCPU_ATOM_SIZE), therefore > > rendering this patch unnecessary. IIU

Re: [RFC 0/8] Add support for NVIDIA Tegra XUSB

On 02/11/15 17:27, Andrew Bresticker wrote: Hi Martyn, On Mon, Nov 2, 2015 at 3:55 AM, Martyn Welch wrote: This series is based on commits that can be found in the git tree here: https://github.com/thierryreding/linux/commits/staging/xhci I have included the patches I've used from that tre

Re: [RFC PATCH net-next] net/core: initial support for stacked dev feature toggles

Alexander Duyck wrote: On 10/30/2015 09:25 AM, Jarod Wilson wrote: ... Rather than outright dropping the second bit though, I was thinking maybe just drop a note in dmesg along the lines of "hey, you shut off LRO, it is still enabled on upper dev foo", to placate end-users. I would rather not

Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

On 11/02/2015 01:32 AM, Andrey Ryabinin wrote: > And the major factor here is number 2. > > In your dmesg: > [ 67.891156] rbtree testing -> 570841 cycles > [ 88.609636] augmented rbtree testing > [ 116.546697] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! > [swapper/0:1] > > > I've

Re: [PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes

On 11/01/2015 06:50 PM, Hillf Danton wrote: > Andrew, please correct me if I miss/mess anything. > >>> This hunk is already in the next tree, see below please. >>> >> >> Ah, the whole series to add shmem like code to handle hole punch/fault >> races is in the next tree. It has been determined th

Re: [PATCH 4/4] locking: Introduce smp_cond_acquire()

Hi Peter, On Mon, Nov 02, 2015 at 02:29:05PM +0100, Peter Zijlstra wrote: > Introduce smp_cond_acquire() which combines a control dependency and a > read barrier to form acquire semantics. > > This primitive has two benefits: > - it documents control dependencies, > - its typically cheaper than

Re: [PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver

On Mon, Nov 2, 2015 at 11:26 AM, Timur Tabi wrote: > On 11/02/2015 10:20 AM, Sinan Kaya wrote: >>> >>> >> Is there a good example I can look or a wiki about the device-tree >> naming conventions? There are many examples. Generally, it is the form of: ,- >> >> I'm more of an ACPI person than DTS

Re: [PATCH RFC] tpm: seal with a policy

On Mon, Nov 02, 2015 at 07:48:42AM -0500, Mimi Zohar wrote: > On Sat, 2015-10-31 at 17:53 +0200, Jarkko Sakkinen wrote: > > Support for sealing with a policy. > > > > Two new options for trusted keys: > > > > * 'policydigest=': provide a policydigest for the seal operation. > > * 'policyhandle=':

Re: Problems with 'mtd: warn when registering the same master many times'

On Mon, Nov 02, 2015 at 07:41:48AM -0800, Guenter Roeck wrote: > Brian, > > I see the following warnings in recent mips qemu tests on linux-next. > > WARNING: CPU: 0 PID: 1 at drivers/mtd/mtdcore.c:619 > mtd_device_parse_register+0x160/0x16c() > MTD already registered > > Looking into the code,

Re: [PATCH 4/4] locking: Introduce smp_cond_acquire()

On Mon, Nov 02, 2015 at 02:57:26PM +0100, Peter Zijlstra wrote: > On Mon, Nov 02, 2015 at 02:29:05PM +0100, Peter Zijlstra wrote: > > > Note that while smp_cond_acquire() has an explicit > > smp_read_barrier_depends() for Alpha, neither sites it gets used in > > were actually buggy on Alpha for th

[PATCH] MAINTAINERS: update for intel Pstate driver

Added Len Brown and Srinivas Pandruvada as maintainers. Signed-off-by: Srinivas Pandruvada --- MAINTAINERS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 747c653..d263f4a 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -5429,7 +5429,8 @@ S:

Re: [PATCH v2 1/2] usb: dwc2: optionally assert phy "full reset" when waking up

Hi, On Mon, Nov 2, 2015 at 9:16 AM, Rob Herring wrote: > On Mon, Nov 2, 2015 at 10:22 AM, Doug Anderson wrote: >> Rob, >> >> On Mon, Nov 2, 2015 at 8:12 AM, Rob Herring wrote: >>> On Fri, Oct 30, 2015 at 3:17 PM, Douglas Anderson >>> wrote: From: Doug Anderson > We can get the PHY

Re: [PATCH v2 1/3] keys, trusted: select the hash algorithm

On Mon, Nov 02, 2015 at 07:16:49AM -0500, Mimi Zohar wrote: > On Fri, 2015-10-30 at 13:35 +0200, Jarkko Sakkinen wrote: > > > @@ -787,6 +791,20 @@ static int getoptions(char *c, struct > > trusted_key_payload *pay, > > return -EINVAL; > > opt->pcrlo

Re: [PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver

On 11/02/2015 11:42 AM, Rob Herring wrote: On Mon, Nov 2, 2015 at 11:26 AM, Timur Tabi wrote: >On 11/02/2015 10:20 AM, Sinan Kaya wrote: >>> >>> >>Is there a good example I can look or a wiki about the device-tree >>naming conventions? There are many examples. Generally, it is the form of:

Re: question about commit "proc: make proc_fd_permission() thread-friendly"

Hi Jin, (add lkml) On 11/02, Jin, Yihua wrote: > > --- > a/fs/proc/fd.c > +++ > b/fs/proc/fd.c

Re: Flush requests not going through IO scheduler

Jan Kara writes: > Hello, > > when looking into a performance issue, I've noticed one interesting thing > in blktrace data: Hi Jan, Do you have a reproducer I can run? Thanks, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@

[PATCH net-next] net/core: generic support for disabling netdev features down stack

There are some netdev features, which when disabled on an upper device, such as a bonding master or a bridge, must be disabled and cannot be re-enabled on underlying devices. This is a rework of an earlier more heavy-handed appraoch, which simply disables and prevents re-enabling of netdev feature

[PATCH] livepatch: old_name.number scheme in livepatch sysfs directory

The following directory structure will allow for cases when the same function name exists in a single object. /sys/kernel/livepatch/// The number is incremented on each known initialized func kobj thus creating unique names in this case. An example of this issue is documented here:

Re: [PATCH] namei: permit linking with CAP_FOWNER in userns

Quoting Dirk Steinmetz (pub...@rsjtdrjgfuzkfg.com): > On Wed, 28 Oct 2015 17:33:10 +, Serge Hallyn wrote: > > Quoting Dirk Steinmetz (pub...@rsjtdrjgfuzkfg.com): > > > On Tue, 27 Oct 2015 20:28:02 +, Serge Hallyn wrote: > > > > Quoting Dirk Steinmetz (pub...@rsjtdrjgfuzkfg.com): > > > > > O

Re: [PATCH] block: genhd: Add disk/partition specific uevent callbacks for partition info

Hi John, John Stultz writes: > From: San Mehat > > This patch has been carried in the Android tree for quite some > time and is one of the few patches required to get a mainline > kernel up and running with an exsiting Android userspace. So I > wanted to submit it for review and consideration i

Re: [PATCH net-next] net/core: generic support for disabling netdev features down stack

On 11/02/2015 09:53 AM, Jarod Wilson wrote: There are some netdev features, which when disabled on an upper device, such as a bonding master or a bridge, must be disabled and cannot be re-enabled on underlying devices. This is a rework of an earlier more heavy-handed appraoch, which simply disab

Kernel 4.3 breaks security in systems using capabilities

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I read recently about patch 58319057b7847667f0c9585b9de0e8932b0fdb08 which made it into kernel 4.3 recently. And I have to say that I was shocked on how could such a patch that breaks normal use of capabilities make it into the kernel. Usually

Re: [PATCH 01/70] cpufreq: interactive: New 'interactive' governor

On 11/02/2015 06:02 AM, Peter Zijlstra wrote: > On Wed, Oct 28, 2015 at 08:30:42AM +0530, Viresh Kumar wrote: >> These are the last memories I have around upstreaming this governor: >> http://marc.info/?l=linux-kernel&m=132867057910479&w=2 >> >> Has anything changed after that? Or we decided to go

Re: [PATCH 4/4] locking: Introduce smp_cond_acquire()

On Mon, Nov 2, 2015 at 5:29 AM, Peter Zijlstra wrote: > +#define smp_cond_acquire(cond) do {\ > + while (!(cond)) \ > + cpu_relax();\ > + smp_read_barrier_depends(); /* ctrl */ \ > + smp_rmb(); /* ctrl + rmb :

Re: [patch 3/3] vmstat: Create our own workqueue

On Tue, 3 Nov 2015, Tetsuo Handa wrote: > I'm still unclear. I think that the result of this patchset is > > The counters are never updated even after stat_interval > if some workqueue item is doing a __GFP_WAIT memory allocation. > > but the patch description sounds as if > > The counters w

Re: [PATCH v6 2/3] percpu: add PERCPU_ATOM_SIZE for a generic percpu area setup

On Mon, 2 Nov 2015, Catalin Marinas wrote: > On Mon, Nov 02, 2015 at 10:48:17AM -0600, Christoph Lameter wrote: > > On Mon, 2 Nov 2015, Catalin Marinas wrote: > > > I haven't looked at the patch 3/3 in detail but I'm pretty sure I'll NAK > > > the approach (and the definition of PERCPU_ATOM_SIZE),

Re: linux-next: build failure after merge of the pci tree

On Sun, Nov 1, 2015 at 6:00 PM, Ley Foon Tan wrote: > On Isn, 2015-11-02 at 02:23 +1100, Stephen Rothwell wrote: >> Hi Bjorn, >> >> After merging the pci tree, today's linux-next build (powerpc >> allyesconfig) failed like this: >> >> In file included from include/linux/kvm_host.h:20:0, >>

Re: [PATCH v2 2/5] mfd: ts4800-syscon: add driver for TS-4800 syscon

On Mon, Nov 02, 2015 at 09:12:53AM +, Lee Jones wrote: > [Cc'ing Arnd] > > On Fri, 30 Oct 2015, Damien Riegel wrote: > > On Fri, Oct 30, 2015 at 05:56:56PM +, Lee Jones wrote: > > > On Thu, 29 Oct 2015, Damien Riegel wrote: > > > > > > > Driver for TS-4800 syscon. These registers belong t

Re: [PATCH v4 1/6] arm64: ftrace: adjust callsite addresses examined by stack tracer

On Fri, 30 Oct 2015 11:16:19 + Will Deacon wrote: > On Fri, Oct 30, 2015 at 02:25:36PM +0900, AKASHI Takahiro wrote: > > On arm64, no PC values returned by save_stack_trace() will match to LR > > values saved in stack frames on a stack after the following commit: > > commit e306dfd06fcb (

Re: [PATCH] tracing: fix compiler warnings in trace_events.c

On Mon, 2 Nov 2015 00:00:43 -0800 Geliang Tang wrote: > Fix the following warnings: > kernel/trace/trace_events.c: In function '__ftrace_clear_event_pids': > kernel/trace/trace_events.c:579: warning: passing argument 1 of > 'unregister_trace_sched_switch' from incompatible pointer type >

Re: [PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver

On Mon, Nov 2, 2015 at 11:48 AM, Timur Tabi wrote: > On 11/02/2015 11:42 AM, Rob Herring wrote: >> >> On Mon, Nov 2, 2015 at 11:26 AM, Timur Tabi wrote: >>> >>> >On 11/02/2015 10:20 AM, Sinan Kaya wrote: > > >>> > >>> >>Is there a good example I can look or a wiki about the

Re: [PATCH] recordmcount: arm64: replace the ignored mcount call into nop

On Fri, 30 Oct 2015 14:00:28 +0800 libin wrote: > It is a bug in nop_mcount: > ... > if (mcountsym == Elf_r_sym(relp) && !is_fake_mcount(relp)) { > if (make_nop) { > ret = make_nop((void *)ehdr, shdr->sh_offset + > relp->r_offset); > } > ... > > shdr->sh_offset a

Re: [PATCH] recordmcount: arm64: replace the ignored mcount call into nop

On Mon, Nov 02, 2015 at 01:26:08PM -0500, Steven Rostedt wrote: > On Fri, 30 Oct 2015 14:00:28 +0800 > libin wrote: > > > It is a bug in nop_mcount: > > ... > > if (mcountsym == Elf_r_sym(relp) && !is_fake_mcount(relp)) { > > if (make_nop) { > > ret = make_nop((void *)ehdr

Re: [PATCH v4 1/6] arm64: ftrace: adjust callsite addresses examined by stack tracer

On Mon, Nov 02, 2015 at 01:20:43PM -0500, Steven Rostedt wrote: > On Fri, 30 Oct 2015 11:16:19 + > Will Deacon wrote: > > > On Fri, Oct 30, 2015 at 02:25:36PM +0900, AKASHI Takahiro wrote: > > > On arm64, no PC values returned by save_stack_trace() will match to LR > > > values saved in stack

Re: [PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver

On 11/02/2015 12:25 PM, Rob Herring wrote: Then document it with "" and fill that in later. Just don't make up version numbers. I don't think you understand. We literally have no name for our chip. The closest is what I used on the pin control driver, "qdf2xxx", which really doesn't say anyt

Re: [PATCH v6 2/3] percpu: add PERCPU_ATOM_SIZE for a generic percpu area setup

On Mon, Nov 02, 2015 at 12:11:33PM -0600, Christoph Lameter wrote: > On Mon, 2 Nov 2015, Catalin Marinas wrote: > > > On Mon, Nov 02, 2015 at 10:48:17AM -0600, Christoph Lameter wrote: > > > On Mon, 2 Nov 2015, Catalin Marinas wrote: > > > > I haven't looked at the patch 3/3 in detail but I'm pret

Re: [PATCH] block: genhd: Add disk/partition specific uevent callbacks for partition info

On Mon, Nov 2, 2015 at 10:03 AM, Jeff Moyer wrote: > Hi John, > > John Stultz writes: > >> From: San Mehat >> >> This patch has been carried in the Android tree for quite some >> time and is one of the few patches required to get a mainline >> kernel up and running with an exsiting Android users

[PATCH RESEND v4 1/2] dt-bindings: Add new SoCs to bcm4708 DT bindings

Add the 4708, 4709, and 53012 SoCs to the the documentation for the Broadcom Northstar device tree bindings. Signed-off-by: Jon Mason Acked-by: Hauke Mehrtens Acked-by: Scott Branden Acked-by: Rob Herring --- Documentation/devicetree/bindings/arm/bcm/brcm,bcm4708.txt | 7 +++ 1 file chang

[PATCH RESEND v4 2/2] ARM: dts: bcm5301x: Add BCM SVK DT files

Add device tree files for Broadcom Northstar based SVKs. Since the bcm5301x.dtsi already exists, all that is necessary is the dts files to enable the UARTs. With these files, the SVKs are able to boot to shell. Signed-off-by: Jon Mason --- arch/arm/boot/dts/Makefile | 5 +++- arch/arm/b

[PATCH RESEND v4 0/2] ARM: dts: bcm5301x: Add SVK DT files and docs

Resending due to lack of any response to the original v4 series Changes in v4: * Changed bootargs to stdout-path, per Sudeep Holla Changes in v3: * Updated the DT documentation compat strings * Modified the include files and compat strings for the SVK DT files, per Hauke Mehrtens Changes in v2

Re: [RFC PATCHv3 3/4] x86/pci: Initial commit for new VMD device driver

Keith! On Tue, 27 Oct 2015, Keith Busch wrote: I'm just looking at the interrupt part of the patch and it's way better than the first version I looked at. > 4) Interrupts: Part of VMD's BAR 4 is reserved for VMD's MSI-X Table and > PBA. MSIs from VMD domain devices and ports are remapped to

mm: remove vmalloc info from /proc/meminfo

Reading /proc/meminfo is really slow, as it requires recomputing the vmalloc data every time, which is a lot of work, when most (all?) consumers of meminfo don't even care about those statistics. Linus mentioned[*] that he wanted to just remove these fields from this file, and just break the ABI i

Re: [PATCH 4/4] locking: Introduce smp_cond_acquire()

On Mon, Nov 02, 2015 at 10:08:24AM -0800, Linus Torvalds wrote: > On Mon, Nov 2, 2015 at 5:29 AM, Peter Zijlstra wrote: > > +#define smp_cond_acquire(cond) do {\ > > + while (!(cond)) \ > > + cpu_relax();\ > > + smp_

Re: Kernel 4.3 breaks security in systems using capabilities

CC'ing patch authors. On Mon, Nov 2, 2015 at 7:06 PM, Klaus Ethgen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi, > > I read recently about patch 58319057b7847667f0c9585b9de0e8932b0fdb08 > which made it into kernel 4.3 recently. And I have to say that I was > shocked on how co

Re: [PATCH 2/2] mm: kasan: unified support for SLUB and SLAB allocators

I must admit the original patch was of poor quality, and my decision to submit it unchanged wasn't a well-thought one. I'll probably need to rework it and send again. The idea behind removing the alloc/dealloc stacks was to replace them with a better stack storage in https://github.com/steelanneli

[PATCH RESEND 0/3] ARM: dts: NSP: Add PCI, NAND, and TWD Support to DT

Resending due to lack of any response to the original series Add PCI, NAND, and TWD Support to the Broadcom Northstar Plus SoC device tree file. Since no driver changes are needed to enable these pieces of hardware, only the device tree changes are required to make them functional. Jon Mason (3)

[PATCH RESEND 2/3] ARM: dts: NSP: Add NAND Support to DT

Add NAND support to the device tree for the Broadcom Northstar Plus SoC. Since no driver changes are needed to enable this hardware, only the device tree changes are required to make this functional. Signed-off-by: Jon Mason --- arch/arm/boot/dts/bcm-nsp.dtsi | 16 +++- arch/arm/bo

[PATCH RESEND 3/3] ARM: dts: NSP: Add TWD Support to DT

Add support for the ARM TWD Timer and Watchdog to the Northstar Plus device tree. Signed-off-by: Jon Mason --- arch/arm/boot/dts/bcm-nsp.dtsi | 16 1 file changed, 16 insertions(+) diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi index 62bc86f..4bcdd

Re: [PATCH v4 1/6] arm64: ftrace: adjust callsite addresses examined by stack tracer

On Mon, Nov 02, 2015 at 06:29:28PM +, Mark Rutland wrote: > On Mon, Nov 02, 2015 at 01:20:43PM -0500, Steven Rostedt wrote: > > On Fri, 30 Oct 2015 11:16:19 + > > Will Deacon wrote: > > > > > On Fri, Oct 30, 2015 at 02:25:36PM +0900, AKASHI Takahiro wrote: > > > > On arm64, no PC values r

[PATCH RESEND 1/3] ARM: dts: NSP: Add PCI support

Add PCI support to the Northstar Plus SoC. This uses the existing pcie-iproc driver. So, all that is needed is device tree entries in the DTS. Signed-off-by: Jon Mason --- arch/arm/boot/dts/bcm-nsp.dtsi | 74 +++- arch/arm/boot/dts/bcm958625k.dts | 12

Re: [PATCH v4 1/6] arm64: ftrace: adjust callsite addresses examined by stack tracer

On Mon, Nov 02, 2015 at 06:41:24PM +, Will Deacon wrote: > On Mon, Nov 02, 2015 at 06:29:28PM +, Mark Rutland wrote: > > On Mon, Nov 02, 2015 at 01:20:43PM -0500, Steven Rostedt wrote: > > > On Fri, 30 Oct 2015 11:16:19 + > > > Will Deacon wrote: > > > > > > > On Fri, Oct 30, 2015 at

Re: [PATCH RESEND 0/3] ARM: dts: NSP: Add PCI, NAND, and TWD Support to DT

On 02/11/15 10:40, Jon Mason wrote: > Resending due to lack of any response to the original series > > Add PCI, NAND, and TWD Support to the Broadcom Northstar Plus SoC device > tree file. Since no driver changes are needed to enable these pieces of > hardware, only the device tree changes are re

Re: [PATCH 1/2] perf/x86/intel/pt: Add interface to stop Intel PT logging

Takao, On Wed, 28 Oct 2015, Takao Indoh wrote: > +#if defined(CONFIG_PERF_EVENTS) && defined(CONFIG_CPU_SUP_INTEL) > +void cpu_emergency_stop_pt(void); > +#else > +void cpu_emergency_stop_pt(void) {} This wants to be static inline void please. Thanks, tglx -- To unsubscribe from

Re: [PATCH RESEND v4 0/2] ARM: dts: bcm5301x: Add SVK DT files and docs

On 02/11/15 10:34, Jon Mason wrote: > Resending due to lack of any response to the original v4 series > > Changes in v4: > * Changed bootargs to stdout-path, per Sudeep Holla > > Changes in v3: > * Updated the DT documentation compat strings > * Modified the include files and compat strings for t

Re: linux-next: Tree for Nov 1 (xconfig problem)

On 11/02/15 08:58, Thiago Macieira wrote: > On Monday 02 November 2015 08:44:01 Randy Dunlap wrote: >>> Randy, we need a backtrace. The problem is on the function that called >>> first(). Can you make sure the crash generates a core dump, then get the >>> bt >>> from that? >> >> ASSERT: "!isEmpty()

Re: [PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver

On 11/2/2015 12:42 PM, Rob Herring wrote: Except I was suggesting not using 1.0 or 1.1. There is one main exception and that is Xilinx blocks, but they are releasing versions of blocks to customers. If "1.0" is not a well defined number, then don't use that. I'd be surprised if any SOC vendor h

Re: Kernel 4.3 breaks security in systems using capabilities

On Mon, Nov 2, 2015 at 10:38 AM, Richard Weinberger wrote: > CC'ing patch authors. > > On Mon, Nov 2, 2015 at 7:06 PM, Klaus Ethgen wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> Hi, >> >> I read recently about patch 58319057b7847667f0c9585b9de0e8932b0fdb08 >> which made it in

[PATCH] selftests/seccomp: Be more precise with syscall arguments.

Certain syscall emulation layers strictly check that the number of arguments match what the syscall handler expects. The KILL_one_arg_one and KILL_one_arg_six tests passed more parameters than expected to various syscalls, causing failures in this emulation mode. Instead, test using syscalls that t

Re: Kernel 4.3 breaks security in systems using capabilities

On Mon, Nov 2, 2015 at 10:38 AM, Richard Weinberger wrote: >> >> With the patch above, any process that is spawned by such a program will >> inherit the raised capabilities if it has no own filecapabilities set. Do you actually have a real example of this? The ambient capabilities stay empty unl

[PATCH 1/2] thermal: devfreq_cooling: use a thermal_cooling_device for register and unregister

Be consistent with what other cooling devices do and return a struct thermal_cooling_device * on register. Also, for the unregister, accept a struct thermal_cooling_device * as parameter. Cc: Zhang Rui Cc: Eduardo Valentin Signed-off-by: Javi Merino --- drivers/thermal/devfreq_cooling.c | 16

[PATCH 0/2] Fixes for devfreq cooling

When devfreq cooling entered Eduardo's tree, the kbuild test robot spotted a compilation warning on sh. Also, the first patch aligns the return type and the parameters of the devfreq register/unregister with those of the cpu cooling device. This patches apply on top of eduardo/next. Javi Merino

Re: [RFC][PATCH] Oops messages transfer using QR codes

On 10/30/2015 08:03 AM, Murtaza Alexandru wrote: This patch is continued from this previous RFC: https://lkml.org/lkml/2014/3/17/525 If the config option for this feature is enabled, then when an Oops is in progress, the printk() calls' strings are buffered. When the Oops finishes, the buffer is

[PATCH 2/2] thermal: devfreq_cooling: Make power a u64

The prototype of do_div() is: uint32_t do_div(uint64_t *n, uint32_t base); Make power u64 to avoid the following warning: drivers/thermal/devfreq_cooling.c: In function 'get_dynamic_power': drivers/thermal/devfreq_cooling.c:267:2: warning: comparison of distinct pointer types lacks a cast

Re: [PATCH 3/3] tracing: Apply tracer specific options from kernel command line.

On Sun, 18 Oct 2015 19:58:10 +0800 Jiaxing Wang wrote: > +static int __init apply_trace_boot_options(void) > +{ > + char *option; > + char *buf; > + char *str; > + size_t len; > + > + if (trace_boot_options) { > + len = strlen(trace_boot_options); > + > +

Re: [PATCH] tracefs, debugfs: fix refcount imbalance in start_creating

On Fri, 9 Oct 2015 20:30:10 +0200 Daniel Borkmann wrote: > In tracefs' start_creating(), we pin the file system to safely access > its root. When we failed to create a file, we unpin the file system via > failed_creating() to release the mount count and eventually the reference > of the vfsmount

Re: [PATCH] x86/irq: Probe for PIC presence before allocating descs for legacy IRQs

Vitaly! On Mon, 2 Nov 2015, Vitaly Kuznetsov wrote: > Commit d32932d02e18 ("x86/irq: Convert IOAPIC to use hierarchical irqdomain > interfaces") brought a regression for Hyper-V Gen2 instances. These > instances don't have i8259 legacy PIC but they use legacy IRQs for serial > port, rtc, and acpi.

Re: [PATCH v6 1/3] percpu: remove PERCPU_ENOUGH_ROOM which is stale definition

On Sun, Nov 01, 2015 at 07:46:15AM +, Jungseok Lee wrote: > As pure cleanup, this patch removes PERCPU_ENOUGH_ROOM which is not > used any more. That is, no code refers to the definition. > > Signed-off-by: Jungseok Lee Applied to percpu/for-4.4. Thanks. -- tejun -- To unsubscribe from th

Re: Resource leak in unshare

Dmitry Vyukov writes: > Hello, > > I am hitting the following warnings on > bcee19f424a0d8c26ecf2607b73c690802658b29 (4.3): Do you have any trace of the earlier failures? This appears to be something caused by an earlier failure (possibly whatever fails to allocate memory). Having network devi

Re: [patch 3/3] vmstat: Create our own workqueue

On Mon, Nov 02, 2015 at 12:10:04PM -0600, Christoph Lameter wrote: > Well true that is dependend on the correct workqueue operation. I though > that was fixed by Tejun? At least for now, we're going with Tetsuo's short sleep patch. Thanks. -- tejun -- To unsubscribe from this list: send the lin

Re: [PATCH] PM / OPP: Protect updates to list_dev with mutex

On 10/31, Viresh Kumar wrote: > On 30-10-15, 10:06, Stephen Boyd wrote: > > On 10/30, Viresh Kumar wrote: > > > dev_opp_list_lock is used everywhere to protect device and OPP lists, > > > but dev_pm_opp_set_sharing_cpus() is missed somehow. And instead we used > > > rcu-lock, which wouldn't help he

Re: livepatch: old_name.number scheme in livepatch sysfs directory

+++ Chris J Arges [02/11/15 11:58 -0600]: The following directory structure will allow for cases when the same function name exists in a single object. /sys/kernel/livepatch/// The number is incremented on each known initialized func kobj thus creating unique names in this case. An exam

Re: [KERNEL] Re: Kernel 4.3 breaks security in systems using capabilities

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Mo den 2. Nov 2015 um 19:50 schrieb Andy Lutomirski: > >> I read recently about patch 58319057b7847667f0c9585b9de0e8932b0fdb08 > >> which made it into kernel 4.3 recently. And I have to say that I was > >> shocked on how could such a patch t

Re: [PATCH 4/4] locking: Introduce smp_cond_acquire()

On Mon, Nov 2, 2015 at 10:37 AM, Will Deacon wrote: > On Mon, Nov 02, 2015 at 10:08:24AM -0800, Linus Torvalds wrote: >> On Mon, Nov 2, 2015 at 5:29 AM, Peter Zijlstra wrote: >> > +#define smp_cond_acquire(cond) do {\ >> > + while (!(cond)) \ >> > +

Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding

On 10/31, Viresh Kumar wrote: > On 30-10-15, 15:18, Stephen Boyd wrote: > > > Also, this makes it sound like opp-supported-hw is really just > > telling us if this is a supported frequency or not for the > > particular device we're running on. > > That's right. > > > The current wording makes it

Re: [PATCH] mm,vmscan: Use accurate values for zone_reclaimable() checks

On Mon, Nov 02, 2015 at 04:01:37PM +0100, Michal Hocko wrote: ... > which is perfectly suited for the stable backport, OOM sysrq resp. any > sysrq which runs from the WQ context should be as robust as possible and > shouldn't rely on all the code running from WQ context to issue a sleep > to get un

Re: [PATCH 1/3] PM / OPP: Add "opp-supported-hw" binding

On 10/31, Viresh Kumar wrote: > On 30-10-15, 14:49, Stephen Boyd wrote: > > I suppose if you wanted to have 64 possible combinations of some > > attribute you would just extend it to two 32 bit numbers in > > sequence? I don't see the limitation here, and hopefully there > > isn't a limitation so t

Re: [PATCH 2/2] dma: add Qualcomm Technologies HIDMA channel driver

On 11/2/2015 11:33 AM, Arnd Bergmann wrote: On Sunday 01 November 2015 13:50:53 Sinan Kaya wrote: The issue is not writel_relaxed vs. writel. After I issue reset, I need wait for some time to confirm reset was done. I can use readl_polling instead of mdelay if we don't like mdelay. I meant t

Re: linux-next: Tree for Nov 1 (xconfig problem)

On Monday 02 November 2015 10:48:00 Randy Dunlap wrote: > Hi, > What does this patch apply to? > I can't apply it cleanly to to 4.3 or linux-next of yesterday or today. Hmm... interesting, it doesn't apply on linux-next. The reason for that is that the code on linux-next is different from the one

Re: mm: remove vmalloc info from /proc/meminfo

On Mon, Nov 2, 2015 at 10:36 AM, Dave Jones wrote: > Reading /proc/meminfo is really slow, as it requires recomputing the > vmalloc data every time, which is a lot of work, when most (all?) > consumers of meminfo don't even care about those statistics. Ahh. My version of this patch (which I actua

[v4.1.10-rt10] [PATCH 2/2] PCI: dra7xx: fix "WARNING: CPU: 1 PID: 82 at kernel/irq/handle.c:150 handle_irq_event_percpu"

Use generic_handle_irq_rt_wa() to W/A below backtrace, which is triggered because dra7xx_pcie_msi_irq_handler() forced to be threaded on -RT: [ cut here ] WARNING: CPU: 1 PID: 82 at kernel/irq/handle.c:150 handle_irq_event_percpu+0x14c/0x174() irq 460 handler irq_default_p

[v4.1.10-rt10][PATCH 0/2] PCI: dra7xx/dwc: fix "WARNING: CPU: 1 PID: 82 at kernel/irq/handle.c:150 handle_irq_event_percpu"

Now in kernel below code pattern is used by many drivers: static irqreturn_t driver_xx_hw_irq_handler(int irq, void *arg) { for () { generic_handle_irq(); |- handle_simple_irq() |-or- handle_level_irq()

[v4.1.10-rt10][PATCH 1/2] genirq: introduce new generic_handle_irq_rt_wa() api

Now in kernel below code pattern is used by many drivers: static irqreturn_t driver_xx_hw_irq_handler(int irq, void *arg) { for () { generic_handle_irq(); |- handle_simple_irq() |-or- handle_level_irq()

RE: [PATCH v6 01/15] scsi: ufs: clear UTRD, UPIU req and rsp before new transfers

> + cdb_len = min_t(unsigned short, lrbp->cmd->cmd_len, MAX_CDB_SIZE); > + memcpy(ucd_req_ptr->sc.cdb, lrbp->cmd->cmnd, cdb_len); > + if (cdb_len < MAX_CDB_SIZE) > + memset(ucd_req_ptr->sc.cdb + cdb_len, 0, > +(MAX_CDB_SIZE - cdb_len)); It's just 16 byt

Re: [PATCH 1/3] recordmcount: fix endianness handling bug for nop_mcount

On Sat, 31 Oct 2015 10:07:38 +0800 libin wrote: > > > on 2015/10/30 22:35, Sergei Shtylyov wrote: > > Hello. > > > > On 10/30/2015 11:31 AM, Li Bin wrote: > > > >> In nop_mcount, shdr->sh_offset and welp->r_offset should handle > >> endianness properly, otherwise it will trigger Segmentation

Re: [PATCH] recordmcount: arm64: replace the ignored mcount call into nop

On Mon, 2 Nov 2015 18:28:37 + Will Deacon wrote: > I see you're playing "chase the patches" at the moment ;) > Why yes I am! Trying to grab last minute patches from my INBOX (or they could be old patches that I just missed), before kicking off my 12 hour test suite. -- Steve -- To unsubsc

Re: [lkp] [fs] df4c0e36f1: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:1]

2015-11-02 20:39 GMT+03:00 Dave Hansen : > On 11/02/2015 01:32 AM, Andrey Ryabinin wrote: >> And the major factor here is number 2. >> >> In your dmesg: >> [ 67.891156] rbtree testing -> 570841 cycles >> [ 88.609636] augmented rbtree testing >> [ 116.546697] NMI watchdog: BUG: soft lockup - CP

Re: [v4.1.10-rt10][PATCH 1/2] genirq: introduce new generic_handle_irq_rt_wa() api

On Mon, 2 Nov 2015, Grygorii Strashko wrote: > Now in kernel below code pattern is used by many drivers: > static irqreturn_t driver_xx_hw_irq_handler(int irq, void *arg) > { > > > > for () { > > generic_handle_irq(); > |- handle_simpl

Re: [KERNEL] Re: Kernel 4.3 breaks security in systems using capabilities

On Mon, Nov 2, 2015 at 11:16 AM, Klaus Ethgen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi, > > Am Mo den 2. Nov 2015 um 19:50 schrieb Andy Lutomirski: >> >> I read recently about patch 58319057b7847667f0c9585b9de0e8932b0fdb08 >> >> which made it into kernel 4.3 recently. And

[GIT PULL] regmap updates for v4.4

The following changes since commit 25cb62b76430a91cc6195f902e61c2cb84ade622: Linux 4.3-rc5 (2015-10-11 11:09:45 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.4 for you to fetch changes up to d4a1a317e7478b70e1

<    1   2   3   4   5   6   7   8   9   >