Re: 3.15.0-rc2 radeon HD 7480D [Aruba] blank display

On Mon, Apr 21, 2014 at 10:34 PM, Ken Moffat wrote: > On Tue, Apr 22, 2014 at 03:31:06AM +0100, Ken Moffat wrote: > > [ resending, somehow lkml dropped out of the Cc. ] > >> On Tue, Apr 22, 2014 at 12:19:40AM +0100, Ken Moffat wrote: >> > On Mon, Apr 21, 2014 at 05:29:27PM -0400, Ed Tomlinson

Re: Ext4: deadlock occurs when running fsstress and ENOSPC errors are seen.

Hi Darrick, Thanks for the reply, sorry for responding late. On Wed, Apr 16, 2014 at 11:16 PM, Darrick J. Wong wrote: > On Wed, Apr 16, 2014 at 01:21:34PM +0530, Amit Sahrawat wrote: >> Sorry Ted, if it caused the confusion. >> >> There were actually 2 parts to the problem, the logs in the

min() and max() have warning: comparison of distinct pointer types lacks a cast

Hi all Have these warning messages when compiling kernel. Anyone know what's wrong? Regards. In file included from mm/readahead.c:10:0: mm/readahead.c: In function 'max_sane_readahead': include/linux/kernel.h:713:17: warning: comparison of distinct pointer types

[PATCH] cgroup: use uninitialized_var() for may-be uninitialized variable

To suppress this warning: warning: ‘err’ may be used uninitialized in this function [-Wmaybe-uninitialized] int err; ^ Use the uninitialized_var() to decalre err. It also serves to be good documetation. Signed-off-by: Jianyu Zhan --- kernel/cgroup.c | 2 +- 1 file changed, 1

[PATCH] x86: LLVMLinux: Wrap -mno-80387 with cc-option

From: Behan Webster Wrap -mno-80387 gcc options with cc-option so they don't break clang. Signed-off-by: Behan Webster --- arch/x86/Makefile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/arch/x86/Makefile b/arch/x86/Makefile index d1b7c37..ce6ad7e 100644 ---

[f2fs-dev][PATCH 2/2] f2fs: introduce f2fs_seek_block to support SEEK_{DATA,HOLE} in llseek

In This patch we introduce f2fs_seek_block to support SEEK_{DATA,HOLE} of lseek(2). Signed-off-by: Chao Yu --- fs/f2fs/f2fs.h |6 fs/f2fs/file.c | 96 +++- 2 files changed, 101 insertions(+), 1 deletion(-) diff --git

[f2fs-dev][PATCH 1/2] f2fs: handle inline data independently in f2fs_bmap

We'd better handle inline data case independently in f2fs_bmap(). It can reduce our handling time in f2fs_bmap(). Signed-off-by: Chao Yu --- fs/f2fs/data.c |5 + 1 file changed, 5 insertions(+) diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index 6b89b25..150c12a 100644 ---

[PATCH] device_cgroup: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

[PATCH] netprio_cgroup: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

[PATCH] netclassid_cgroup: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

Re: ftrace/kprobes: Warning when insmod two modules

(2014/04/22 12:51), Rusty Russell wrote: > Steven Rostedt writes: >> On Mon, 24 Mar 2014 20:26:05 +0900 >> Masami Hiramatsu wrote: >> >> >>> Thank you for reporting with this pretty backtrace :) >>> Steven, I think this is not the kprobe bug but ftrace (and perhaps, module). >> >> Looks to be

[PATCH] hugetlb_cgroup: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

Re: kaslr relocation incompitable with kernel loaded high

On 04/21/14 at 09:58pm, Yinghai Lu wrote: > On Mon, Apr 21, 2014 at 8:16 PM, WANG Chao wrote: > > On 04/21/14 at 11:01am, Kees Cook wrote: > >> On Mon, Apr 21, 2014 at 10:56 AM, Yinghai Lu wrote: > >> > On Mon, Apr 21, 2014 at 3:52 AM, WANG Chao wrote: > >> >> Hi, Kees > >> >> > >> >> When I'm

[PATCH] perf-event/cgroup: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

[PATCH] cgroup_freezer: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

[PATCH] cgroup: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

[PATCH] blk-cgroup: explicitly init the early_init field

For a cgroup subsystem who should init early, then it should carefully take care of the implementation of css_alloc, because it will be called before mm_init() setup the world. Luckily we don't, and we better explicitly assign the early_init field to 0, for document reason. Signed-off-by: Jianyu

