[PATCHv4 2/2] pwm: sunxi: document OF bindings

This is the documentation for the Allwinner Socs PWM bindings. Signed-off-by: Alexandre Belloni Acked-by: Maxime Ripard --- Documentation/devicetree/bindings/pwm/pwm-sunxi.txt | 20 1 file changed, 20 insertions(+) create mode 100644

[PATCHv4 0/2] Add Allwinner SoCs PWM support

Hi, This patch set adds support for the PWM controller found on the Allwinner SoCs. The first patch adds the driver itself. The second patch adds the DT binding documentation Changes in v4: - use the non relaxed versions of readl/writel - dropped the DT patches that got applied Changes in

[PATCHv4 1/2] pwm: Add Allwinner SoC support

This adds a generic PWM framework driver for the PWM controller found on Allwinner SoCs. Signed-off-by: Alexandre Belloni Acked-by: Maxime Ripard --- drivers/pwm/Kconfig | 9 ++ drivers/pwm/Makefile| 1 + drivers/pwm/pwm-sunxi.c | 345

Re: [PATCH 1/7] reset: sunxi: document sunxi's reset controllers bindings

Hi Boris, On Mon, Apr 28, 2014 at 04:58:44PM +0200, Boris BREZILLON wrote: > Add DT bindings documentation for sunxi's reset controllers. > > Signed-off-by: Boris BREZILLON > --- > .../bindings/reset/allwinner,sunxi-clock-reset.txt | 21 > + > 1 file changed, 21

Re: [PATCH v2 3/7] tty/serial: convert 8250 to generic earlycon

On Sat, Apr 26, 2014 at 1:29 AM, Yinghai Lu wrote: > On Fri, Apr 18, 2014 at 3:19 PM, Rob Herring wrote: >> From: Rob Herring >> >> With the generic earlycon infrastructure in place, convert the 8250 >> early console to use it. >> >> Signed-off-by: Rob Herring >> Cc: Greg Kroah-Hartman >> Cc:

Re: [PATCH 4/4] x86/gart: Tidy messages and add bridge device info

On Sat, Apr 26, 2014 at 12:01 AM, Ingo Molnar wrote: > > * Bjorn Helgaas wrote: > >> Print the AGP bridge info the same way as the rest of the kernel, e.g., >> ":00:04.0" instead of "00:04:00". >> >> Also print the AGP aperture address range the same way we print resources, >> and label it

[GIT PULL] ftrace/module: Hardcode ftrace_module_init() call into load_module()

Linus, Takao Indoh reported that he was able to cause a ftrace bug while loading a module and enabling function tracing at the same time. He uncovered a race where the module when loaded will convert the calls to mcount into nops, and expects the module's text to be RW. But when function

Re: [PATCH v2 3/7] tty/serial: convert 8250 to generic earlycon

On Sat, Apr 26, 2014 at 1:19 AM, Yinghai Lu wrote: > On Fri, Apr 18, 2014 at 3:19 PM, Rob Herring wrote: >> From: Rob Herring >> >> With the generic earlycon infrastructure in place, convert the 8250 >> early console to use it. >> >> Signed-off-by: Rob Herring >> Cc: Greg Kroah-Hartman >> Cc:

Re: [PATCH V6 0/4] perf/x86/amd: AMD Family 16h Data Breakpoint Extensions

On 2/25/2014 9:49 AM, Frederic Weisbecker wrote: This message has been archived. View the original item

Re: [PATCH 2/5] power: reset: Add Allwinner A31 reset code

Hi, On Sat, Apr 26, 2014 at 08:32:27AM -0700, Guenter Roeck wrote: > On 04/23/2014 08:04 AM, Maxime Ripard wrote: > >That code used to be in the machine code, but it's more fit here with other > >restart hooks. > > > >That will allow to cleanup the machine directory, while waiting for a proper >

Re: [PATCH v12 30/31] ARM: dts: add System MMU nodes of exynos5250

Vikas, On Sun, Apr 27, 2014 at 10:39 AM, Vikas Sajjan wrote: > Hi shaik, > > +Doug, Abhilash, > > On Sun, Apr 27, 2014 at 1:08 PM, Shaik Ameer Basha > wrote: >> From: Cho KyongHo >> >> Signed-off-by: Cho KyongHo >> --- >> arch/arm/boot/dts/exynos5250.dtsi | 270 >>

Re: [PATCH 2/2] cpuidle / menu: Return error code if there are no suitable states

On Monday, April 28, 2014 01:14:32 PM Daniel Lezcano wrote: > On 04/27/2014 02:55 PM, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > If there is a PM QoS latency limit and all of the sufficiently shallow > > C-states are disabled, the cpuidle menu governor returns 0 which on > >

Re: [BUG] kernel BUG at mm/vmacache.c:85!

