Re: [patch 1/2] mm: fincore()

On Sat, 16 Feb 2013 14:53:43 +1030 Rusty Russell wrote: > Andrew Morton writes: > > On Fri, 15 Feb 2013 18:13:04 -0500 > > Johannes Weiner wrote: > >> I dunno. The byte vector might not be optimal but its worst cases > >> seem more attractive, is just as extensible, and dead simple to use. >

[ 30/66] [media] gspca_kinect: add Kinect for Windows USB id

3.2-stable review patch. If anyone has any objections, please let me know. -- From: Jacob Schloss commit 98fd485795db064d0885150e2c0c7f296d8fe06e upstream. Add the USB ID for the Kinect for Windows RGB camera so it can be used with the gspca_kinect driver. Signed-off-by:

[ 21/66] USB: storage: Define a new macro for USB storage match rules

3.2-stable review patch. If anyone has any objections, please let me know. -- From: fangxiaozhi commit 07c7be3d87e5cdaf5f94c271c516456364ef286c upstream. 1. Define a new macro for USB storage match rules: matching with Vendor ID and interface descriptors. Signed-off-by:

[ 25/66] drivers/rtc/rtc-pl031.c: fix the missing operation on enable

3.2-stable review patch. If anyone has any objections, please let me know. -- From: Haojian Zhuang commit e7e034e18a0ab6bafb2425c3242cac311164f4d6 upstream. The RTC control register should be enabled in the process of initializing. Without this patch, I failed to enable RTC

[ 18/66] USB: ftdi_sio: add PID/VID entries for ELV WS 300 PC II

3.2-stable review patch. If anyone has any objections, please let me know. -- From: Sven Killig commit c249f911406efcc7456cb4af79396726bf7b8c57 upstream. Add PID/VID entries for ELV WS 300 PC II weather station Signed-off-by: Sven Killig Signed-off-by: Greg Kroah-Hartman

[ 16/66] drm/radeon: prevent crash in the ring space allocation

3.2-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit fd5d93a0015ce1a7db881382022b2fcdfdc61760 upstream. If the requested number of DWs on the ring is larger than the size of the ring itself, return an error. In testing with

[ 03/66] xhci: Fix TD size for isochronous URBs.

3.2-stable review patch. If anyone has any objections, please let me know. -- From: Sarah Sharp commit f18f8ed2a9adc41c2d9294b85b6af115829d2af1 upstream. To calculate the TD size for a particular TRB in an isoc TD, we need know the endpoint's max packet size. Isochronous

Re: [patch 1/2] mm: fincore()

On Sat, Feb 16, 2013 at 02:53:43PM +1030, Rusty Russell wrote: > Andrew Morton writes: > > On Fri, 15 Feb 2013 18:13:04 -0500 > > Johannes Weiner wrote: > >> I dunno. The byte vector might not be optimal but its worst cases > >> seem more attractive, is just as extensible, and dead simple to

Re: Debugging Thinkpad T430s occasional suspend failure.

On 02/16/2013 11:46 AM, Linus Torvalds wrote: Adding Peter Anvin to the people, just in case he sees what's wrong with the system call stub generation that keeps excessively old object files around. If it's easy to fix, it might be worth trying to make it ok to switch from i386 to x86-64 and

Re: [PATCH] DocBook: update EXPORT_SYMBOL entry to point at export.h

On 02/14/2013 02:32:04 PM, Paul Gortmaker wrote: Previously we used to get EXPORT_SYMBOL and friends from module.h but we moved away from that since module.h largely includes the entire header space one way or another. As most users just wanted the simple export related macros, they were spun

Re: [v3 0/6] ARM: tegra: convert device tree files to use CLK defines

Hi Hiroshi, On Fri, Feb 15, 2013 at 12:43 AM, Hiroshi Doyu wrote: > Hi, > > With new dtc+cpp feature, we could get rid of magic numbers in dts* > files. This patch replaces CLK IDs. > > We also plan to share those DT header files with kernel source > later[1]. > > This series depends on: >

Re: [patch 1/2] mm: fincore()

Andrew Morton writes: > On Fri, 15 Feb 2013 18:13:04 -0500 > Johannes Weiner wrote: >> I dunno. The byte vector might not be optimal but its worst cases >> seem more attractive, is just as extensible, and dead simple to use. > > But I think "which pages from this 4TB file are in core" will not

Re: [v3 0/6] ARM: tegra: convert device tree files to use CLK defines