[PATCH RESEND] fs/aio.c: Remove ctx parameter in kiocb_cancel

ctx is no longer used in kiocb_cancel since 57282d8fd74407 ("aio: Kill ki_users") Cc: Alexander Viro Cc: Andrew Morton Signed-off-by: Fabian Frederick --- fs/aio.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/aio.c b/fs/aio.c index 12a3de0e..b92fdee 100644 ---

[Bugfix] sched: fix possible invalid memory access caused by CPU hot-addition

When calling kzalloc_node(size, flags, node), we should first check whether node is onlined, otherwise it may cause invalid memory access as below. [ 3663.324476] BUG: unable to handle kernel paging request at 1f08 [ 3663.332348] IP: [] __alloc_pages_nodemask+0xb9/0x2d0 [ 3663.339719]

[PATCH RESEND] FS: Remove bs paramater in biovec_create_pool

bs is no longer used in biovec_create_pool since 9f060e2231ca96 ("block: Convert integrity to bvec_alloc_bs()") Cc: Alexander Viro Cc: Andrew Morton Signed-off-by: Fabian Frederick --- fs/bio-integrity.c | 2 +- fs/bio.c| 4 ++-- include/linux/bio.h | 2 +- 3 files changed, 4

[PATCH] mbcache: LLVMLinux: Remove double calculation from mbcache

From: Mark Charlebois The call to __builtin_log2 presumes there is a double log2(double x) function defined in the kernel. The call to hash_log is a call to hash_64 which is defined in include/linux/hash.h static __always_inline u64 hash_64(u64 val, unsigned int bits) That means that

[PATCH RESEND] fs/bio.c: remove nr_segs (unused function parameter)

nr_segs is no longer used in bio_alloc_map_data since c8db444820a1e3 ("block: Don't save/copy bvec array anymore") Cc: Alexander Viro Cc: Andrew Morton Signed-off-by: Fabian Frederick --- fs/bio.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/fs/bio.c b/fs/bio.c

[PATCH] cpufreq: Make linux...@vger.kernel.org official mailing list

There have been confusion all the time about which mailing list to follow for cpufreq activities, linux...@vger.kernel.org or cpuf...@vger.kernel.org. As Maintainers always wanted people to send patches to linux...@vger.kernel.org and kernel source asked them to use cpuf...@vger.kernel.org. Lets

Re: [tip:locking/core] arch,avr32: Convert smp_mb__*()

* Hans-Christian Egtvedt wrote: > Around Fri 18 Apr 2014 06:05:23 -0700 or thereabout, tip-bot for Peter > Zijlstra wrote: > > Commit-ID: 710adaa913169d7183cdf0de41c2a349101ff615 > > Gitweb: > > http://git.kernel.org/tip/710adaa913169d7183cdf0de41c2a349101ff615 > > Author: Peter

Re: kaslr relocation incompitable with kernel loaded high

On Mon, Apr 21, 2014 at 8:16 PM, WANG Chao wrote: > On 04/21/14 at 11:01am, Kees Cook wrote: >> On Mon, Apr 21, 2014 at 10:56 AM, Yinghai Lu wrote: >> > On Mon, Apr 21, 2014 at 3:52 AM, WANG Chao wrote: >> >> Hi, Kees >> >> >> >> When I'm testing kaslr with kdump, I find that when 2nd kernel is

Re: [PATCH v3 2/2] dt: platform driver: Fill the resources before probe and defer if needed