On Mon, 28 Apr 2014 15:58:02 -0700 Linus Torvalds wrote: > On Mon, Apr 28, 2014 at 3:39 PM, Davidlohr Bueso wrote: > > > > Is this perhaps a KVM guest? fwiw I see CONFIG_KVM_ASYNC_PF=y which is a > > user of use_mm(). > > So I tried to look through these guys, and that was one of the ones I

Re: [PATCH 1/5] wdt: sunxi: Move restart code to the watchdog driver

Hi, On Sat, Apr 26, 2014 at 08:31:07AM -0700, Guenter Roeck wrote: > On 04/23/2014 08:04 AM, Maxime Ripard wrote: > >Most of the watchdog code is duplicated between the machine restart code and > >the watchdog driver. Add the restart hook to the watchdog driver, to be able > >to > >remove it

Re: [PATCH v2] rwsem: Support optimistic spinning

On Mon, Apr 28, 2014 at 03:09:01PM -0700, Davidlohr Bueso wrote: > We have reached the point where our mutexes are quite fine tuned > for a number of situations. This includes the use of heuristics > and optimistic spinning, based on MCS locking techniques. > > Exclusive ownership of read-write

Re: [PATCH] x86-64: espfix for 64-bit mode *PROTOTYPE*

On 04/28/2014 04:05 PM, H. Peter Anvin wrote: > > So I tried writing this bit up, but it fails in some rather spectacular > ways. Furthermore, I have been unable to debug it under Qemu, because > breakpoints don't work right (common Qemu problem, sadly.) > > The kernel code is at: > >

Re: [PATCH] x86-64: espfix for 64-bit mode *PROTOTYPE*

On 04/23/2014 09:53 PM, Andrew Lutomirski wrote: > > This particular vector hurts: you can safely keep trying until it works. > > This just gave me an evil idea: what if we make the whole espfix area > read-only? This has some weird effects. To switch to the espfix > stack, you have to write

Re: mmotm 2014-04-24-13-07 uploaded

On Mon, 28 Apr 2014 14:39:09 -0700 "Paul E. McKenney" wrote: > On Mon, Apr 28, 2014 at 01:06:40PM -0700, Paul E. McKenney wrote: > > On Mon, Apr 28, 2014 at 07:21:27PM +0200, Richard Weinberger wrote: > > > Am 28.04.2014 19:17, schrieb Randy Dunlap: > > > > > > > > uml defconfig on x86_64: > >

Re: [PATCH 10/10] hwmon: vexpress: Use devm helper for hwmon device registration

On 04/28/2014 10:57 AM, Pawel Moll wrote: Use devm_hwmon_device_register_with_groups instead of the old-style manual attributes and hwmon device registration. Also, unwind the attribute group macros for better code readability. Cc: Jean Delvare Cc: Guenter Roeck Cc: lm-sens...@lm-sensors.org

Re: [BUG] kernel BUG at mm/vmacache.c:85!

On Mon, Apr 28, 2014 at 3:39 PM, Davidlohr Bueso wrote: > > Is this perhaps a KVM guest? fwiw I see CONFIG_KVM_ASYNC_PF=y which is a > user of use_mm(). So I tried to look through these guys, and that was one of the ones I looked at. It's using use_mm(), but it's only called through

Re: [PATCH 2/3] sched: idle: Add sched balance option

On Monday, April 28, 2014 01:07:31 PM Daniel Lezcano wrote: > On 04/28/2014 12:28 PM, Peter Zijlstra wrote: > > On Mon, Apr 28, 2014 at 12:09:20PM +0200, Daniel Lezcano wrote: > >> I agree a numerical value is not flexible. But it sounds weird to put a > >> scheduler option in the sysfs and maybe

[PATCH 0/2] sched: Idle load balance fixes

[Resending to LKML] This patchset includes fixes relating to idle_balance() and rebalance_domains(). These apply on top of the following patches: https://lkml.org/lkml/2014/4/23/767 https://lkml.org/lkml/2014/4/23/764 Patch #1 addresses an issue introduced by commit e5fc6611 which potentially

[PATCH 2/2] sched: Fix next_balance logic in rebalance_domains() and idle_balance()

