[PATCH v2] checkpatch: Warn on unnecessary line continuations

When the previous line is not a line continuation and the current line has a line continuation but is not a #define, emit a warning. Signed-off-by: Joe Perches --- scripts/checkpatch.pl |9 + 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/scripts/checkpatch.pl

[PATCH] ext4: fix unjournaled inode bitmap modification

commit 119c0d4460b001e44b41dcf73dc6ee794b98bd31 changed ext4_new_inode() such that the inode bitmap was being modified outside a transaction, which could lead to corruption, and was discovered when journal_checksum found a bad checksum in the journal during log replay. Nix ran into this when

Re: [PATCH] exec: do not leave bprm->interp on stack

On Sat, Oct 27, 2012 at 1:16 PM, P J P wrote: > +-- On Sat, 27 Oct 2012, Kees Cook wrote --+ > | Al showed a list of them earlier in the thread. > > Yeah, the list Al showed and I came across mostly has - binfmt_aout - entry. > Do people still use - a.out - format? (considering ELF has been the

[PATCH]Documentation: Fixes a word in Documentation/arm64/memory.txt

Fixes a term in Documentation/arm64/memory.txt The modification is based on Catalin Marinas 's suggestion: "memory" in "ffc0 256GB memory" should be treated as "kernel logical memory map". Signed-off-by: Fu Wei --- Documentation/arm64/memory.txt |2 +-

Re: Linix-3.6.3 sda, sdb drives in reverse order (with a USB 2.0 drives and a monolithic kernel configuration)

On Sun, Oct 28, 2012 at 04:17:00AM +0100, Wallak wrote: > I've found where this issue come from. This behavior was introduced > with the commit: 0cc15d03bcccdf95e2bd82e094e6064e61b54207.The > description is available below. Removing this patch fix the drive > order. Hmm the patch should only

Documentation: Fixes a term's translation in Documentation/zh_CN/arm64/memory.txt

Fixes a term's translation in Documentation/zh_CN/arm64/memory.txt The modification is based on Catalin Marinas 's suggestion: "memory" in "ffc0 256GB memory" should be treated as "kernel logical memory map", so the translation should be "内核逻辑内存映射".

Re: Linix-3.6.3 sda, sdb drives in reverse order (with a USB 2.0 drives and a monolithic kernel configuration)

I've found where this issue come from. This behavior was introduced with the commit: 0cc15d03bcccdf95e2bd82e094e6064e61b54207.The description is available below. Removing this patch fix the drive order. Best Regards, Wallak. commit 0cc15d03bcccdf95e2bd82e094e6064e61b54207 Author: Andi Kleen

[PATCH] r8169: Fix WoL on RTL8168d/8111d.

This regression was spotted between Debian squeeze and Debian wheezy kernels (respectively based on 2.6.32 and 3.2). The fix was inspired by , using RTL_GIGA_MAC_VER_{25,26} for the RTL8168d/8111d chipset. Probable regression from

Re: drm i915 hangs on heavy io load

Hi Chris, I haven't answered due to several reboots necessary (sometimes I have to work on Win***) and no effect, but .. On Mi, 24 Okt 2012, Chris Wilson wrote: > > > http://cgit.freedesktop.org/~danvet/drm/commit/?h=ilk-wa-pile=0d5fed2de763b49bb1a90140758153481f043757 > > > is the missing

Re: [PATCH]Documentation:Chinese translation of Documentation/arm64/memory.txt

Thanks for your answer! So I will make a patch for it (in English and Chinese). For English patch ,if you like it, please acked it. 2012/10/27 Catalin Marinas : > On 27 October 2012 06:11, Ninja Tekkaman wrote: >> I have a question about the original document. >> what is the exact meaning about

Re: [PATCH V4 REPOST 2/2] kbuild: run the pre-processor on *.dts files

On 10/27/2012 07:06 PM, Rob Herring wrote: > Mark Brown wrote: > > On Fri, Oct 26, 2012 at 02:57:50PM -0500, Rob Herring wrote: > > Like I said previously, I think we first need guidelines on what > is and > isn't acceptable use of C preprocessor in dts files. > >

Re: [PATCH v3 2/6] Add the main bulk of core driver for SI476x code

On 10/27/2012 02:31 PM, Mark Brown wrote: > On Thu, Oct 25, 2012 at 03:26:02PM -0700, Andrey Smirnov wrote: >> On 10/25/2012 12:45 PM, Mark Brown wrote: >>> This really makes little sense to me, why are you doing this? Does the >>> device *really* layer a byte stream on top of I2C for sending

Re: [PATCH 163/193] net/dccp/ccids: remove CONFIG_EXPERIMENTAL

On Tue, 23 Oct 2012 13:03:56 -0700 Kees Cook wrote: > From: Kees Cook > To: linux-kernel@vger.kernel.org > Cc: Kees Cook , Gerrit Renker , > "David S. Miller" > Subject: [PATCH 163/193] net/dccp/ccids: remove CONFIG_EXPERIMENTAL > Date: Tue, 23 Oct 2012 13:03:56 -0700 > X-Mailer:

Re: [PATCH 162/193] net/dccp: remove CONFIG_EXPERIMENTAL

> This config item has not carried much meaning for a while now and is > almost always enabled by default. As agreed during the Linux kernel > summit, remove it. > > CC: Gerrit Renker > CC: "David S. Miller" > Signed-off-by: Kees Cook Acked-by: Gerrit Renker -- To unsubscribe from this list:

Re: [PATCH 2/3] ext4: introduce ext4_error_remove_page

Hi Ted, On Sat, Oct 27, 2012 at 06:16:26PM -0400, Theodore Ts'o wrote: > On Fri, Oct 26, 2012 at 10:24:23PM +, Luck, Tony wrote: > > > Well, we could set a new attribute bit on the file which indicates > > > that the file has been corrupted, and this could cause any attempts to > > > open the

[PATCH 5/5] fat: add mutex lock to fat_build_inode

From: Namjae Jeon fat_nfs_get_inode does not hold i_mutex of parent directory.So add lock to fat_build_inode. Signed-off-by: Namjae Jeon Signed-off-by: Ravishankar N Signed-off-by: Amit Sahrawat --- fs/fat/fat.h |1 + fs/fat/inode.c | 15 +++ 2 files changed, 16

[PATCH 4/5] fat: (exportfs) move code to rebuild directory-inode to separate function

From: Namjae Jeon Move the logic to rebuild directory inode (when mounted with nostale_ro) to new function fat_rebuild_parent Signed-off-by: Namjae Jeon Signed-off-by: Ravishankar N Signed-off-by: Amit Sahrawat --- fs/fat/nfs.c | 71

[PATCH 2/5] fat: restructure export operations

From: Namjae Jeon Define two nfs export_operation structures,one for 'stale_rw' mounts and the other for 'nostale_ro'.The former uses the generic export_encode_fh function to encode file handle, while the latter uses fat_encode_fh. Since inode number is not needed for nostale_ro, remove it from

[PATCH 3/5] fat: move fat_i_pos_read to fat.h

From: Namjae Jeon Originally, fat_i_pos_read was a static inline function in inode.c. The static keyword was removed so that it could be accessed from other files. However it is better to make it a static inline function in fat.h as suggested by Ogawa. Signed-off-by: Namjae Jeon Signed-off-by:

[PATCH 1/5] fat: remove parent_logstart check in fat_get_parent

From: Namjae Jeon The root directory inode is added to the directory hash table in fat_attach when mounted with nfs option. Since root dentry never expires until umount, fat_dget never fails to return the root inode for subdirectories of root inode.i.e., parent_logstart cannot be zero.

Re: ipc, msgqueue: NULL ptr deref in msgrcv

On 10/25/2012 08:43 PM, Sasha Levin wrote: > Hi all, > > While fuzzing with trinity inside a KVM tools (lkvm) guest running latest > -next, > I've stumbled on the follwing: > > [ 80.110944] NULL pointer dereference at 0011 > [ 80.110944] IP: [] testmsg.isra.5+0x40/0x70 > [

Re: [PATCH v2 1/1] freezer: change ptrace_stop/do_signal_stop to use freezable_schedule()

On Friday, October 26, 2012 02:29:09 PM Tejun Heo wrote: > Hello, > > On Fri, Oct 26, 2012 at 11:29:56PM +0200, Rafael J. Wysocki wrote: > > Actually, what tree is it supposed to apply to? > > > > The change in kernel/cgroup_freezer.c doesn't look like anything in > > the current Linus' tree to

Re: [BUG] perf parser: does not support arbitrary new sysfs events

On Sun, Oct 28, 2012 at 01:13:59AM +0200, Stephane Eranian wrote: > On Sat, Oct 27, 2012 at 10:34 PM, Jiri Olsa wrote: > > On Fri, Oct 26, 2012 at 10:23:09PM +0200, Stephane Eranian wrote: > >> Hi, > >> > >> The latest round of perf parser changes broke my PEBS-LL patch series > >> (at the last

Re: [BUG] perf parser: does not support arbitrary new sysfs events

On Sat, Oct 27, 2012 at 10:34 PM, Jiri Olsa wrote: > On Fri, Oct 26, 2012 at 10:23:09PM +0200, Stephane Eranian wrote: >> Hi, >> >> The latest round of perf parser changes broke my PEBS-LL patch series >> (at the last minute). For PEBS-LL, I need to add to generic events but I want >> to keep

Re: [ 108/147] ALSA: hda - Fix internal mic for Lenovo Ideapad U300s

On Thu, 2012-10-18 at 15:50 -0300, Herton Ronaldo Krzesinski wrote: > On Sun, Oct 14, 2012 at 03:37:21PM +0100, Ben Hutchings wrote: > > 3.2-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: David Henningsson > > > > commit

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On 10/27/12 4:19 PM, Eric Sandeen wrote: > On 10/27/12 1:47 PM, Nix wrote: >> On 27 Oct 2012, Theodore Ts'o said: >> >>> On Sat, Oct 27, 2012 at 01:45:25PM +0100, Nix wrote: Ah! it's turned on by journal_async_commit. OK, that alone argues against use of journal_async_commit, tested or

Re: [PATCH 2/3] ext4: introduce ext4_error_remove_page

On Fri, Oct 26, 2012 at 10:24:23PM +, Luck, Tony wrote: > > Well, we could set a new attribute bit on the file which indicates > > that the file has been corrupted, and this could cause any attempts to > > open the file to return some error until the bit has been cleared. > > That sounds a

[PATCH] firmware: use noinline_for_stack

The comment above fw_file_size() suggests it is noinline for stack size reasons. Use noinline_for_stack to make this more clear. Cc: Ming Lei Cc: Greg Kroah-Hartman Cc: Linus Torvalds Signed-off-by: Cesar Eduardo Barros --- drivers/base/firmware_class.c | 2 +- 1 file changed, 1

[Q] .readable_reg() not verified during read?

Hi Mark Looking at regmap.c it looks like the .readable_reg() callback is not consulted when performing a register read, e.g. in _regmap_raw_read(). Is this intentional? If yes - why? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer

[PATCH] x86: remove dummy long from EFI stub

Commit 2e064b1 (x86, efi: Fix issue of overlapping .reloc section for EFI_STUB) removed a dummy reloc added by commit 291f363 (x86, efi: EFI boot stub support), but forgot to remove the dummy long used by that reloc. Cc: Jordan Justen Cc: Matt Fleming Cc: "H. Peter Anvin" Cc: Thomas Gleixner

[PATCH] x86: fix comment for set_real_mode_permissions

The function which gets called very early is setup_real_mode(). The set_real_mode_permissions() function is the arch_initcall. Cc: Jarkko Sakkinen Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Signed-off-by: Cesar Eduardo Barros --- arch/x86/realmode/init.c | 2 +- 1 file

Re: [PATCH v2 1/1] freezer: change ptrace_stop/do_signal_stop to use freezable_schedule()

On Fri, 2012-10-26 at 19:46 +0200, Oleg Nesterov wrote: > try_to_freeze_tasks() and cgroup_freezer rely on scheduler locks > to ensure that a task doing STOPPED/TRACED -> RUNNING transition > can't escape freezing. This mostly works, but ptrace_stop() does > not necessarily call schedule(), it can

Re: [PATCH V4 REPOST 2/2] kbuild: run the pre-processor on *.dts files

On Fri, Oct 26, 2012 at 02:57:50PM -0500, Rob Herring wrote: > Like I said previously, I think we first need guidelines on what is and > isn't acceptable use of C preprocessor in dts files. Didn't we already say that it was just the same rules as for things tht get included in .S files? Besides

Re: [Patch v3 2/7] Regulator: DA9055 Regulator driver

On Thu, Oct 11, 2012 at 03:39:24PM +0530, Ashish Jangam wrote: > This is the Regulator patch for the DA9055 PMIC and has got dependency on > the DA9055 MFD core. Always submit patches with subject lines appropriate for the subsystem, this helps get your patch noticed. People do things like

[PATCH 2/2] staging/comedi: Use dev_ printks in drivers/quatech_daqp_cs.c

fixed below checkpatch warnings. - WARNING: printk() should include KERN_ facility level Signed-off-by: YAMANE Toshiaki --- drivers/staging/comedi/drivers/quatech_daqp_cs.c |9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git

[PATCH 1/2] staging/comedi: Fix trailing statements should be on next line in drivers/quatech_daqp_cs.c

fixed below checkpatch errors. - ERROR: trailing statements should be on next line Signed-off-by: YAMANE Toshiaki --- drivers/staging/comedi/drivers/quatech_daqp_cs.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/staging/comedi/drivers/quatech_daqp_cs.c

Re: [PATCH 3.7-rc1] omap zoom2.c: Fix compile error by including correct header files

On Wed, Oct 03, 2012 at 09:31:02AM -0700, Tony Lindgren wrote: > Actually we can also drop "#include " too, > it's now empty for mach-omap2. I've updated Tim's patch below > for you guys to queue via the ASoC fixes. It's against the > current linux next. Applied. Tim, you should send patches

Re: [PATCH] gpiolib: Don't return -EPROBE_DEFER to sysfs, or for invalid gpios

On Fri, Oct 26, 2012 at 09:26:33AM +0200, Linus Walleij wrote: > On Thu, Oct 25, 2012 at 1:03 PM, Mathias Nyman > > gpios requested with invalid numbers, or gpios requested from userspace via > > sysfs > > should not try to be deferred on failure. > Very good catch. I applied this to my fixes

Re: [PATCH v2 2/4] gpio: add viperboard gpio driver

On Sat, Oct 27, 2012 at 06:14:16PM +0200, Linus Walleij wrote: > I think you've done an honest effort (more than most would do for sure) > to explore the ways of the regmap. If it doesn't fit, it doesn't fit and > that's it. The bus stuff is needed by a bunch of other drivers - there's a similar

Re: [PATCH v3 2/6] Add the main bulk of core driver for SI476x code

On Thu, Oct 25, 2012 at 03:26:02PM -0700, Andrey Smirnov wrote: > On 10/25/2012 12:45 PM, Mark Brown wrote: > > This really makes little sense to me, why are you doing this? Does the > > device *really* layer a byte stream on top of I2C for sending messages > > that look like marshalled register

[PATCH 0/2] mm: do not call frontswap_init() during swapoff

The call to frontswap_init() was added in a place where it is called not only from sys_swapon, but also from sys_swapoff. This pair of patches fixes that. The first patch moves the acquisition of swap_lock from enable_swap_info to two separate helpers, one for sys_swapon and one for sys_swapoff.

[PATCH 1/2] mm: refactor reinsert of swap_info in sys_swapoff

The block within sys_swapoff which re-inserts the swap_info into the swap_list in case of failure of try_to_unuse() reads a few values outside the swap_lock. While this is safe at that point, it is subtle code. Simplify the code by moving the reading of these values to a separate function,

[GIT PULL] MXS SPI fixes for v3.7

The following changes since commit ddffeb8c4d0331609ef2581d84de4d763607bd37: Linux 3.7-rc1 (2012-10-14 14:41:04 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git tags/spi-mxs for you to fetch changes up to

[PATCH 2/2] mm: do not call frontswap_init() during swapoff

The call to frontswap_init() was added within enable_swap_info(), which was called not only during sys_swapon, but also to reinsert the swap_info into the swap_list in case of failure of try_to_unuse() within sys_swapoff. This means that frontswap_init() might be called more than once for the same

[PATCH 4/5] perf tool: Move strxfrchar into string object

Moving strxfrchar function into string object. Signed-off-by: Jiri Olsa Cc: Corey Ashford Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Arnaldo Carvalho de Melo --- tools/perf/util/string.c | 18 ++

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On 10/27/12 1:47 PM, Nix wrote: > On 27 Oct 2012, Theodore Ts'o said: > >> On Sat, Oct 27, 2012 at 01:45:25PM +0100, Nix wrote: >>> Ah! it's turned on by journal_async_commit. OK, that alone argues >>> against use of journal_async_commit, tested or not, and I'd not have >>> turned it on if I'd

[PATCH 0/5] perf dso: Separate dso symbols to separate object

hi, separating dso related stuff into dso object plus some other symbol object cleanup. It's just a code moving, no actual change was done. Attached patches: 1/5 perf tool: Move build_id__sprintf into build-id object 2/5 perf tool: Move BUILD_ID_SIZE into build-id object 3/5 perf tool: Move

[PATCH 3/5] perf tool: Move hex2u64 into util object

Moving hex2u64 function into util object. Signed-off-by: Jiri Olsa Cc: Corey Ashford Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Arnaldo Carvalho de Melo --- tools/perf/util/symbol.c | 33 -

[PATCH 1/5] perf tool: Move build_id__sprintf into build-id object

Moving build_id__sprintf function into build-id object. Signed-off-by: Jiri Olsa Cc: Corey Ashford Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Arnaldo Carvalho de Melo --- tools/perf/builtin-buildid-cache.c | 2 +-

[PATCH 5/5] perf tool: Move dso_* related functions into dso object

Moving dso_* related functions into dso object. Keeping symbol loading related functions still in the symbol object as it seems more convenient. Signed-off-by: Jiri Olsa Cc: Corey Ashford Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc:

[PATCH 2/5] perf tool: Move BUILD_ID_SIZE into build-id object

Moving BUILD_ID_SIZE define into build-id object, plus include related changes. Signed-off-by: Jiri Olsa Cc: Corey Ashford Cc: Frederic Weisbecker Cc: Ingo Molnar Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Arnaldo Carvalho de Melo --- tools/perf/builtin-buildid-cache.c |

Re: [PATCH] regmap: Fix printing of size_t variable

On Thu, Oct 25, 2012 at 03:52:32PM -0700, Randy Dunlap wrote: > Acked-by: Randy Dunlap There's not much point in doing this after a patch has been applied... > http://marc.info/?l=linux-kernel=135041943424273=2 So, the difference between Fabio's patch and your patch is that he sent the patch

Re: [ 60/85] xtensa: add missing system calls to the syscall table

Hi Ben, On 10/27/2012 11:26 AM, Ben Hutchings wrote: > On Thu, 2012-10-25 at 17:06 -0700, Greg Kroah-Hartman wrote: > [...] >> #define __NR_available287 287 >> -__SYSCALL(287, sys_faccessat, 0) >> +__SYSCALL(287, sys_ni_syscall, 0) > [...] > > Why was this one un-plumbed

Re: [BUG] perf parser: does not support arbitrary new sysfs events

On Fri, Oct 26, 2012 at 10:23:09PM +0200, Stephane Eranian wrote: > Hi, > > The latest round of perf parser changes broke my PEBS-LL patch series > (at the last minute). For PEBS-LL, I need to add to generic events but I want > to keep them PMU specific. As such, they need to live in the sysfs

Re: [PATCH 33/33] perf, tools: List kernel supplied event aliases in perf list v2

On Fri, Oct 26, 2012 at 01:30:15PM -0700, Andi Kleen wrote: > From: Andi Kleen > > List the kernel supplied pmu event aliases in perf list > > It's better when the users can actually see them. with the HW events being part of PMU 'events' dir we get single HW events listed twice

Re: [PATCH] exec: do not leave bprm->interp on stack

+-- On Sat, 27 Oct 2012, Kees Cook wrote --+ | Al showed a list of them earlier in the thread. Yeah, the list Al showed and I came across mostly has - binfmt_aout - entry. Do people still use - a.out - format? (considering ELF has been the default standard for so many years) | I don't have

Re: [PATCH 32/33] perf, tools: Default to cpu// for events v2

On Fri, Oct 26, 2012 at 01:30:14PM -0700, Andi Kleen wrote: > From: Andi Kleen > > When an event fails to parse and it's not in a new style format, > try to parse it again as a cpu event. > > This allows to use sysfs exported events directly without //, so I can use > > perf record -e

[PATCH 2/2] MAINTAINERS: add pinctrl atmel at91 entry

Cc: linux-kernel@vger.kernel.org Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD --- MAINTAINERS |6 ++ 1 file changed, 6 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 027ec2b..cb97031 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -5624,6 +5624,12 @@ S: Maintained F:

Re: [PATCH 31/33] perf, tools: Support generic events as pmu event names v2

On Fri, Oct 26, 2012 at 01:30:13PM -0700, Andi Kleen wrote: > From: Andi Kleen > > Extend the parser/lexer to allow generic event names like > "instructions" as a sysfs supplied PMU event name. > > This resolves the problem that cpu/instructions/ gives a parse > error, even when the kernel

Re: [PATCH 27/33] tools, perf: Add a precise event qualifier

On Fri, Oct 26, 2012 at 01:30:09PM -0700, Andi Kleen wrote: > From: Andi Kleen > > Add a precise qualifier, like cpu/event=0x3c,precise=1/ hm, I think this works already via 'p' modifier like: cpu/event=0x3c/p jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel"

Re: [PATCH 25/33] perf, tools: Support events with - in the name

On Fri, Oct 26, 2012 at 01:30:07PM -0700, Andi Kleen wrote: > From: Andi Kleen > > - looks nicer than _, so allow - in the event names. Used for various > of the arch perfmon and Haswell events. > > Signed-off-by: Andi Kleen > --- > tools/perf/util/parse-events.l |2 +- > 1 files changed,

[ANNOUNCE] 3.6.3-rt8

Dear RT Folks, I'm pleased to announce the 3.6.3-rt8 release. Changes since 3.6.3-rt7: * Fix the SLUB fallout on NUMA machines I missed to fixup the smp function calls which can result in a deadlock on RT. * Fix a mainline issue with cpufreq/powernow-k8 (Same patch is

Re: [PATCH] cpufreq: powernow-k8: Remove bogus smp_processor_id() usage

On Sat, 27 Oct 2012, Tejun Heo wrote: > Hello, Thomas. > > On Sat, Oct 27, 2012 at 07:29:25PM +0200, Thomas Gleixner wrote: > > This is fully preemptible non cpu bound context though the comment in the > > code says: > > > > * Must run on @pol->cpu. cpufreq core is responsible for

Re: [PATCH 0/7] Add support for Freescale's mc34708 to mc13xxx driver

Hi Samuel, On Thu, Oct 4, 2012 at 10:51 AM, Samuel Ortiz wrote: >> I want to add mc34708 support to mx53qsb and need this series to be applied. > I understand. I'll queue it to my for-next branch as soon as the merge window > is closed. Could you please queue this series? I still do not see it

[PATCH] slub: Use the correct per cpu slab on CPU_DEAD

While making slub available for RT I noticed, that during CPU offline for each kmem_cache __flush_cpu_slab() is called on a live CPU. This correctly flushs the cpu_slab of the dead CPU via flush_slab. Though unfreeze_partials which is called from __flush_cpu_slab() after that looks at the cpu_slab

Re: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

On 10/27/2012 06:56 AM, Daniel Vetter wrote: On Fri, Oct 26, 2012 at 10:57 PM, Justin P. Mattock wrote: :~/drm> git clone git://people.freedesktop.org/~danvet/drm Cloning into 'drm'... remote: Counting objects: 2728390, done. remote: Compressing objects: 100% (418606/418606), done. remote:

Re: [PATCH] cpufreq: powernow-k8: Remove bogus smp_processor_id() usage

Hello, Thomas. On Sat, Oct 27, 2012 at 07:29:25PM +0200, Thomas Gleixner wrote: > This is fully preemptible non cpu bound context though the comment in the > code says: > >* Must run on @pol->cpu. cpufreq core is responsible for ensuring >* that we're bound to the current CPU

Re: [PATCH 24/33] perf, tools: Move parse_events error printing to parse_events_options

On Fri, Oct 26, 2012 at 01:30:06PM -0700, Andi Kleen wrote: > From: Andi Kleen > > The callers of parse_events usually have their own error handling. > Move the fprintf for a bad event to parse_events_options, which > is the only one who should need it. > > Signed-off-by: Andi Kleen > --- >

[PATCH] Add FDT support to Pandaboard initialization

From: Constantine Shulyupin Problem: - FDT is supported only by generic OMAP board initialization in arch/arm/mach-omap2/board-generic.c and lacks some configurations, which are not yet configured in FDT (USB for example). Solution: - arch/arm/mach-omap2/board-omap4panda.c supports

Re: [PATCH] Remove uninitialized_var()

On Sat, 27 Oct 2012 15:12:03 +0200 Ingo Molnar wrote: > There's 3 types of conversions done: > >uninitialized_var(x)=> x = 0 /* for scalar types */ >uninitialized_var(x)=> x = NULL/* for pointers */ >uninitialized_var(x)=> x = { } /* for

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On 27 Oct 2012, Theodore Ts'o said: > On Sat, Oct 27, 2012 at 01:45:25PM +0100, Nix wrote: >> Ah! it's turned on by journal_async_commit. OK, that alone argues >> against use of journal_async_commit, tested or not, and I'd not have >> turned it on if I'd noticed that. >> >> (So, the combinations

[PATCH 2/2] staging: csr: Remove struct CsrEvent

No one use struct CsrEvent. So it's unnecessary. Signed-off-by: SeongJae Park --- drivers/staging/csr/csr_framework_ext_types.h | 12 1 file changed, 12 deletions(-) diff --git a/drivers/staging/csr/csr_framework_ext_types.h b/drivers/staging/csr/csr_framework_ext_types.h index

[PATCH 1/2] staging: csr: Remove CsrEventHandle

No one use CsrEventHandle, No one call functions using it as parameter. So those are not need to be here. Signed-off-by: SeongJae Park --- drivers/staging/csr/csr_framework_ext.h | 61 - drivers/staging/csr/csr_framework_ext_types.h |2 - 2 files changed, 63

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On 10/27/12 7:45 AM, Nix wrote: > [nfs people purged from Cc] > > On 27 Oct 2012, Theodore Ts'o verbalised: > >> Huh? It's not turned on by default. If you mount with no mount >> options, journal checksums are *not* turned on. > > ?! it's turned on for me, and though I use weird mount options

Re: [ 60/85] xtensa: add missing system calls to the syscall table

On Thu, 2012-10-25 at 17:06 -0700, Greg Kroah-Hartman wrote: > 3.6-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Chris Zankel > > commit 7216cabfff5149670445cd65d415ed5db21314b4 upstream. > > Add the following system calls to the

[PATCH] sched, autogroup: fix crash on reboot when autogroup is disabled

On Fri, 2012-10-26 at 13:29 -0700, Mike Galbraith wrote: > On Sat, 2012-10-20 at 08:38 -0400, Mike Galbraith wrote: > > > So what I would do is either let the user decide once at boot, in which > > case if off, creating groups would be stupid), or, just rip autogroup > > completely out, since

[PATCH] PPC: ePAPR: Convert header to uapi

The new uapi framework splits kernel internal and user space exported bits of header files more cleanly. Adjust the ePAPR header accordingly. Signed-off-by: Alexander Graf --- arch/powerpc/include/asm/Kbuild |1 - arch/powerpc/include/asm/epapr_hcalls.h | 56

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On Sat, Oct 27, 2012 at 01:45:25PM +0100, Nix wrote: > Ah! it's turned on by journal_async_commit. OK, that alone argues > against use of journal_async_commit, tested or not, and I'd not have > turned it on if I'd noticed that. > > (So, the combinations I'll be trying for effect on this bug are:

[PATCH] cpufreq: powernow-k8: Remove bogus smp_processor_id() usage

commit 6889125b (cpufreq/powernow-k8: workqueue user shouldn't migrate the kworker to another CPU) has a broken optimization of calling powernowk8_target_fn() directly from powernowk8_target() which results in the following splat: [ 11.789468] BUG: using smp_processor_id() in preemptible

Re: [ 26/85] usb: host: xhci: New system added for Compliance Mode Patch on SN65LVPE502CP

On Thu, 2012-10-25 at 17:05 -0700, Greg Kroah-Hartman wrote: > 3.6-stable review patch. If anyone has any objections, please let me know. > > -- > > From: "Alexis R. Cortes" > > commit 470809741a28c3092279f4e1f3f432e534d46068 upstream. > > This minor change adds a new system

Re: [PATCH] arm: mvebu: support for the Globalscale Mirabox MBX0001 board

On Sat, 27 Oct 2012 18:22:45 +0200, Gregory CLEMENT wrote: > This platform, available from Globalscale has an Armada 370. For now, > only the serial port is supported. Support for network, USB and other > peripherals will be added as drivers for them become available for > Armada 370 in mainline.

Re: [GIT PULL 0/9] perf/core improvements and fixes

On Fri, Oct 26, 2012 at 5:31 PM, Namhyung Kim wrote: > 2012-10-26 (금), 09:06 -0600, David Ahern: >> On 10/26/12 8:54 AM, Ingo Molnar wrote: >> >> perf/core improvements: >> >> >> >> . perf inject changes to allow showing where a task sleeps, from Andrew >> >> Vagin. >> >> >> >> . Makefile

Re: [PATCH] staging: csr: Fix typo in csr/netdev.c

On 27 October 2012 15:53, Masanari Iida wrote: > Correct spelling typo in trace message. > > Signed-off-by: Masanari Iida > --- > drivers/staging/csr/netdev.c | 14 +++--- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/drivers/staging/csr/netdev.c

Re: [PATCH] exec: do not leave bprm->interp on stack

On Sat, Oct 27, 2012 at 3:47 AM, P J P wrote: > +-- On Fri, 26 Oct 2012, Al Viro wrote --+ > | > not. Module alias could dodge this though, I guess. > | "Could"? Can you show a single module that would have name matching > | binfmt-[0-9a-f]*? In other words, are they ever loaded _not_ via an >

Re: [ 16/85] use clamp_t in UNAME26 fix

On Sat, Oct 27, 2012 at 05:11:58PM +0100, Ben Hutchings wrote: > On Thu, 2012-10-25 at 17:05 -0700, Greg Kroah-Hartman wrote: > > 3.6-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Kees Cook > > > > commit

Re: [PATCH] arm: mvebu: support for the Globalscale Mirabox MBX0001 board

On Sat, 27 Oct 2012 18:44:48 +0200, Andrew Lunn wrote: > > diff --git a/arch/arm/boot/dts/mbx001.dts b/arch/arm/boot/dts/mbx001.dts > > new file mode 100644 > > index 000..88a5a11 > > --- /dev/null > > +++ b/arch/arm/boot/dts/mbx001.dts > > Hi Gregory > > Maybe it would be good to prefix

RE: [PATCH v4 5/5] zynq: move static peripheral mappings

HI Josh and Nick, look below. > -Original Message- > From: Josh Cartwright [mailto:josh.cartwri...@ni.com] > Sent: Friday, October 26, 2012 3:03 AM > To: Nick Bowler > Cc: a...@kernel.org; Arnd Bergmann; linux-kernel@vger.kernel.org; linux-arm- > ker...@lists.infradead.org; John Linn;

RE: [PATCH v4 3/5] zynq: remove use of CLKDEV_LOOKUP

> -Original Message- > From: Josh Cartwright [mailto:josh.cartwri...@ni.com] > Sent: Wednesday, October 24, 2012 10:04 PM > To: a...@kernel.org; Arnd Bergmann > Cc: linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org; John > Linn; Nick Bowler; Michal Simek > Subject:

Re: [PATCH] arm: mvebu: support for the Globalscale Mirabox MBX0001 board

> diff --git a/arch/arm/boot/dts/mbx001.dts b/arch/arm/boot/dts/mbx001.dts > new file mode 100644 > index 000..88a5a11 > --- /dev/null > +++ b/arch/arm/boot/dts/mbx001.dts Hi Gregory Maybe it would be good to prefix this with armada-370. It then fits with armada-370-db.dts, and all the

Re: [PATCH] arm: mvebu: support for the Globalscale Mirabox MBX0001 board

On 10/27/2012 06:33 PM, Thomas Petazzoni wrote: On Sat, 27 Oct 2012 18:22:45 +0200, Gregory CLEMENT wrote: This platform, available from Globalscale has an Armada 370. For now, only the serial port is supported. Support for network, USB and other peripherals will be added as drivers for them

Re: [PATCH] arm: mvebu: support for the Globalscale Mirabox MBX0001 board

Hello, On Sat, 27 Oct 2012 18:22:45 +0200, Gregory CLEMENT wrote: > This platform, available from Globalscale has an Armada 370. For now, > only the serial port is supported. Support for network, USB and other > peripherals will be added as drivers for them become available for > Armada 370 in

Re: [ 18/85] x86: Exclude E820_RESERVED regions and memory holes above 4 GB from direct mapping.

On Thu, 2012-10-25 at 17:05 -0700, Greg Kroah-Hartman wrote: > 3.6-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Jacob Shin > > commit 1e779aabe1f0768c2bf8f8c0a5583679b54a upstream. > > On systems with very large memory (1 TB in

[PATCH] arm: mvebu: support for the Globalscale Mirabox MBX0001 board

This platform, available from Globalscale has an Armada 370. For now, only the serial port is supported. Support for network, USB and other peripherals will be added as drivers for them become available for Armada 370 in mainline. Signed-off-by: Gregory CLEMENT --- arch/arm/boot/dts/Makefile

Re: [PATCH 5/5] debugfs: remove goto in debugfs_remount()

2012/10/27 Greg KH : > On Sat, Oct 27, 2012 at 04:05:29PM +0800, Yan Hong wrote: >> Simple code clean to remove goto. > > There is nothing wrong with gotos on error paths, so this one should > stay. > > greg k-h I thought we use goto on error path because there is no other elegant ways to do the

Re: [PATCH -next] GPIO: clps711x: use platform_device_unregister in gpio_clps711x_init()

On Fri, Oct 26, 2012 at 5:15 PM, Wei Yongjun wrote: > From: Wei Yongjun > > platform_device_unregister() only calls platform_device_del() and > platform_device_put(), thus use platform_device_unregister() to > simplify the code. > > Also the documents in platform.c shows that

Re: [PATCH 1/4] mfd: ab8500: add devicetree support for fuelgauge

On 10/27/2012 06:00 PM, Rajanikanth HV wrote: > On 27 October 2012 20:37, Francesco Lavra wrote: >> On 10/25/2012 08:30 AM, Rajanikanth H.V wrote: >>> From: "Rajanikanth H.V" >>> + bat_tech = of_get_property(np_bat_supply, >>> + "stericsson,battery-type", NULL); >>> +

Re: [PATCH v2 2/4] gpio: add viperboard gpio driver

On Fri, Oct 26, 2012 at 11:16 AM, Lars Poeschel wrote: > I am a bit unsure what to do now. Since Linus said he would take my driver > without regmap, this will be my way for the driver. Please submit the code in the shape you want me to merge it. I think you've done an honest effort (more than

Re: [ 16/85] use clamp_t in UNAME26 fix

On Thu, 2012-10-25 at 17:05 -0700, Greg Kroah-Hartman wrote: > 3.6-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Kees Cook > > commit 31fd84b95eb211d5db460a1dda85e004800a7b52 upstream. > > The min/max call needed to have explicit

[PATCH 2/2] zram: handle mem suffixes in disk size zram_sysfs parameter

zram: handle mem suffixes in disk size zram_sysfs parameter Use memparse() to allow mem suffixes in disksize sysfs number. Examples: echo 256K > /sys/block/zram0/disksize echo 512M > /sys/block/zram0/disksize echo 1G > /sys/block/zram0/disksize Signed-off-by:

[PATCH 1/2] zram: factor-out zram_decompress_page() function

zram: factor-out zram_decompress_page() function zram_bvec_read() shared decompress functionality with zram_read_before_write() function. Factor-out and make commonly used zram_decompress_page() function, which also simplified error handling in zram_bvec_read(). Signed-off-by:

  1   2   3   4   5   >