* Tony Lindgren [140421 20:06]: > * Tony Lindgren [140421 13:26]: > > * Rob Herring [140421 12:01]: > > > Something like this is what you had in mind? ... > > > --- a/drivers/of/irq.c > > > +++ b/drivers/of/irq.c > > > @@ -400,6 +400,26 @@ int of_irq_to_resource(struct device_node *dev, int >

RE: linux-next: build failure after merge of the mmc tree

On Tue, April 22, 2014, Stephen Rothwell wrote: > Hi Chris, > > After merging the mmc tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card': > drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20: error:

Re: [PATCH] locks: rename file-private locks to file-description locks

On 04/21/2014 11:15 PM, Stefan (metze) Metzmacher wrote: > Am 21.04.2014 21:55, schrieb Jeff Layton: >> On Mon, 21 Apr 2014 21:39:12 +0200 >> "Michael Kerrisk (man-pages)" wrote: >> >>> On 04/21/2014 08:46 PM, Rich Felker wrote: On Mon, Apr 21, 2014 at 08:32:44PM +0200, Michael Kerrisk

Re: [PATCH v2 3/4] sysctl: allow for strict write position handling

On Mon, Apr 21, 2014 at 3:45 PM, Andrew Morton wrote: > On Thu, 17 Apr 2014 17:16:22 -0700 Kees Cook wrote: > >> When writing to a sysctl string, each write, regardless of VFS position, >> begins writing the string from the start. This means the contents of >> the last write to the sysctl

Re: [PATCH 0/4] ipc/shm.c: increase the limits for SHMMAX, SHMALL

On 04/21/2014 07:25 PM, Davidlohr Bueso wrote: On Mon, 2014-04-21 at 16:26 +0200, Manfred Spraul wrote: Hi all, the increase of SHMMAX/SHMALL is now a 4 patch series. I don't have ideas how to improve it further. Manfred, is there any difference between this set and the one you sent a couple

Re: [PATCH] Kbuild, lto: Avoid reported warning with strtoul

On 21 April 2014 22:20, Andi Kleen wrote: > Hmm that's odd. I guess could assign it to a dummy variable That produces this: scripts/mod/modpost.c: In function ‘remove_dot’: scripts/mod/modpost.c:1708:16: warning: variable ‘ignore’ set but not used [-Wunused-but-set-variable] > or use viro's

Re: [PATCH v2 2/7] of: introduce of_dma_get_range() helper

On 04/19/2014 09:32 AM, Santosh Shilimkar wrote: > From: Grygorii Strashko [..] > + * Look in bottom up direction for the first "dma-range" property > + * and parse it. > + * dma-ranges format: > + * DMA addr (dma_addr) : naddr cells > + * CPU addr (phys_addr_t) : pna cells > + * size

Re: [PATCH V2 14/19] tick-sched: add comment about 'idle_active' in tick_nohz_idle_exit()

On Tuesday 22 April 2014 04:50 AM, Frederic Weisbecker wrote: > It's still over-detailed. Much of the above is easily deduced after common > review. OTOH > I proposed to summarize there: https://lkml.org/lkml/2014/4/11/334 > The below disambiguates it a bit further. Hmm.. Something broke for

[PATCH 9/9] sysfs: disallow world-writable files.

This check was introduced in 2006 by Alexey Dobriyan (9774a1f54f173) for module parameters; we removed it when we unified the check into VERIFY_OCTAL_PERMISSIONS() as sysfs didn't have the same requirement. Now all those users are fixed, reintroduce it. Cc: Alexey Dobriyan Cc: Dave Jones Cc:

[PATCH 0/9] Avoid world-writable sysfs files.

This adds checking for world-writable sysfs files, after cleaning up all the users. This check has been in module sysfs params since 2006. If you have a reason for being world-writable, please tell me now! Rusty Russell (9): drivers/mtd/devices/docg3.c: avoid world-writable sysfs files.

[PATCH 3/9] drivers/hid/hid-lg4ff.c: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Simon Wood Signed-off-by: Rusty Russell --- drivers/hid/hid-lg4ff.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hid/hid-lg4ff.c

Re: ftrace/kprobes: Warning when insmod two modules

Steven Rostedt writes: > On Mon, 24 Mar 2014 20:26:05 +0900 > Masami Hiramatsu wrote: > > >> Thank you for reporting with this pretty backtrace :) >> Steven, I think this is not the kprobe bug but ftrace (and perhaps, module). > > Looks to be more of a module issue than a ftrace issue. > >> >>

[PATCH 2/9] drivers/video/fbdev/sm501fb.c: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Vincent Sanders Cc: Ben Dooks Signed-off-by: Rusty Russell --- drivers/video/fbdev/sm501fb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 8/9] samples/kobject/: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Greg Kroah-Hartman Signed-off-by: Rusty Russell --- samples/kobject/kobject-example.c | 7 --- samples/kobject/kset-example.c| 7 --- 2 files changed, 8

[PATCH 6/9] drivers/staging/speakup/: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Christopher Brannon Cc: Samuel Thibault Cc: Greg Kroah-Hartman Signed-off-by: Rusty Russell --- drivers/staging/speakup/kobjects.c | 60

[PATCH 1/9] drivers/mtd/devices/docg3.c: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Robert Jarzmik Signed-off-by: Rusty Russell --- drivers/mtd/devices/docg3.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 4/9] drivers/scsi/pm8001/pm8001_ctl.c: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Lindar Liu Cc: James Bottomley Signed-off-by: Rusty Russell --- drivers/scsi/pm8001/pm8001_ctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 5/9] drivers/regulator/virtual: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Mark Brown Signed-off-by: Rusty Russell --- drivers/regulator/virtual.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH 7/9] drivers/hid/hid-picolcd_fb: avoid world-writable sysfs files.