Currently, in idle_balance(), we update rq->next_balance when we pull_tasks. However, it is also important to update this in the !pulled_tasks case too. When the CPU is "busy" (the CPU isn't idle), rq->next_balance gets computed using sd->busy_factor (so we increase the balance interval when the

[PATCH 1/2] sched: Fix updating rq->max_idle_balance_cost and rq->next_balance in idle_balance()

Commit e5fc6611 can potentially cause rq->max_idle_balance_cost to not be updated, even when load_balance(NEWLY_IDLE) is attempted and the per-sd max cost value is updated. Preeti noticed a similar issue with updating rq->next_balance. In this patch, we fix this by making sure we still

Re: [BUG] kernel BUG at mm/vmacache.c:85!

Adding Oleg. On Mon, 2014-04-28 at 14:55 -0700, Linus Torvalds wrote: > On Mon, Apr 28, 2014 at 2:20 PM, Linus Torvalds > wrote: > > > > That said, the bug does seem to be that some path doesn't invalidate > > the vmacache sufficiently, or something inserts a vmacache entry into > > the current

RE: [PATCH] staging: comedi: remove duplicate pointer assignments in attach functions

On Saturday, April 26, 2014 7:04 AM, Christian Engelmayer wrote: > Some board pointer are assigned twice via comedi_board() in the comedi low > level driver attach functions. Remove the duplicate assignment from the > variable definition where the pointer is not used anyway until assigned later >

Re: [Patch V2 0/9] I2C ACPI operation region handler support

On Monday, April 28, 2014 10:27:39 PM Lan Tianyu wrote: > ACPI 5.0 spec(5.5.2.4.5) defines GenericSerialBus(i2c, spi, uart) operation > region. It allows ACPI aml code able to access such kind of devices to > implement some ACPI standard method. > > On the Asus T100TA, Bios use GenericSerialBus

Re: [Patch V2 1/9] ACPICA: Executer: Fix buffer allocation issue for generic_serial_bus region field accesses.

On Monday, April 28, 2014 11:08:25 AM Adam Williamson wrote: > On Mon, 2014-04-28 at 10:52 -0700, Adam Williamson wrote: > > On Mon, 2014-04-28 at 22:27 +0800, Lan Tianyu wrote: > > > From: Lv Zheng > > > > > > The size of the buffer allocated for generic_serial_bus region access > > > is not

[PATCH] iommu/amd: Take mmap_sem when calling get_user_pages

From: Jay Cornwall get_user_pages requires caller to hold a read lock on mmap_sem. Signed-off-by: Jay Cornwall Signed-off-by: Suravee Suthikulpanit --- drivers/iommu/amd_iommu_v2.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/iommu/amd_iommu_v2.c

Re: [PATCH_v8 0/2] arm64: Add audit support

On 04/28/2014 05:51 AM, AKASHI Takahiro wrote: Hi Don, Sorry for not responding to you soon: been there, done that! .. no problem.. On 04/12/2014 06:37 AM, Don Dutile wrote: On 03/15/2014 01:49 AM, AKASHI Takahiro wrote: (Please apply this patch after my ftrace patch to resolve some

Re: [BUG] kernel BUG at mm/vmacache.c:85!

On Mon, Apr 28, 2014 at 3:14 PM, Davidlohr Bueso wrote: > > I think that returning some stale/bogus vma is causing those segfaults > in udev. It shouldn't occur in a normal scenario. What puzzles me is > that it's not always reproducible. This makes me wonder what else is > going on... I've

Re: linux-next: Tree for Apr 28 (drivers/pnp/quirks.c)

On Monday, April 28, 2014 04:09:28 PM Bjorn Helgaas wrote: > On Mon, Apr 28, 2014 at 11:14:15PM +0200, Rafael J. Wysocki wrote: > > On 4/28/2014 11:11 PM, Bjorn Helgaas wrote: > > >On Mon, Apr 28, 2014 at 10:45:37AM -0700, Randy Dunlap wrote: > > >>On 04/27/14 23:57, Stephen Rothwell wrote: > >

Re: [PATCH 2/5 v2] iio: exynos_adc: rearrange clk and regulator enable/disable calls

Naveen, On Sat, Apr 26, 2014 at 4:37 AM, Naveen Krishna Chatradhi wrote: > From: Naveen Krishna Ch > > This patch maintains the following order in > probe(), remove(), resume() and suspend() calls > > regulator enable, clk prepare enable > ... > clk disable unprepare, regulator disable > >

[PATCH 4/7] x86: Add support for rd/wr fs/gs base

From: Andi Kleen IvyBridge added new instructions to directly write the fs and gs 64bit base registers. Previously this had to be done with a system call to write to MSRs. The main use case is fast user space threading and switching the fs/gs registers quickly there. The instructions are opt-in

[PATCH 6/7] x86: Enumerate kernel FSGS capability in AT_HWCAP2

From: Andi Kleen The kernel needs to explicitely enable RD/WRFSBASE to handle context switch correctly. So the application needs to know if it can safely use these instruction. Just looking at the CPUID bit is not enough because it may be running in a kernel that does not enable the

Re: [BUG] kernel BUG at mm/vmacache.c:85!

On Mon, 2014-04-28 at 15:05 -0700, Hugh Dickins wrote: > On Mon, 28 Apr 2014, Linus Torvalds wrote: > > On Mon, Apr 28, 2014 at 2:20 PM, Linus Torvalds > > wrote: > > > > > > That said, the bug does seem to be that some path doesn't invalidate > > > the vmacache sufficiently, or something inserts

[PATCH 3/7] x86: Add C intrinsics for new rd/wr fs/gs base instructions

From: Andi Kleen Plus for swapgs. Very straight forward. Used in followon patch. Signed-off-by: Andi Kleen --- arch/x86/include/asm/fsgs.h | 43 +++ 1 file changed, 43 insertions(+) create mode 100644 arch/x86/include/asm/fsgs.h diff --git

Add support for RD/WR FS/GSBASE

This adds kernel support for some Intel instructions that allow fast access to the FS and GS 64bit base. They need some changes to entry_64.S because they allow user to fully control the GS base. Advantages: - NMIs (and other "paranoid" interrupts) avoid one RDMSR which makes them faster - User

[PATCH 1/7] percpu: Add a DEFINE_PER_CPU_2PAGE_ALIGNED

From: Andi Kleen Needed in a followon patch which needs to naturally align a 8K stack. I just put it into the page aligned section. This may cause an extra 4K hole if we're unlucky. Cc: t...@kernel.org Signed-off-by: Andi Kleen --- include/linux/percpu-defs.h | 4 1 file changed, 4

[PATCH 2/7] x86: Naturally align the debug IST stack

From: Andi Kleen The followon patch for RD*BASE requires the IST stacks to be naturally aligned because it uses and to access the bottom of the stack. This was true for everyone except for the debug ist stack. Make the debug ist stack naturally aligned too. Signed-off-by: Andi Kleen ---

[PATCH 7/7] x86: Add documentation for rd/wr fs/gs base

From: Andi Kleen Signed-off-by: Andi Kleen --- Documentation/x86/fsgs.txt | 73 ++ 1 file changed, 73 insertions(+) create mode 100644 Documentation/x86/fsgs.txt diff --git a/Documentation/x86/fsgs.txt b/Documentation/x86/fsgs.txt new file mode

[PATCH 5/7] x86: Make old K8 swapgs workaround conditional

From: Andi Kleen Every gs selector/index reload always paid an extra MFENCE between the two SWAPGS. This was to work around an old bug in early K8 steppings. All other CPUs don't need the extra mfence. Patch the extra MFENCE only in for K8. Signed-off-by: Andi Kleen ---

[PATCH v2] rwsem: Support optimistic spinning

We have reached the point where our mutexes are quite fine tuned for a number of situations. This includes the use of heuristics and optimistic spinning, based on MCS locking techniques. Exclusive ownership of read-write semaphores are, conceptually, just about the same as mutexes, making them

Re: linux-next: Tree for Apr 28 (drivers/pnp/quirks.c)

On Mon, Apr 28, 2014 at 11:14:15PM +0200, Rafael J. Wysocki wrote: > On 4/28/2014 11:11 PM, Bjorn Helgaas wrote: > >On Mon, Apr 28, 2014 at 10:45:37AM -0700, Randy Dunlap wrote: > >>On 04/27/14 23:57, Stephen Rothwell wrote: > >>>Hi all, > >>> > >>>This tree still fails (more than usual) the

Re: [BUG] kernel BUG at mm/vmacache.c:85!

On Mon, 28 Apr 2014, Linus Torvalds wrote: > On Mon, Apr 28, 2014 at 2:20 PM, Linus Torvalds > wrote: > > > > That said, the bug does seem to be that some path doesn't invalidate > > the vmacache sufficiently, or something inserts a vmacache entry into > > the current process when looking up a

[PATCH 0/5] RAPL driver updates

A few updates to the RAPL driver. Including David's IOSF-SB driver change and a small tweak to allow RAPL driver to use IOSF driver on platforms with and without IOSF mailbox interface. David E. Box (1): x86, iosf: Add dummy functions for loadable modules Jacob Pan (4): powercap/rapl:

[PATCH 2/5] powercap/rapl: add new cpu ids

Adding support for Broadwell model 0x3d and HSW model (0x3c) Signed-off-by: Jacob Pan --- drivers/powercap/intel_rapl.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c index 1c987d2..b1cda6f 100644 ---

[PATCH 4/5] x86/iosf: kconfig and used by other drivers

Allow Kconfig selection for IOSF driver. Fix warning condition when MBI interface dummy functions are called at runtime. Signed-off-by: Jacob Pan --- arch/x86/Kconfig| 2 +- arch/x86/include/asm/iosf_mbi.h | 9 + 2 files changed, 6 insertions(+), 5 deletions(-) diff

[PATCH 3/5] x86, iosf: Add dummy functions for loadable modules

From: "David E. Box" Some loadable modules only need IOSF access on the platforms where it exists. Provide dummy functions to allow these modules to compile and load on the platforms where it doesn't exist. Signed-off-by: David E. Box Link:

[PATCH 1/5] powercap/rapl: further relax energy counter checks

Energy counters may roll slowly for some RAPL domains, checking all of them can be time consuming and takes unpredictable amount of time. Therefore, we relax the sanity check by only checking availability of the MSRs and non-zero value of the energy status counters. It has been shown sufficient

[PATCH 5/5] powercap/rapl: change floor frequency for vallewview

RAPL power limit reduce power by limiting CPU P-state and other techniques. On Valleyview, RAPL power limit cannot go to LFM (low frequency mode) if we don't set the floor frequency via IOSF mailbox. This patch enables setting of floor frquency such that RAPL power limit is more effective.

Re: mmotm 2014-04-24-13-07 uploaded

On 04/28/14 14:15, Paul E. McKenney wrote: > On Mon, Apr 28, 2014 at 01:32:38PM -0700, Randy Dunlap wrote: >> On 04/28/14 13:06, Paul E. McKenney wrote: >>> On Mon, Apr 28, 2014 at 07:21:27PM +0200, Richard Weinberger wrote: Am 28.04.2014 19:17, schrieb Randy Dunlap: > > uml defconfig

Re: X86: Impossible select Enhanced Real Time Clock Support (legacy PC RTC driver)

On Mon, 28 Apr 2014 11:16:37 -0700 John Stultz wrote: > >> This breaks the API since there is no more misc device /dev/rtc > >> available without a udev rule or a link to /dev/rtc0. > > So yea.. I feel like that /dev/rtcN renaming (and API) break (which > was a huge and annoying pain) was

Re: [PATCH 3/6] staging: comedi: addi_apci_1032: board has 32 digital inputs

On 28/04/14 19:11, Hartley Sweeten wrote: On Saturday, April 26, 2014 6:37 PM, Chase Southwood wrote: This board always has 32 digital inputs. Remove the test when initializing the subdevice. Also, since this board is the only one supported by this driver, remove the boardinfo about the

Re: [BUG] kernel BUG at mm/vmacache.c:85!

On Mon, Apr 28, 2014 at 2:20 PM, Linus Torvalds wrote: > > That said, the bug does seem to be that some path doesn't invalidate > the vmacache sufficiently, or something inserts a vmacache entry into > the current process when looking up a remote process or whatever. > Davidlohr, ideas? Maybe we

Re: [PATCH] staging: crypto: skein: depend upon CRYPTO

On Friday, April 25, 2014 at 06:45:09 PM, Jason Cooper wrote: > Fengguang's randconfig kernel build tester discovered the following > warnings: > > warning: (CRYPTO_THREEFISH) selects CRYPTO_ALGAPI which has unmet direct > dependencies (CRYPTO) warning: (DM_VERITY && CRYPTO_SKEIN) selects >

umount -f Device or resource busy; already tried: mount, lsof, fuser, exportfs, ps axf, dmsetup table, losetup -a

I am posting with hope to improve the reliability and usability of unmounting 'busy' filesystems (for which umount -f doesn't work and no remedy is known). There are no apparent resource holders but the device is still 'busy'. (

Re: [PATCH] random: Add "initialized" variable to proc

On Mon, Apr 28, 2014 at 09:52:11PM +0200, Florian Weimer wrote: > Before this change, you had to check kernel log messages to see if the > non-blocking pool had been properly initialized. With this change, you > can consult the file /proc/sys/kernel/random/intialized instead. > > Signed-off-by:

Re: [PATCH] Kernel 3.15-rc2 : Peak DVB-T USB tuner device ids for rtl28xxu driver

On Sun, Apr 27, 2014 at 03:19:12PM -0700, Linus Torvalds wrote: Hi Linus, apologies, i've changed email clients in order to preserve the formatting this time around. The patch is now included inline as an attachment. I ran the script but noticed you've already cc'd the appropriate people.

Re: [PATCH v2 2/5] x86/PCI: Support additional MMIO range capabilities

On Mon, Apr 28, 2014 at 02:50:29PM -0600, Bjorn Helgaas wrote: > This I/O ECS thing seems likely to cause future problems. My > understanding (based on sec 2.8 of [1]) is that enable_pci_io_ecs() > and pci_enable_pci_io_ecs() are there to enable access to extended > config space (offsets

Re: mmotm 2014-04-24-13-07 uploaded

rs/tty/sysrq.c:558: undefined > reference to `rcu_sysrq_end' > > This is due to Rik's "#include " getting lost somehow. > This #include is needed in drivers/tty/sysrq.c. > > But maybe I need to be using some other branch of linux-next. Am currently > on 5bd4e10b96ce20271688aa

[patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v3

Hello! This is (I hope) the final version. Most changes from v2 are sitting in documentation, where I tried to reflect that the time we're printing out is remaining until the timer expiration. Please take a look. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the

[patch 3/3] timerfd: Implement write method

The read() of timerfd files allows to fetch the number of timer ticks while there is no way to set it back from userspace. To restore the timer state as it was at checkpoint moment we need a way to setup ticks back. So as a counterpart of read() the write() takes ticks number from the userspace

[patch 1/3] timerfd: Implement show_fdinfo method

For checkpoint/restore of timerfd files we need to know how exactly the timer were armed to be able to handle it. Thus implement show_fdinfo method which provides enough information for timer re-creation. One of significant changes I think is addition of timerfd_ctx::settime_flags member.

[patch 2/3] docs: procfs -- Document timerfd output

CC: Shawn Landden CC: Thomas Gleixner CC: Andrew Morton CC: Andrey Vagin CC: Pavel Emelyanov CC: Vladimir Davydov Signed-off-by: Cyrill Gorcunov --- Documentation/filesystems/proc.txt | 19 +++ 1 file changed, 19 insertions(+) Index:

Re: [PATCH -V1 22/22] ext4: Add Ext4 compat richacl feature flag

On Apr 27, 2014, at 10:14 AM, Aneesh Kumar K.V wrote: > This feature flag can be used to enable richacl on > the file system. Once enabled the "acl" mount option > will enable richacl instead of posix acl I was going to complain about this patch, because re-using the "acl" mount option to

Re: [PATCH v2 5/5] PCI: Remove redundant 'quirk_amd_nb_node'

On Sun, Apr 20, 2014 at 4:54 AM, Borislav Petkov wrote: > On Fri, Apr 18, 2014 at 08:53:46PM -0600, Myron Stowe wrote: >> With the amd_bus.c updates to support additional AMD processors (11h, 12h, >> 14h 15h and 16h) 'quirk_amd_nb_node' seems to be redundant. This patch >> removes it. >> >>

Re: [PATCH v2 4/5] ACPI/PCI: Warn if we have to "guess" host bridge node information

On Sun, Apr 20, 2014 at 4:21 AM, Borislav Petkov wrote: > On Fri, Apr 18, 2014 at 08:53:39PM -0600, Myron Stowe wrote: >> The vast majority of platforms are not supplying ACPI _PXM (proximity) >> information corresponding to host bridge (PNP0A03/PNP0A08) devices >> resulting in sysfs "numa_node"

Re: [PATCH v2 3/5] x86/PCI: Miscellaneous code clean up for early_fillup_mp_bus_info

On Sun, Apr 20, 2014 at 2:02 AM, Borislav Petkov wrote: > On Fri, Apr 18, 2014 at 08:53:31PM -0600, Myron Stowe wrote: >> From: Suravee Suthikulpanit >> >> * Refactoring of the early_fill_mp_bus_info function into multiple helper >> functions since it is getting long, and difficult to follow.

Re: [BUG] kernel BUG at mm/vmacache.c:85!

On Mon, Apr 28, 2014 at 12:18 PM, Srivatsa S. Bhat wrote: > > I hit this during boot on v3.15-rc3, just once so far. > Subsequent reboots went fine, and a few quick runs of multi- > threaded ebizzy also didn't recreate the problem. > > The kernel I was running was v3.15-rc3 + some totally >

Re: mmotm 2014-04-24-13-07 uploaded

nux-next... > > > > OK, now I get a different build failure: > > > > /home/paulmck/public_git/linux-next/drivers/tty/sysrq.c:514: undefined > > reference to `rcu_sysrq_start' > > /home/paulmck/public_git/linux-next/drivers/tty/sysrq.c:558: undefined > >

Re: [PATCH 1/1] MM: make vmpressure_win dynamic

On Mon, 28 Apr 2014 14:10:25 -0700 Andrew Morton wrote: > On Mon, 28 Apr 2014 22:25:21 +0200 Fabian Frederick wrote: > > > Initialize vmpressure_win in vmstat using > > calculate_normal_threshold() based on each zone/cpu * SWAP_CLUSTER_SIZE > > > > Value refreshed through cpu notifier > >

Re: [PATCH v2 2/5] x86/PCI: Support additional MMIO range capabilities

On Sat, Apr 19, 2014 at 7:52 AM, Borislav Petkov wrote: > On Fri, Apr 18, 2014 at 08:53:23PM -0600, Myron Stowe wrote: >> From: Suravee Suthikulpanit >> >> This patch adds supports for additional MMIO ranges (16 ranges). Also, >> each MMIO base/limit can now support up to 48-bit MMIO addresses.

[PATCH] Staging: gdm72xx: gdm_wimax: Fixed coding style issues.

Fixed following coding style issues. - No space is necessary after a cast - Alignment should match open parenthesis - Braces {} should be used on all arms of this statement Signed-off-by: Junsu Shin x --- drivers/staging/gdm72xx/gdm_wimax.c | 71 ++- 1 file

Re: linux-next: Tree for Apr 28 (drivers/pnp/quirks.c)

On 4/28/2014 11:11 PM, Bjorn Helgaas wrote: On Mon, Apr 28, 2014 at 10:45:37AM -0700, Randy Dunlap wrote: On 04/27/14 23:57, Stephen Rothwell wrote: Hi all, This tree still fails (more than usual) the powerpc allyesconfig build. Changes since 20140424: on i386: CC

[PATCH V3 2/2] fs/ext4/fsync.c: generic_file_fsync call based on barrier flag

generic_file_fsync has been updated to issue a flush for older filesystems. This patch tests for barrier flag in ext4 mount flags and calls the right function. Suggested-by: Jan Kara Suggested-by: Christoph Hellwig Cc: Jan Kara Cc: Christoph Hellwig Cc: Alexander Viro Cc: "Theodore Ts'o"

[PATCH 1/3][RFC][v1] kconfig: Change COMMAND_LINE_SIZE to a kernel config option, which is now set per architecture.

Having COMMAND_LINE_SIZE a kernel config option is a cleaner way to modify the value if needed. Currently defines need to be changed within the architecture specific header files. The default COMMAND_LINE_SIZE for asm-generic is still set by a define in include/asm-generic/setup.h.

Re: usage of rcu_dereference_raw

On Mon, Apr 21, 2014 at 06:47:34PM -0400, Pranith Kumar wrote: > > On Mon, Apr 21, 2014 at 6:03 PM, Paul E. McKenney > wrote: > >> do most of the uses of rcu_dereference_raw() need to be changed to use > >> other > >> dereference functions or are there cases where its usage is valid? > > >

[PATCH 2/3][RFC][v1] powerpc: Change the powerpc architecture to use Kconfig to set COMMAND_LINE_SIZE.

The powerpc architecture currently uses asm-generic to set the value of COMMAND_LINE_SIZE. This change will allow the value of COMMAND_LINE_SIZE to be set specifically for powerpc without affecting other architectures that may use asm-generic. Signed-off-by: Joseph Salisbury ---

[PATCH v2 3/3] irqchip: orion: reverse irq handling priority

Non-DT irq handlers were working through irq causes from most-significant to least-significant bit, while DT irqchip driver does it the other way round. This revealed some more HW issues on Kirkwood peripheral IP, where spurious sdio irqs can happen although irqs are masked. Also, the generated

[PATCH 0/3][RFC][v1] kconfig: powerpc: Make COMMAND_LINE_SIZE a kernel config option. Increase COMMAND_LINE_SIZE for the powerpc architecture.

I'm sending this out as a RFC to get feedback and see which way folks would like to go. Patch 1 of this patch set makes COMMAND_LINE_SIZE a seperate config option for each architecture. However, an alternative to that would be to create a single default size(Possibly 2048 to satisfy patchs 2

[PATCH 3/3][RFC][v1] powerpc: kconfig: Increase the size of COMMAND_LINE_SIZE to 2048 from 512 for powerpc.

BugLink: http://bugs.launchpad.net/bugs/1306677 While booting the PPC64EL kernel, the command line gets truncated to 512 characters. This is due to a limit of 512 defined for COMMAND_LINE_SIZE. It would be beneficial to have a command line longer than 512 characters, as iscsi targets and

[PATCH 2/5] staging: rtl8188eu: fix potential leak in rtw_wx_set_enc_ext()

Function rtw_wx_set_enc_ext() dynamically allocates a temporary buffer that is not freed in all error paths. Use a centralized exit path and make sure that all memory is freed correctly. Detected by Coverity - CID 1077712. Signed-off-by: Christian Engelmayer ---

Re: linux-next: Tree for Apr 28 (drivers/pnp/quirks.c)

On Mon, Apr 28, 2014 at 10:45:37AM -0700, Randy Dunlap wrote: > On 04/27/14 23:57, Stephen Rothwell wrote: > > Hi all, > > > > This tree still fails (more than usual) the powerpc allyesconfig build. > > > > Changes since 20140424: > > > > on i386: > > CC drivers/pnp/quirks.o >

Re: [PATCH v2 1/5] x86/PCI: Add support for generic AMD hostbridges

On Sat, Apr 19, 2014 at 5:31 AM, Borislav Petkov wrote: > On Fri, Apr 18, 2014 at 08:53:16PM -0600, Myron Stowe wrote: >> From: Suravee Suthikulpanit >> >> AMD hostbridges gnenerally show up as PCI device 0:18.0. This patch adds >> logic to automatically probe the device at this location and

[PATCH V3 1/2] FS: Add generic data flush to fsync

This patch issues a flush in generic_file_fsync. (Modern filesystems already do it) -Behaviour can be reversed using /sys/devices/.../cache_type -Filesystems can also call __generic_file_fsync with bool flush false Suggested-by: Jan Kara Suggested-by: Christoph Hellwig Cc: Jan Kara Cc:

Re: [PATCH 1/1] MM: make vmpressure_win dynamic

On Mon, 28 Apr 2014 22:25:21 +0200 Fabian Frederick wrote: > Initialize vmpressure_win in vmstat using > calculate_normal_threshold() based on each zone/cpu * SWAP_CLUSTER_SIZE > > Value refreshed through cpu notifier Anton wrote vmpressure so please let's cc him. `git blame' is useful for

Re: [GIT PULL] SCSI fixes for 3.15-rc3

Il 25/04/2014 16:59, James Bottomley ha scritto: This is a set of seven fixes, three (hpsa) and free'd command references correcting bugs in the last round of updates and the remaining four correcting problems within the SCSI error handler that was causing a deadlock within USB. The patch is

[PATCH 4/5] staging: rtl8188eu: fix potential leak in rtw_mp_SetRFPath()

Function rtw_mp_SetRFPath() dynamically allocates a temporary buffer that is not freed in all error paths. Use a centralized exit path and make sure that all memory is freed correctly. Detected by Coverity - CID 1077714. Signed-off-by: Christian Engelmayer ---

[PATCH 0/5] staging: rtl8188eu: fix Coverity defects in os_dep/ioctl_linux.c

This is a cleanup of staging/rtl8188eu/os_dep/ioctl_linux.c regarding Coverity resource leak findings. The changes leave the current implementation intact and just attack the problems in the error paths, however, it seems that we could get easily rid of some of the mallocs altogether. char

[PATCH 1/5] staging: rtl8188eu: fix potential leak in rtw_wx_read32()

Function rtw_wx_read32() dynamically allocates a temporary buffer that is not freed in all error paths. Use a centralized exit path and make sure that all memory is freed correctly. Detected by Coverity - CID 1077711. Signed-off-by: Christian Engelmayer ---

[PATCH 5/5] staging: rtl8188eu: fix potential leak in rtw_mp_pwrtrk()

Function rtw_mp_pwrtrk() dynamically allocates a temporary buffer that is not freed in all error paths. Use a centralized exit path and make sure that all memory is freed correctly. Detected by Coverity - 1077715. Signed-off-by: Christian Engelmayer ---

Re: [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v2

On Mon, Apr 28, 2014 at 10:59:34PM +0200, Thomas Gleixner wrote: > On Tue, 29 Apr 2014, Cyrill Gorcunov wrote: > > > On Mon, Apr 07, 2014 at 09:47:01PM +0400, Cyrill Gorcunov wrote: > > > Hi, here is an updated series, changes mostly in show_fdinfo code which > > > now > > > produces a way more

[PATCH 3/5] staging: rtl8188eu: fix potential leak in rtw_mp_QueryDrv()

Function rtw_mp_QueryDrv() dynamically allocates a temporary buffer that is not freed in all error paths. Use a centralized exit path and make sure that all memory is freed correctly. Detected by Coverity - CID 1077713. Signed-off-by: Christian Engelmayer ---

Re: [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v2

On Tue, 29 Apr 2014, Cyrill Gorcunov wrote: > On Mon, Apr 07, 2014 at 09:47:01PM +0400, Cyrill Gorcunov wrote: > > Hi, here is an updated series, changes mostly in show_fdinfo code which now > > produces a way more information (and documentation update). Please take a > > look > > once time

Re: [PATCH RESEND 3/3] irqchip: orion: reverse irq handling priority

On Mon, Apr 28, 2014 at 10:06:25PM +0200, Sebastian Hesselbarth wrote: > On 04/28/2014 09:39 PM, Thomas Gleixner wrote: > > On Sat, 26 Apr 2014, Sebastian Hesselbarth wrote: > > > >> Non-DT irq handlers were working through irq causes from most-significant > >> to least-significant bit, while DT

Re: [PATCH v2 0/5] Cpufreq frequency serialization fixes

> Meelis Roos reported hangs during boot in the longhaul cpufreq driver, after > commit 12478cf0c55 (cpufreq: Make sure frequency transitions are serialized). > The root-cause of this issue is the extra invocation of the > cpufreq_freq_transition_begin() and cpufreq_freq_transition_end() APIs in

Re: [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v2

On Mon, Apr 07, 2014 at 09:47:01PM +0400, Cyrill Gorcunov wrote: > Hi, here is an updated series, changes mostly in show_fdinfo code which now > produces a way more information (and documentation update). Please take a look > once time permit. Thanks! Hi, any new comments on this series? -- To

Re: [PATCH V5 02/12] PNPACPI: use whilte list for pnpacpi device enumeration

s/whilte/white/ in subject line -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH v2 2/5] x86/PCI: Support additional MMIO range capabilities

[+cc Jan (24d9b70b8 author), Yinghai] On Sat, Apr 26, 2014 at 3:10 AM, Borislav Petkov wrote: > + Robert. > > On Fri, Apr 25, 2014 at 04:24:31PM -0600, Myron Stowe wrote: >> On Sun, Apr 20, 2014 at 1:59 AM, Borislav Petkov wrote: >> > Drop Andreas' old email address from CC as it keeps

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