On 02/15/2013 02:43:11 AM, Hiroshi Doyu wrote: Hi, With new dtc+cpp feature, we could get rid of magic numbers in dts* files. This patch replaces CLK IDs. We also plan to share those DT header files with kernel source later[1]. ... [1]

kswapd craziness round 2

Hi, You still feel the sour taste of the "kswapd craziness in v3.7" thread, right? Welcome to the hell, part two :{. I believe this started happening after update from 3.8.0-rc4-next-20130125 to 3.8.0-rc7-next-20130211. The same as before, many hours of uptime are needed and perhaps some

Re: [PATCH 0/9] System Framebuffer Bus (sysfb)

> > This series tries to fix the mess with global system framebuffer access in > device drivers. Currently, architecture initialization sets the "screen_info" > object according to the system framebuffer that was detected during boot. The > device driver that can map VMEM first gets access to it.

Re: [RFC] sched: The removal of idle_balance()

On Sun, 2013-02-17 at 08:14 +0100, Mike Galbraith wrote: > (And puts a dent in x264 ultrafast) > > +SD_BALANCE_NEWIDLE > encoded 600 frames, 425.04 fps, 22132.71 kb/s > encoded 600 frames, 416.07 fps, 22132.71 kb/s > encoded 600 frames, 417.49 fps, 22132.71 kb/s > encoded 600 frames, 420.65 fps,

[PATCH 1/3] Drivers: hv: vmbus: Handle channel rescind message correctly

Properly cleanup the channel state on receipt of the "offer rescind" message. Starting with ws2012, the host requires that the channel "relid" be properly cleaned up when the offer is rescinded. Signed-off-by: K. Y. Srinivasan Reviewed-by: Haiyang Zhang --- drivers/hv/channel_mgmt.c | 11

[PATCH 3/3] Drivers: hv: balloon: Execute hot-add code in a separate context

Execute the hot-add operation in a separate work context. This allows us to decouple the pressure reporting activity from the "hot-add" activity. Signed-off-by: K. Y. Srinivasan Reviewed-by: Haiyang Zhang --- drivers/hv/hv_balloon.c | 40 ++-- 1 files

[PATCH 2/3] Drivers: hv: balloon: Execute balloon inflation in a separate context

Execute the balloon inflation operation in a separate work context. This allows us to decouple the pressure reporting activity from the ballooning activity. Testing has shown that this decoupling makes the guest more reponsive. Signed-off-by: K. Y. Srinivasan Reviewed-by: Haiyang Zhang ---

[PATCH 0/3] Drivers: hv

The patch for the vmbus drivers properly cleans up the channel state on receipt of the "offer rescind" message. The balloon driver patches permit the execution of both "balloon up" operation as well as the "hot-add" operation in separate execution contexts. This allows the balloon driver to be

Re: Debugging Thinkpad T430s occasional suspend failure.

2013/2/17 Frederic Weisbecker : > 2013/2/17 Linus Torvalds : >> On Sun, Feb 17, 2013 at 7:11 AM, Frederic Weisbecker >> wrote: >>> >>> preempt_value_in_interrupt() looks buggy in your patch: it makes >>> invoke_softirq() returning if (val & HARDIRQ_MASK). But that's always >>> true since you

Re: Debugging Thinkpad T430s occasional suspend failure.

2013/2/17 Linus Torvalds : > On Sun, Feb 17, 2013 at 7:11 AM, Frederic Weisbecker > wrote: >> >> preempt_value_in_interrupt() looks buggy in your patch: it makes >> invoke_softirq() returning if (val & HARDIRQ_MASK). But that's always >> true since you have moved further the

Re: [Bisected] 3.7-rc1 can't resume

T43 is quite old... which might have exposed unique bugs. How reliable is the failure? Even one misidentified commit results in git bisect giving garbage. Jonas Heinrich wrote: >Hello, >since kernel version 3.7-rc1 I can't resume my notebook (Thinkpad T43) >from suspend2ram anymore. > >I

Re: [Bisected] 3.7-rc1 can't resume

On Sunday, February 17, 2013 05:48:25 PM Jonas Heinrich wrote: > Hello, > since kernel version 3.7-rc1 I can't resume my notebook (Thinkpad T43) > from suspend2ram anymore. > > I started a kernel bisection (see bisection_log in attachement). Also > see kernel conifg @ attachement. > > The

Re: [PATCH 0/3] coredump: fix the ancient signal problems

On 02/17, Oleg Nesterov wrote: > > On 02/17, Linus Torvalds wrote: > > > > SIGKILL really is very very special. Having it kill a > > coredump in progress sounds fine to me. > > Great. Forgot to mention just in case... We could probably make a simpler patch. do_coredump() can ignore all signals

Re: [PATCH 0/3] coredump: fix the ancient signal problems

On 02/17, Linus Torvalds wrote: > > On Sun, Feb 17, 2013 at 11:18 AM, Oleg Nesterov wrote: > > > > Linus, et al, could you please ack/nack the intent? Of course I will > > appreciate if you can review the code, but what I am actually worried > > about is the user-visible change: the coredumping

Re: [PATCH 04/16] rcu: rcutiny: Prevent RCU stall

On Wed, Feb 13, 2013 at 05:11:59PM +0100, Sebastian Andrzej Siewior wrote: > From: Thomas Gleixner > > rcu_read_unlock_special() checks in_serving_softirq() and leaves early > when true. On RT this is obviously wrong as softirq processing context > can be preempted and therefor such a task can

Re: Debugging Thinkpad T430s occasional suspend failure.

On Sat, Feb 16, 2013 at 11:46:59AM -0800, Linus Torvalds wrote: > On Sat, Feb 16, 2013 at 11:25 AM, Paul E. McKenney > wrote: > > > > Sorry for the delay in testing this, but there was a need to upgrade > > my laptop, and bozo here figured "why not go to 64 bits while I am at > > it?" -- and then

Re: [PATCH 0/3] coredump: fix the ancient signal problems

On Sun, Feb 17, 2013 at 11:18 AM, Oleg Nesterov wrote: > > Linus, et al, could you please ack/nack the intent? Of course I will > appreciate if you can review the code, but what I am actually worried > about is the user-visible change: the coredumping becomes killable but > only by the _explicit_

Re: [PATCH 00/15] Secure boot policy support

On lun., 2013-01-28 at 11:42 -0500, Matthew Garrett wrote: > Secure boot makes it possible to ensure that the on-disk representation of > the kernel hasn't been modified. This can be sidestepped if the in-memory > representation can be trivially altered. We currently have a large number > of

[PATCH 1/3] coredump: only SIGKILL should interrupt the coredumping task

There are 2 well known and ancient problems with coredump/signals, and a lot of related bug reports: - do_coredump() clears TIF_SIGPENDING but of course this can't help if, say, SIGCHLD comes after that. In this case the coredump can fail unexpectedly. See for example

[PATCH 2/3] coredump: ensure that SIGKILL always kills the dumping thread

prepare_signal() blesses SIGKILL sent to the dumping process but this signal can be "lost" anyway. The problems is, complete_signal() sees SIGNAL_GROUP_EXIT and skips the "kill them all" logic. And even if the dumping process is single-threaded (so the target is always "correct"), the group-wide

[PATCH 3/3] coredump: sanitize the setting of signal->group_exit_code

Now that the coredumping process can be SIGKILL'ed, the setting of ->group_exit_code in do_coredump() can race with complete_signal() and SIGKILL or 0x80 can be "lost", or wait(status) can report status == SIGKILL | 0x80. But the main problem is that it is not clear to me what should we do if

[PATCH 0/3] coredump: fix the ancient signal problems

Hello. These problems are really annoying. I reported and tried to fix them in 2008 (see http://marc.info/?l=linux-kernel=121665710711931) but nobody was interested. Since then I had a lot of (to some degree contradictory) bug reports: we do not want the interrupted coredumps (this is what the

Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts

On 02/17/2013 10:51 AM, KY Srinivasan wrote: No one can base their tree on linux-next, so no. Please wait for them to get into Linus's tree. Or send them to me now, with the instructions to apply them after 3.9-rc1, and I will save them for that point in time. Thanks Greg. Will do. As I

RE: [PATCH RFC] video: Add Hyper-V Synthetic Video Frame Buffer Driver

> From: Olaf Hering > Sent: Sunday, February 17, 2013 9:32 AM > To: Haiyang Zhang > Cc: florianschandi...@gmx.de; linux-fb...@vger.kernel.org; KY Srinivasan; > jasow...@redhat.com; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org > Subject: Re: [PATCH RFC] video: Add Hyper-V

Re: Linux 3.7.9

diff --git a/Makefile b/Makefile index ad48987..5634228 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 7 -SUBLEVEL = 8 +SUBLEVEL = 9 EXTRAVERSION = NAME = Terrified Chipmunk diff --git a/arch/s390/kernel/time.c b/arch/s390/kernel/time.c index b5d8a18..252c7e6

Linux 3.7.9

I'm announcing the release of the 3.7.9 kernel. All users of the 3.7 kernel series must upgrade. The updated 3.7.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.7.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 3.4.32

diff --git a/Makefile b/Makefile index 930db76..ece8970 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 4 -SUBLEVEL = 31 +SUBLEVEL = 32 EXTRAVERSION = NAME = Saber-toothed Squirrel diff --git a/arch/s390/kernel/time.c b/arch/s390/kernel/time.c index

Re: Linux 3.0.65

diff --git a/Makefile b/Makefile index 1a4a8cd..cdba5c1 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 0 -SUBLEVEL = 64 +SUBLEVEL = 65 EXTRAVERSION = NAME = Sneaky Weasel diff --git a/arch/x86/include/asm/pgtable.h b/arch/x86/include/asm/pgtable.h index

Linux 3.4.32

I'm announcing the release of the 3.4.32 kernel. All users of the 3.4 kernel series must upgrade. The updated 3.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.4.y and can be browsed at the normal kernel.org git web browser:

Linux 3.0.65

I'm announcing the release of the 3.0.65 kernel. All users of the 3.0 kernel series must upgrade. The updated 3.0.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.0.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH] ADP1653 board code for Nokia RX-51

Hi, On Sun, Feb 17, 2013 at 04:16:49PM +0100, Pali Rohár wrote: > I'm sending ADP1653 flash torch board code for Nokia RX-51. Kernel > driver ADP1653 is already in upstream kernel. Board code was extracted > from this big camera meego patch: > >

[PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts

Use the infrastructure for delivering VMBUS interrupts using a special vector. With this patch, we can now properly handle the VMBUS interrupts that can be delivered on any CPU. Also, turn on interrupt load balancing as well. This patch requires the infrastructure that was implemented in the

Re: [PATCH 3/3] posix timers: Add syscall that works on timer sigevent

On 02/17/2013 05:42 PM, Jann Horn wrote: > On Thu, Feb 14, 2013 at 08:19:45PM +0400, Pavel Emelyanov wrote: >> +struct sigevent event; > [...] >> +event.sigev_notify = timer->it_sigev_notify; >> +event.sigev_signo = timer->sigq->info.si_signo; >> +event.sigev_value =

RE: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Sunday, February 17, 2013 1:25 PM > To: KY Srinivasan > Cc: H. Peter Anvin; x...@kernel.org; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com; >

Re: [stable request] fix stack overflow in __reserve_region_with_split

On Mon, 2013-02-11 at 17:26 +0100, Jiri Slaby wrote: > Hi, > > I think this one should go to stable: > commit 4965f5667f36a95b41cda6638875bc992bd7d18b > Author: T Makphaibulchoke > Date: Thu Oct 4 17:16:55 2012 -0700 > > kernel/resource.c: fix stack overflow in

Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts

On Sun, Feb 17, 2013 at 06:13:49PM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Wednesday, February 13, 2013 1:53 PM > > To: H. Peter Anvin > > Cc: KY Srinivasan; x...@kernel.org; linux-kernel@vger.kernel.org; > >

Re: Driver lis3lv02d_i2c not working on Nokia RX-51

On Sun, Feb 17, 2013 at 05:40:41PM +0100, Pali Rohár wrote: > $ dmesg | grep lis3 > [ 110.454345] lis3lv02d_i2c 3-001d: Failed to get supply 'Vdd': -517 > [ 110.457397] i2c 3-001d: Driver lis3lv02d_i2c requests probe deferral > [ 111.507415] lis3lv02d_i2c 3-001d: Failed to get supply 'Vdd':

Re: Debugging Thinkpad T430s occasional suspend failure.

2013/2/17 Linus Torvalds : > On Sun, Feb 17, 2013 at 7:11 AM, Frederic Weisbecker > wrote: >> >> preempt_value_in_interrupt() looks buggy in your patch: it makes >> invoke_softirq() returning if (val & HARDIRQ_MASK). But that's always >> true since you have moved further the

RE: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Wednesday, February 13, 2013 1:53 PM > To: H. Peter Anvin > Cc: KY Srinivasan; x...@kernel.org; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com; >

[PATCH 2/9] video: sysfb: new vbefb device type

From: David Herrmann This adds the VESA BIOS Extension (VBE) device type. Platform code needs to provide the "vbefb" platform-device with a screen_info structure as platform code. All drivers that depend on VBE can now register as bus drivers and bind to SYSFB_VBE devices. There is no

[PATCH 0/9] System Framebuffer Bus (sysfb)

Hi This series tries to fix the mess with global system framebuffer access in device drivers. Currently, architecture initialization sets the "screen_info" object according to the system framebuffer that was detected during boot. The device driver that can map VMEM first gets access to it. There

[PATCH 3/9] video: sysfb: always provide vbefb device

From: David Herrmann HACK: This should be provided by architecture setup code. But to show how it is supposed to work, we now simply add a "vbefb" device during initialization. The better way to do this is by moving this into arch-code. So for instance the x86 boot initialization should create

[PATCH 5/9] video: vesafb: use sysfb bus

Instead of using our own platform device, we now register as sysfb driver and get notified whenever we are loaded on a system VBE device. This allows other VBE drivers to be loaded at the same time and users can bind/unbind drivers via sysfs. We also no longer need to fake a platform-device

[PATCH 9/9] drm: dvbe: add optional fbdev frontend

This adds a new fbdev frontend to the dvbe driver. It allows userspace to access the dvbe driver via an fbdev frontend. It is disabled by default so you can use dvbe without CONFIG_FB. It should only be used for backwards-compatibility. Use the DRM dumb API to access dvbe buffers properly.

[PATCH 8/9] drm: dvbe: implement VBE/VESA blitting backend

Extend the dvbe core driver by a VESA/VBE backend that simply blits the data from a framebuffer into the hardware framebuffer on damage. Modesetting has to be done during the boot-process by the architecture code (same way as vesafb requires it). No runtime modesetting is allowed due to

[PATCH 7/9] drm: new VESA BIOS Extension DRM driver stub

This driver uses the VESA BIOS Extensions to control the display device. Modesetting has to be done during the boot-process by the architecture code (same way as vesafb requires it). No runtime modesetting is allowed due to RealMode/ProtectedMode restrictions. This patch only introduces the stub

[PATCH 6/9] drm: new sysfb DRM bus module

This provides a new DRM bus helper for the system framebuffer bus. It is very similar in its functionality to the DRM_USB helper. It allows to write DRM drivers that register as SYSFB drivers to the system. Signed-off-by: David Herrmann --- drivers/gpu/drm/Kconfig | 5 ++

[PATCH 1/9] video: introduce system framebuffer bus

From: David Herrmann For a long time now we have the problem that there are multiple drivers available that try to use system framebuffers (like EFI, VESA/VBE, ...). There is no way to control which driver gets access to the devices, but instead works on a first-come-first-serve basis.

[PATCH 4/9] video: vesafb: allow building as module

From: David Herrmann Fix the vesafb module to no longer use any static __init data. Also add a module_exit() function that destroys the platform device. Note that fbdev hotplugging is broken and the self-reference actually prevents sane module-unloading. Anyway, this at least allows delayed

[PATCH 1/2] hid: Add report descriptor for Logitech Driving Force wheel

This is the original report descriptor as reported by lsusb -vd 046d:c294. Signed-off-by: Paul Sbarra --- drivers/hid/hid-lg.c | 101 --- 1 file changed, 96 insertions(+), 5 deletions(-) diff --git a/drivers/hid/hid-lg.c b/drivers/hid/hid-lg.c

[PATCH 2/2] hid: Split accel, brake for Logitech Driving Force wheel

Signed-off-by: Paul Sbarra --- drivers/hid/hid-lg.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/hid/hid-lg.c b/drivers/hid/hid-lg.c index 6daa192..6bb7f05 100644 --- a/drivers/hid/hid-lg.c +++ b/drivers/hid/hid-lg.c @@ -81,7 +81,6 @@ static __u8

BUG in find_pid_ns

Hi all, While fuzzing with trinity inside a KVM tools guest, running latest -next kernel, I've stumbled on the following spew: [ 400.345287] BUG: unable to handle kernel paging request at fff0 [ 400.346614] IP: [] find_pid_ns+0x110/0x1f0 [ 400.347649] PGD 5429067 PUD 542b067 PMD

Re: Debugging Thinkpad T430s occasional suspend failure.

On Sun, Feb 17, 2013 at 7:11 AM, Frederic Weisbecker wrote: > > preempt_value_in_interrupt() looks buggy in your patch: it makes > invoke_softirq() returning if (val & HARDIRQ_MASK). But that's always > true since you have moved further the sub_preempt_count(IRQ_EXIT) > further. No, that's not

Re: Debugging Thinkpad T430s occasional suspend failure.

On Sun, Feb 17, 2013 at 5:31 PM, Hugh Dickins wrote: > On Sun, 17 Feb 2013, Daniel Vetter wrote: >> On Sun, Feb 17, 2013 at 3:21 AM, Hugh Dickins wrote: >> > On Sat, 16 Feb 2013, Hugh Dickins wrote: >> >> On Sat, 16 Feb 2013, Linus Torvalds wrote: >> >> > >> >> > I think it's worth it to give

Re: [PATCH] sound: usb/quirks, fix out-of-bounds access

At Sun, 17 Feb 2013 14:33:04 +0100, Jiri Slaby wrote: > > bootresponse in snd_usb_mbox2_boot_quirk is only 12 (decimal) u8's > long, but i9s passed to snd_usb_ctl_msg as it would be 0x12 (hexa) > long. Fix that by having proper size of the array, i.e. 0x12. > > Signed-off-by: Jiri Slaby > Cc:

Re: 3.7 HDMI channel map regression

On Sun, Feb 17, 2013 at 09:34:53AM +0100, Takashi Iwai wrote: > At Sat, 16 Feb 2013 18:22:25 -0600, > Shawn Bohrer wrote: > > > > On Mon, Jan 28, 2013 at 08:52:05PM -0600, Shawn Bohrer wrote: > > > On Mon, Jan 28, 2013 at 09:56:33AM +0100, Takashi Iwai wrote: > > > > At Sun, 27 Jan 2013 19:18:27

Re: Driver lis3lv02d_i2c not working on Nokia RX-51

On Sunday 17 February 2013 17:25:24 Mark Brown wrote: > On Sun, Feb 17, 2013 at 12:46:25AM +0100, Pali Rohár wrote: > > Accelerometer driver lis3lv02d_i2c not working on Nokia > > RX-51 with linux kernel 3.8-rc3. Probing for i2c device > > failing. > > > > I tried to compile older version and it

Re: Debugging Thinkpad T430s occasional suspend failure.

On Sun, 17 Feb 2013, Daniel Vetter wrote: > On Sun, Feb 17, 2013 at 3:21 AM, Hugh Dickins wrote: > > On Sat, 16 Feb 2013, Hugh Dickins wrote: > >> On Sat, 16 Feb 2013, Linus Torvalds wrote: > >> > > >> > I think it's worth it to give them a heads-up already. So I've cc'd > >> > the main suspects

Re: Driver lis3lv02d_i2c not working on Nokia RX-51

On Sun, Feb 17, 2013 at 12:46:25AM +0100, Pali Rohár wrote: > Accelerometer driver lis3lv02d_i2c not working on Nokia RX-51 > with linux kernel 3.8-rc3. Probing for i2c device failing. > I tried to compile older version and it working without problem. > Then I bisected commit which broke

Re: regmap: Question about devices with unequal register sizes

On Sat, Feb 16, 2013 at 06:03:51PM +0100, Daniel Mack wrote: > The register layout is described on page 26, and they call their > registers 'subaddresses'. Up to sub-address 0x1c, I see no problem > mapping that to a simple 8-bit regmap layout, but above that, access > gets trickier because

slab: odd BUG on kzalloc

Hi all, I was fuzzing with trinity inside a KVM tools guest, running latest -next kernel, and hit the following bug: [ 169.773688] BUG: unable to handle kernel NULL pointer dereference at 0001 [ 169.774976] IP: [] memset+0x1f/0xb0 [ 169.775989] PGD 93e02067 PUD ac1a2067 PMD 0 [

Re: BUG at net/sunrpc/svc_xprt.c:921 (another one)

On Fri, Feb 15, 2013 at 08:33:14PM +0100, Paweł Sikora wrote: > On Tuesday 12 of February 2013 15:52:17 J. Bruce Fields wrote: > > On Sun, Jan 20, 2013 at 05:51:12PM -0500, Mark Lord wrote: > > > Got it again, this time on a different system > > > running mostly the same software. > > > > Mark,

Re: [PATCH 02/11] ARM: samsung: fix assembly syntax for new gas

On Sunday 17 February 2013, Mikael Pettersson wrote: > Russell King - ARM Linux writes: > > On Thu, Feb 14, 2013 at 02:49:18PM +0100, Arnd Bergmann wrote: > > > Recent assembler versions complain about extraneous > > > whitespace inside [] brackets. This fixes all of > > > these instances for

Re: fb: mmp: include linux/platform_device.h

On Fri, Feb 15, 2013 at 10:16 PM, Arnd Bergmann wrote: > Patch 16559ae "kgdb: remove #include from kgdb.h" > changes the kgdb.h file so that drivers including it do not implicitly > include linux/platform_device.h. The mmp framebuffer driver is new, > so Greg did not have a chance to fix it up

Re: thermal governor: does it actually work??

Hi, Borislav Petkov writes: On Sun, Feb 17, 2013 at 03:43:13AM +0100, Peter Feuerer wrote: From 7b39bd8837de6dc5658ac3e54ac5d4df9d351528 Mon Sep 17 00:00:00 2001 From: Peter Feuerer Date: Sun, 17 Feb 2013 03:29:19 +0100 Subject: [PATCH] added two more trip points to acerhdf, this allows

Re: [PATCH 02/11] ARM: samsung: fix assembly syntax for new gas

Russell King - ARM Linux writes: > On Thu, Feb 14, 2013 at 02:49:18PM +0100, Arnd Bergmann wrote: > > Recent assembler versions complain about extraneous > > whitespace inside [] brackets. This fixes all of > > these instances for the samsung platforms. We should > > backport this to all

Re: [PATCH 02/11] ARM: samsung: fix assembly syntax for new gas

On Sunday 17 February 2013, Aaro Koskinen wrote: > Hi, > > On Thu, Feb 14, 2013 at 02:49:18PM +0100, Arnd Bergmann wrote: > > Recent assembler versions complain about extraneous > > whitespace inside [] brackets. This fixes all of > > these instances for the samsung platforms. We should > >

Re: shouldn't a non-privileged malformed sprintf crashes the kernel

On Sunday 17 February 2013, Toralf Förster wrote: >This is the 2nd time in a row that a stable kernel (3.7.8 currently) >crashes in such a way that even the sys-rq key doesn't work any longer. >Found nothing in the log. The screen shot is here [1]. First time this >issue was reported in [2]. >

[PATCH 5/7] ACPI / hotplug: Introduce user space interface for hotplug profiles

From: Rafael J. Wysocki Introduce user space interface for manipulating hotplug profiles associated with ACPI scan handlers. The interface consists of sysfs directories under /sys/firmware/acpi/hotplug/, one for each hotplug profile, containing attributes allowing user space to manipulate the

[PATCH 4/7] ACPI / scan: Introduce acpi_scan_handler_matching()

From: Rafael J. Wysocki Introduce new helper routine acpi_scan_handler_matching() for checking if the given ACPI scan handler matches a given device ID and rework acpi_scan_match_handler() to use the new routine (that routine will also be useful for other purposes in the future). Signed-off-by:

[PATCH 3/7] ACPI / container: Use common hotplug code

From: Rafael J. Wysocki Switch the ACPI container driver to using common device hotplug code introduced previously. This reduces the driver down to a trivial definition and registration of a struct acpi_scan_handler object. Signed-off-by: Rafael J. Wysocki --- drivers/acpi/container.c | 146

[PATCH 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug

From: Rafael J. Wysocki Multiple drivers handling hotplug-capable ACPI device nodes install notify handlers covering the same types of events in a very similar way. Moreover, those handlers are installed in separate namespace walks, although that really should be done during namespace scans

[PATCH 7/7] ACPI / scan: Make memory hotplug driver use struct acpi_scan_handler

From: Rafael J. Wysocki Make the ACPI memory hotplug driver use struct acpi_scan_handler for representing the object used to set up ACPI memory hotplug functionality and to remove hotplug memory ranges and data structures used by the driver before unregistering ACPI device nodes representing

[PATCH 1/7] ACPI / scan: Introduce acpi_scan_match_handler()

From: Rafael J. Wysocki Introduce helper routine acpi_scan_match_handler() that will find the ACPI scan handler matching a given device ID, if there is one, and rework acpi_scan_attach_handler() to use the new routine (that routine will also be useful for other purposes going forward).

[PATCH 6/7] ACPI / container: Use hotplug profile user space interface

From: Rafael J. Wysocki Make the ACPI container driver register its ACPI scan handler object using acpi_scan_add_handler_with_hotplug() to allow user space to manipulate its hotplug profile attributes. Signed-off-by: Rafael J. Wysocki --- drivers/acpi/container.c |4 ++-- 1 file changed,

[PATCH 0/7] ACPI / hotplug: Common code for ACPI-based hotplug

Hi All, The following patches introduce common code for ACPI-based hotplug for non-PCI devices and modify the container and memory hotplug ACPI drivers to use the new code. This is based on linux-pm.git/master and regarded as v3.10 material. [1/7] Introduce acpi_scan_match_handler() that will

[PATCH] ADP1653 board code for Nokia RX-51

Hello, I'm sending ADP1653 flash torch board code for Nokia RX-51. Kernel driver ADP1653 is already in upstream kernel. Board code was extracted from this big camera meego patch:

Re: Debugging Thinkpad T430s occasional suspend failure.

2013/2/15 Linus Torvalds : > On Fri, Feb 15, 2013 at 9:44 AM, Paul E. McKenney > wrote: >> >> This commit was designed to increase the probability of hitting the >> races described in http://lwn.net/Articles/453002/. These races result >> in deadlocks involving the runqueue lock (and perhaps

Re: [PATCH] dma: tegra: assume CONFIG_OF

On Fri, Feb 15, 2013 at 02:18:59PM -0800, Dan Williams wrote: > On Fri, Feb 15, 2013 at 1:53 PM, Stephen Warren wrote: > > From: Stephen Warren > > > > Tegra only supports, and always enables, device tree. Remove all ifdefs > > and runtime checks for DT support from the driver. > > > >

Re: Stupid user with user-space questions, matrix LED driving with user space code only.

On Sun, 2013-02-17 at 14:37 +, Jonathan Andrews wrote: > > > The dim pixel code is timing critical (but as I said only a tiny > > > fraction of the total CPU usage). What I need to do is grab the CPU and > > > prevent any context switch (IRQ or PREEMPT) for this period. > > why you want to do

[PATCH] perf: check if -DFORTIFY_SOURCE=2 is allowed

It seems gcc (4.7.2) defines _FORTIFY_SOURCE internally and becomes confused when it sees another definition in flags. For me, build failed like this: CHK glibc Makefile:548: *** No gnu/libc-version.h found, please install glibc-dev[el]/glibc-static. Stop. and only with V=1 it printed: :0:0:

Re: [PATCH] pwm: twl: Fix typo that broke build

On Sun, Feb 17, 2013 at 11:26:30AM +0100, Thierry Reding wrote: > On Sun, Feb 17, 2013 at 11:08:13AM +0100, Johannes Thumshirn wrote: > > Fix a little type that unfortunately broke the build :-( > > Signed-off-by: Johannes Thumshirn > > --- > > drivers/pwm/pwm-twl.c | 2 +- > > 1 file changed, 1

Re: Debugging Thinkpad T430s occasional suspend failure.

On Sun, Feb 17, 2013 at 2:38 PM, Daniel Vetter wrote: > 2. The new i915 force restore code is indeed missing a safety check > compared to the old crtc helper based one: > > diff --git a/drivers/gpu/drm/i915/intel_display.c > b/drivers/gpu/drm/i915/intel_display.c > index 6eb3882..095094c 100644

Re: [PATCH] ethernet: neterion: vxge: vxge-traffic.c: fix for a potential NULL pointer dereference

Am 16.02.2013 18:56, schrieb Kumar Amit Mehta: > fix for a potential NULL pointer dereference and removal of a redundant > assignment operation. Found using smatch. > > Signed-off-by: Kumar Amit Mehta > --- > drivers/net/ethernet/neterion/vxge/vxge-traffic.c |8 ++-- > 1 file changed,

Re: Stupid user with user-space questions, matrix LED driving with user space code only.

> > The dim pixel code is timing critical (but as I said only a tiny > > fraction of the total CPU usage). What I need to do is grab the CPU and > > prevent any context switch (IRQ or PREEMPT) for this period. > why you want to do this? Because I need an I/O pin to change state for a short

Re: [PATCH RFC] video: Add Hyper-V Synthetic Video Frame Buffer Driver

On Fri, Feb 15, Haiyang Zhang wrote: > +config HYPERV_FB This should probably be FB_HYPERB to follow the naming of all other drivers. Olaf -- 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

Re: [PATCH v2 1/1] OMAP4: DSS: Add panel for Blaze Tablet boards

> >> + char name[30]; > >> + char buf[50]; > >> + > >> + if (size >= sizeof(buf)) > >> + size = sizeof(buf); > > > > what's the point of this? > > This is a way to limit copied from userspace data by available buffer size, > widely used in current kernel sources. Are you

Re: thermal governor: does it actually work??

On Sun, Feb 17, 2013 at 03:43:13AM +0100, Peter Feuerer wrote: > Hi Boris, Alex, Andreas, > > what do you think about this acerhdf patch? > I think it makes things straight and implements the two-point regulation of > acerhdf to be for correctly handled by the thermal layer: > > > From

<    1   2   3   4   5   6   7   >