In line with practice for module parameters, we're adding a build-time check that sysfs files aren't world-writable. Cc: Bruno Prémont Signed-off-by: Rusty Russell --- drivers/hid/hid-picolcd_fb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hid/hid-picolcd_fb.c

linux-next: manual merge of the audit tree with Linus' tree

Hi Eric, Today's linux-next merge of the audit tree got a conflict in arch/mips/kernel/ptrace.c between commits 6e34574603f6 ("MIPS: asm: syscall: Define syscall_get_arch") and 1225eb825208("MIPS: ptrace: Move away from secure_computing_strict") from Linus' tree and commit 8ea408a0c1e7 ("ARCH:

Re: [PATCH 1/2] gpio: pl061: get gpio base from alias id

Hi Haojian Zhuang, On Tue, Apr 22, 2014 at 09:35:42AM +0800, Haojian Zhuang wrote: > If gpio base number isn't specified, the gpio base will be find from > the end of gpio number. In order to keep with schematics, use alias > to get the ID of gpio chip. > > Signed-off-by: Haojian Zhuang > --- >

Re: 3.14 Regression, kernel panic when suspend, looks ath9k / wireless related

On Sat, Apr 19, 2014 at 12:32 PM, Michael Leun wrote: > 2a901468c221e778af52603e006a53 Odd -- its unclear how you ended up with this bisect given that REGULATORY_COUNTRY_IE_IGNORE is not set for any driver currently. To see this you can try: mcgrof@ergon ~/linux-stable (git::linux-3.14.y)$ git

[PATCH Resend] defconfig: sama5_defconfig: updated

due to enabling -- CONFIG_REGULATOR -- CONFIG_REGULATOR_ACT8865 Signed-off-by: Wenyou Yang --- Hi Nicolas, It is a typo. This patch is based on the branch: at91-3.16-dt, not at91-3.10-dt of git://github.com/at91linux/linux-at91.git Best Regards, Wenyou Yang

Re: [PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver

Hi Jingoo, On Tue, Apr 22, 2014 at 7:48 AM, Jingoo Han wrote: > On Wednesday, April 16, 2014 11:49 PM, Vivek Gautam wrote: >> On Wed, Apr 16, 2014 at 7:14 PM, Tomasz Figa wrote: >> > On 15.04.2014 08:09, Vivek Gautam wrote: >> >> On Thu, Apr 10, 2014 at 5:09 PM, Vivek Gautam wrote: >> >>> On

[PATCH v2.0] ARM: dts: at91-sama5d3_xplained: add the regulator device node

Signed-off-by: Wenyou Yang --- Hi Nicolas, This patch is based on the branch: at91-3.16-dt git://github.com/at91linux/linux-at91.git Best Regards, Wenyou Yang Changelog: v2.0 1./ Remove vddana_reg's property: regulator-always-on. arch/arm/boot/dts/at91-sama5d3_xplained.dts | 41

Re: [RFC PATCH v5 2/2] Use kernfs_break_active_protection() for device online store callbacks

On Mon, 2014-04-21 at 18:46 -0400, Tejun Heo wrote: > Hello, > > On Mon, Apr 21, 2014 at 05:23:50PM +0800, Li Zhong wrote: > > Proper /** function comment would be nice. Ok, will try to write some in next version. > > > +struct kernfs_node *lock_device_hotplug_sysfs(struct device *dev, > > +

Re: [PATCH v2] KVM: x86: Check for host supported fields in shadow vmcs

Il 21/04/2014 15:20, Bandan Das ha scritto: + for (i = j = 0; i < max_shadow_read_write_fields; i++) { + Extra empty line. Not a big deal, but... + switch (shadow_read_write_fields[i]) { + case GUEST_BNDCFGS: + if

Re: [RFC PATCH 1/5] KVM: vmx: speed up emulation of invalid guest state

Il 20/04/2014 22:13, Marcelo Tosatti ha scritto: The same code which resets it to false inside the handle_invalid_guest_state loop (so you would stop emulating at the same point as you do with this patch). So (barring any bugs where we fail to set vmx->emulation_required to true) the

[PATCH] perf tools: Remove extra '/' character in events file path

The array debugfs_known_mountpoints[] will cause extra '/' character output. Remove it. pre: $ perf probe -l /sys/kernel/debug//tracing/uprobe_events file does not exist - please rebuild kernel with CONFIG_UPROBE_EVENTS. post: $ perf probe -l /sys/kernel/debug/tracing/uprobe_events file does not

Re: kaslr relocation incompitable with kernel loaded high

On 04/21/14 at 11:01am, Kees Cook wrote: > On Mon, Apr 21, 2014 at 10:56 AM, Yinghai Lu wrote: > > On Mon, Apr 21, 2014 at 3:52 AM, WANG Chao wrote: > >> Hi, Kees > >> > >> When I'm testing kaslr with kdump, I find that when 2nd kernel is loaded > >> high, it doesn't boot. > >> > >> I reserved

[PATCH] zram: correct offset usage in zram_bio_discard

we want to skip the logical block which is partially covered by the discard bio, so check the remaining size and subtract it if there is a need to goto the next logical block. This patch corrects the offset usage in zram_bio_discard. Signed-off-by: Weijie Yang --- drivers/block/zram/zram_drv.c

linux-next: build failure after merge of the mmc tree

Hi Chris, After merging the mmc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card': drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20: error: 'MMC_STATE_HIGHSPEED' undeclared (first use in this function)

Re: [PATCH 1/6] blackfin/ptrace: call find_vma with the mmap_sem held

Hi Davidlohr, On Sun, Apr 20, 2014 at 10:26 AM, Davidlohr Bueso wrote: > Performing vma lookups without taking the mm->mmap_sem is asking > for trouble. While doing the search, the vma in question can be > modified or even removed before returning to the caller. Take the > lock (shared) in order

Re: [PATCH v3 2/2] dt: platform driver: Fill the resources before probe and defer if needed

* Tony Lindgren [140421 13:26]: > * Rob Herring [140421 12:01]: > > On Mon, Apr 21, 2014 at 10:54 AM, Tony Lindgren wrote: > > > * Rob Herring [140421 06:47]: > > >> On Fri, Apr 18, 2014 at 6:24 PM, Tony Lindgren wrote: > > >> > * Russell King - ARM Linux [140418 16:04]: > > >> >> On Fri,

Re: [PATCH] Save PG_head_mask in VMCOREINFO

On 04/11/14 at 05:50pm, Petr Tesarik wrote: > To allow filtering of huge pages, makedumpfile must be able to > identify them in the dump. This can be done by checking the > appropriate page flag, so communicate its value to makedumpfile > through the VMCOREINFO interface. > > There's only one

Re: [PATCH] cpuidle: governor: menu: move repeated correction factor check to init

ping On 10 April 2014 19:57, Tuukka Tikkanen wrote: > On 10 April 2014 16:43, Chander Kashyap wrote: >> In menu_select function we check for correction factor every time. >> If it is zero we are initializing to unity. Hence move it to init function >> and initialise by unity, hence avoid

Re: [sched,rcu] 9234566d3a3: +1.6% will-it-scale.scalability, +1302.6% time.involuntary_context_switches

On 04/22/2014 09:59 AM, Paul E. McKenney wrote: On Mon, Apr 21, 2014 at 02:28:21PM +0800, Jet Chen wrote: Hi Paul, we noticed the below changes on git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git torture.2014.04.18a commit 9234566d3a36c0aead8852e3c2ca94cd8ebfe219

Re: 3.15.0-rc2 radeon HD 7480D [Aruba] blank display

On Tue, Apr 22, 2014 at 03:31:06AM +0100, Ken Moffat wrote: [ resending, somehow lkml dropped out of the Cc. ] > On Tue, Apr 22, 2014 at 12:19:40AM +0100, Ken Moffat wrote: > > On Mon, Apr 21, 2014 at 05:29:27PM -0400, Ed Tomlinson wrote: > > > > Ken, > > > > > > You might want to try

Re: [Nouveau] [PATCH v2 09/10] drm/nouveau: support GK20A in nouveau_accel_init()

On 04/22/2014 03:07 AM, Ilia Mirkin wrote: On Mon, Apr 21, 2014 at 2:02 AM, Alexandre Courbot wrote: Skip the creation of a software channel for GK20A as software methods are not yet supported. How is GK20A different from a nvc0+ card that lacks PDISPLAY (like all the 3D Controller ones, and

Re: [RFC PATCH v5 1/2] Use lock_device_hotplug() in cpu_probe_store() and cpu_release_store()

On Mon, 2014-04-21 at 18:38 -0400, Tejun Heo wrote: > Hello, > > On Mon, Apr 21, 2014 at 05:20:59PM +0800, Li Zhong wrote: > > While auditing the usage of lock_device_hotplug_sysfs() for implementing > > it in another way in following patch, it seems to me that the code here > > is to add/remove

RE: [PATCH v3] ARM: perf: save/restore pmu registers in pm notifier

> -Original Message- > From: Neil Zhang [mailto:zhan...@marvell.com] > Sent: 2014年4月21日 19:09 > To: will.dea...@arm.com; li...@arm.linux.org.uk > Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; Neil > Zhang; Sudeep KarkadaNagesha > Subject: [PATCH v3] ARM: perf:

[PATCH v4] ARM: perf: save/restore pmu registers in pm notifier

This adds core support for saving and restoring CPU PMU registers for suspend/resume support i.e. deeper C-states in cpuidle terms. This patch adds support only to ARMv7 PMU registers save/restore. It needs to be extended to xscale and ARMv6 if needed. I made this patch because DS-5 is not

[PATCH] tools lib traceevent: Fix backward compatibility macros for pevent filter enums

The return value for pevent_filter_match() is suppose to return FILTER_NONE if the event doesn't have a filter, and FILTER_NOEXIST if there is no filter at all. But the change 41e12e580a7 "tools lib traceevent: Refactor pevent_filter_match() to get rid of die()" replaced the return value with

Re: [PATCH V4 1/5] phy: Add new Exynos5 USB 3.0 PHY driver

On Wednesday, April 16, 2014 11:49 PM, Vivek Gautam wrote: > On Wed, Apr 16, 2014 at 7:14 PM, Tomasz Figa wrote: > > On 15.04.2014 08:09, Vivek Gautam wrote: > >> On Thu, Apr 10, 2014 at 5:09 PM, Vivek Gautam wrote: > >>> On Wed, Apr 9, 2014 at 7:03 PM, Tomasz Figa wrote: > On 09.04.2014

Re: [PATCH v2 07/10] drm/nouveau/graph: pad firmware code at load time

On 04/22/2014 08:48 AM, Ben Skeggs wrote: On Tue, Apr 22, 2014 at 4:03 AM, Ilia Mirkin wrote: On Mon, Apr 21, 2014 at 2:02 AM, Alexandre Courbot wrote: Pad the microcode to a multiple of 0x40 bytes, otherwise firmware will bytes or u32's? From the code, I'm guessing the latter. (Similar

RE: [PATCH 1/4] ACPICA: Add to remove mis-ordered inclusion of from .

Hi, > > +#define ACPI_NATIVE_INTERFACE_HEADER > > This is not good. > > We don't do things like this in the kernel, because they are confusing and > hard > to debug if necessary, so please find a different way to make this work. I use this extra header file to collect: 1. static

Re: [sched,rcu] 9234566d3a3: +1.6% will-it-scale.scalability, +1302.6% time.involuntary_context_switches

On Mon, Apr 21, 2014 at 02:28:21PM +0800, Jet Chen wrote: > Hi Paul, > > we noticed the below changes on > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git > torture.2014.04.18a > commit 9234566d3a36c0aead8852e3c2ca94cd8ebfe219 ("sched,rcu: Make > cond_resched() report RCU

Re: [Nouveau] [PATCH v2 09/10] drm/nouveau: support GK20A in nouveau_accel_init()

On Tue, Apr 22, 2014 at 4:07 AM, Ilia Mirkin wrote: > On Mon, Apr 21, 2014 at 2:02 AM, Alexandre Courbot > wrote: >> Skip the creation of a software channel for GK20A as software methods >> are not yet supported. > > How is GK20A different from a nvc0+ card that lacks PDISPLAY (like all > the

Re: [rcu] 10a94227ba2: -2.0% will-it-scale.per_process_ops

On Sat, Apr 19, 2014 at 04:26:22PM +0800, Fengguang Wu wrote: > Paul, > > FYI, we noticed the below changes on > > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git > next.2014.04.16b > commit 10a94227ba229f1b05672754dc318a8fe7982c95 ("rcu: Update > cpu_needs_another_gp() for

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

On Mon, Apr 21, 2014 at 6:47 PM, H. Peter Anvin wrote: > Race condition (although with x86 being globally ordered, it probably can't > actually happen.) The bitmask is probably the way to go. Does the race matter? In the worst case you take the lock unnecessarily. But yes, the bitmask is

Re: [sched,rcu] b84c4e08143: +3.1% will-it-scale.per_thread_ops

On Sat, Apr 19, 2014 at 04:11:46PM +0800, Fengguang Wu wrote: > On Thu, Apr 17, 2014 at 06:55:03AM -0700, Paul E. McKenney wrote: > > On Thu, Apr 17, 2014 at 12:03:53PM +0800, Fengguang Wu wrote: > > > Hi Paul, > > > > > > FYI, this improves will-it-scale/open1 throughput. > > > > Cool! Not a

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

Race condition (although with x86 being globally ordered, it probably can't actually happen.) The bitmask is probably the way to go. On April 21, 2014 6:28:12 PM PDT, Andrew Lutomirski wrote: >On Mon, Apr 21, 2014 at 6:14 PM, H. Peter Anvin wrote: >> I wanted to avoid the "another cpu made

Re: [PATCH 1/2 V3] workqueue: substitute POOL_FREEZING with __WQ_FREEZING

On 04/22/2014 06:20 AM, Tejun Heo wrote: > On Mon, Apr 21, 2014 at 07:59:20PM +0800, Lai Jiangshan wrote: >> Only workqueues have freezable or freezing attribution/state, not worker >> pools. >> But POOL_FREEZING adds a suspicious state and makes reviewers confused. >> >> And it causes

RE: [PATCH] ARM: dts: at91-sama5d3_xplained: add the regulator device node

Hi, > -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: Monday, April 21, 2014 8:22 PM > To: Yang, Wenyou > Cc: devicet...@vger.kernel.org; Ferre, Nicolas; linux- > ker...@vger.kernel.org; robh...@kernel.org; broo...@kernel.org; linux- >

Re: linux-next: manual merge of the userns tree with Linus' tree

On Thu, 17 Apr 2014 01:44:21 -0700 ebied...@xmission.com (Eric W. Biederman) wrote: > > Al Viro writes: > > > On Thu, Apr 17, 2014 at 03:06:57PM +1000, Stephen Rothwell wrote: > >> Hi Eric, > >> > >> Today's linux-next merge of the userns tree got a conflict in > >> fs/namespace.c between

[PATCH 2/2] ARM: dts: add gpio alias in hi3620 dts file

Use gpio alias to identify the index of gpio chip. Then we can keep the same gpio number as schematics. Otherwise, gpio number is countered from bottom to top. Signed-off-by: Haojian Zhuang --- arch/arm/boot/dts/hi3620.dtsi | 22 ++ 1 file changed, 22 insertions(+) diff

[PATCH 1/2] gpio: pl061: get gpio base from alias id

If gpio base number isn't specified, the gpio base will be find from the end of gpio number. In order to keep with schematics, use alias to get the ID of gpio chip. Signed-off-by: Haojian Zhuang --- .../devicetree/bindings/gpio/gpio-pl061.txt| 31 ++

Re: linux-next: manual merge of the vfs tree with Linus' and te ext4 trees

On Mon, Apr 21, 2014 at 09:19:19PM -0400, Theodore Ts'o wrote: > On Tue, Apr 22, 2014 at 11:04:59AM +1000, Stephen Rothwell wrote: > > > > Today's linux-next merge of the vfs tree got a conflict in > > fs/ext4/extents.c between rebased versions of commits from Linus' and the > > ext4 trees and

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

Hi Eric, On Thu, 17 Apr 2014 00:18:44 -0700 ebied...@xmission.com (Eric W. Biederman) wrote: > > Stephen Rothwell writes: > > > After merging the userns tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > fs/namespace.c: In function 'new_mountpoint': > >

Re: [PATCH 1/1] block/blk-throttle.c: add static to blk_throtl_dispatch_work_fn

On 2014-04-17 13:41, Fabian Frederick wrote: blk_throtl_dispatch_work_fn is only used in blk-throttle.c Thanks, applied for 3.16. -- Jens Axboe -- 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

[PATCH v2] kernel/power/hibernate.c: use 'u64' instead of 's64' to avoid warning

For do_div(), it need 'u64' type, which means the outside must be sure of 'start' is not bigger than 'stop', or it will report warning. Even if 'start' was really bigger than 'stop', it would print incorrect information, but for kernel, it still can continue, so use WARN_ON() is enough. The

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

On Mon, Apr 21, 2014 at 6:14 PM, H. Peter Anvin wrote: > I wanted to avoid the "another cpu made this allocation, now I have to free" > crap, but I also didn't want to grab the lock if there was no work needed. I guess you also want to avoid bouncing all these cachelines around on boot on bit

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: fs/nfs/direct.c: In function 'nfs_direct_read_schedule_iovec': fs/nfs/direct.c:382:4: error: implicit declaration of function 'vfree' [-Werror=implicit-function-declaration]

Re: [PATCH v1 next 0/4] blk-mq: misc changes

On Tue, Apr 22, 2014 at 9:03 AM, Jens Axboe wrote: > On 2014-04-19 04:00, Ming Lei wrote: >> >> Hi, >> >> Three of them are fixes, another one is cleanup. >> >> V1: >> - line break(2/4) >> - use explicit cast(3/4) > > > I believe this is v2, but I guess your first posting was v0

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

On 2014年04月22日 05:38, Rafael J. Wysocki wrote: > Hi, > > On Wednesday, April 16, 2014 09:24:34 PM Lan Tianyu wrote: >> From: Lv Zheng >> >> The size of the buffer allocated for generic_serial_bus region access >> is not correct. This patch introduces acpi_ex_get_serial_access_length() >> to be

Re: linux-next: manual merge of the vfs tree with Linus' and te ext4 trees

On Tue, Apr 22, 2014 at 11:04:59AM +1000, Stephen Rothwell wrote: > > Today's linux-next merge of the vfs tree got a conflict in > fs/ext4/extents.c between rebased versions of commits from Linus' and the > ext4 trees and the same commits from the vfs tree. > > I fixed it up (I just used the

linux-next: manual merge of the vfs tree with Linus' tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in mm/filemap.c between commit b59b8cbca629 ("mm: fix new kernel-doc warning in filemap.c") from Linus' tree and commit cbabd10029a4 ("write_iter variants of {__,}generic_file_aio_write()") from the vfs tree. I fixed it up (I used

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

I wanted to avoid the "another cpu made this allocation, now I have to free" crap, but I also didn't want to grab the lock if there was no work needed. On April 21, 2014 6:06:19 PM PDT, Andrew Lutomirski wrote: >On Mon, Apr 21, 2014 at 5:53 PM, H. Peter Anvin wrote: >> Well, if 2^17 CPUs are

Re: [PATCH 3.13 00/32] 3.13.11-stable review

On Mon, Apr 21, 2014 at 06:06:06PM -0700, Guenter Roeck wrote: > On 04/20/2014 07:13 PM, Greg Kroah-Hartman wrote: > > > > > > Note, this is the LAST 3.13.y kernel I will be releasing. It will be > > end-of-life after this release, please move to 3.14.y at this time. > > > >

linux-next: manual merge of the vfs tree with the ext4 tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in fs/ext4/file.c between rebased commits from the ext4 tree and commit 29a8196bc41c ("convert ext4 to ->write_iter()") from the vfs tree. I fixed it up (in this case I used the conflicting hunks from the vfs tree - I hope its right)

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

On Mon, Apr 21, 2014 at 5:53 PM, H. Peter Anvin wrote: > Well, if 2^17 CPUs are allocated we might 2K pages allocated. We could > easily do a bitmap here, of course. NR_CPUS/64 is a small number, and would > reduce the code complexity. > Even simpler: just get rid of the check entirely.

Re: [blk] WARNING: CPU: 0 PID: 300 at kernel/softirq.c:156 _local_bh_enable_ip()

On 2014-04-20 14:30, Jet Chen wrote: Hi Zhiguo, I got the below dmesg and the first bad commit is git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit 2c575026fae6e63771bd2a4c1d407214a8096a89 Author: Hong Zhiguo AuthorDate: Wed Nov 20 10:35:05 2013 -0700 Commit:

Re: [PATCH 3.13 00/32] 3.13.11-stable review

On 04/20/2014 07:13 PM, Greg Kroah-Hartman wrote: Note, this is the LAST 3.13.y kernel I will be releasing. It will be end-of-life after this release, please move to 3.14.y at this time. This is the start of the stable review cycle for the 3.13.11 release.

linux-next: manual merge of the vfs tree with Linus' and te ext4 trees

Hi Al, Today's linux-next merge of the vfs tree got a conflict in fs/ext4/extents.c between rebased versions of commits from Linus' and the ext4 trees and the same commits from the vfs tree. I fixed it up (I just used the version from Linus' and the ext4 trees) and can carry the fix as necessary

Re: [PATCH v1 next 0/4] blk-mq: misc changes

On 2014-04-19 04:00, Ming Lei wrote: Hi, Three of them are fixes, another one is cleanup. V1: - line break(2/4) - use explicit cast(3/4) I believe this is v2, but I guess your first posting was v0 :-) Applied for testing for 3.16, thanks. -- Jens Axboe -- To unsubscribe

  1   2   3   4   5   6   7   8   9   10   >