On Tue, Jul 31, 2012 at 03:45:41PM +0100, Lee Jones wrote:
> If codec->control_data is not populated SoC Core assumes we want to
> use regmap, which fails catastrophically, as we don't have one:
Applied. If you could do resends at a rate somewhat lower than once per
working day that'd be helpful,
On Tue, Jul 31, 2012 at 04:32:35PM +0200, Thierry Reding wrote:
> On Tue, Jul 31, 2012 at 03:26:07PM +0100, Mark Brown wrote:
> > This is framework code - it doesn't have much option. Disabling HOTPLUG
> > is totally reasonable on space constrained systems, there's no reason
> > for the code to b
On Fri, Jul 27, 2012 at 01:18:36PM -0500, Seth Jennings wrote:
> This patchset creates a new driver class under drivers/ for
> memory management related drivers, like zcache.
I was going back and forth with Dan whether it should be in mm/
or in drivers/mm.
>
> This driver class would be for drive
On Tue, Jul 31, 2012 at 10:21:56AM +0800, Axel Lin wrote:
> 於 一,2012-07-30 於 16:33 +0100,Mark Brown 提到:
> > On Mon, Jul 30, 2012 at 07:47:13AM +0800, Axel Lin wrote:
> > > _notifier_call_chain(rdev, REGULATOR_EVENT_VOLTAGE_CHANGE,
> > > - (void *)best_val);
>
On 07/26/2012 02:50 AM, Colin Cross wrote:
> The cpu hotplug notifier gets called in both atomic and non-atomic
> contexts, it is not always safe to lock a mutex. Filter out all events
> except the six necessary ones, which are all sleepable, before taking
> the mutex.
>
> Signed-off-by: Colin Cr
On Tue, 2012-07-31 at 08:18 -0700, Paul E. McKenney wrote:
> On Tue, Jul 31, 2012 at 10:56:23AM -0400, Steven Rostedt wrote:
> > On Tue, 2012-07-31 at 10:51 -0400, Steven Rostedt wrote:
> >
> > > > OK, I will bite. How about using something like RCU_NONIDLE(), either
> > > > directly or open-code
On Sun, Jul 29, 2012 at 10:54:28AM +0900, Minchan Kim wrote:
> On Fri, Jul 27, 2012 at 02:42:14PM -0700, Dan Magenheimer wrote:
> > > From: Konrad Rzeszutek Wilk [mailto:kon...@darnok.org]
> > > Sent: Friday, July 27, 2012 3:00 PM
> > > Subject: Re: [PATCH 0/4] promote zcache from staging
> > >
>
On 07/31/2012 04:36 PM, me...@codeaurora.org wrote:
> Hi Jens,
>
> Do you have comments on this patch?
> Can we push it to kernel 3.6 version?
I have questions - what is this good for? In other words, explain to me
why this is useful code. And in particular why this cannot be done from
userspace
On 31 July 2012 19:24, Damien Cassou wrote:
> From: Damien Cassou
>
> The various devm_ functions allocate memory that is released when a driver
> detaches. This patch uses these functions for data that is allocated in
> the probe function of a platform device and is only freed in the remove
> f
On 07/31/2012 03:42 AM, Konrad Rzeszutek Wilk wrote:
[PATCH 3/3] x86: Let extend_brk return a NULL pointer instead of
makes extend_brk not do BUG_ON and instead just return NULL. This allows
us to handle the bootup issues more gracefully.
NAK. The whole point of the brk allocator is that
Hi Shea,
> Please CC me on response, I am not subscribed to the list.
>
> hcitool is unable to detect my laptop's bluetooth device:
>
> $ lsusb
> Bus 004 Device 009: ID 05ac:821d Apple, Inc.
> Bus 004 Device 008: ID 05ac:820b Apple, Inc.
> Bus 004 Device 007: ID 05ac:820a Apple, Inc.
> Bus 004 D
The whole patch is incorrect because of:
On Tue, Jul 31, 2012 at 5:47 PM, Sachin Kamat wrote:
>> - ret = request_irq(par->irq, lcdc_irq_handler, 0,
>> - DRIVER_NAME, par);
>> + ret = devm_request_irq(&device->dev, par->irq, lcdc_irq_handler, 0,
>> +
On Tue, Jul 31, 2012 at 9:45 AM, Bjorn Helgaas wrote:
> On Mon, Jul 30, 2012 at 12:15 PM, Jon Mason wrote:
>>
>> I've tried to make it all generic enough that non-Intel NTBs should plug in
>> with
>> minimal changes to ntb_hw.c. If their design is too divergent, then a slight
>> redesign of ntb
On 07/31/2012 11:52 AM, Marcel Holtmann wrote:
Hi Shea,
Please CC me on response, I am not subscribed to the list.
hcitool is unable to detect my laptop's bluetooth device:
$ lsusb
Bus 004 Device 009: ID 05ac:821d Apple, Inc.
Bus 004 Device 008: ID 05ac:820b Apple, Inc.
Bus 004 Device 007: ID
於 二,2012-07-31 於 16:41 +0100,Mark Brown 提到:
> On Tue, Jul 31, 2012 at 10:21:56AM +0800, Axel Lin wrote:
> > 於 一,2012-07-30 於 16:33 +0100,Mark Brown 提到:
> > > On Mon, Jul 30, 2012 at 07:47:13AM +0800, Axel Lin wrote:
>
> > > > _notifier_call_chain(rdev,
> > > > REGULATOR_EVENT_VOLT
On Mon, Jul 30, 2012 at 01:48:29PM -0700, Dan Magenheimer wrote:
> > From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> > Subject: Re: [PATCH 0/4] promote zcache from staging
> >
> > Dan,
> >
> > I started writing inline responses to each concern but that
> > was adding more confusion tha
On Tue, Jul 31, 2012 at 05:43:45AM +0100, Ben Hutchings wrote:
> 3.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Liam Girdwood
>
> commit 01005a729a17ab419f61a366e22f3419e7a2c3fe upstream.
>
> Codec shutdown performs a DAPM power seq
On Tue, 2012-07-31 at 13:46 +0200, javier Martin wrote:
> On 31 July 2012 13:38, Fabio Estevam wrote:
> > On Tue, Jul 31, 2012 at 3:46 AM, Vinod Koul
> > wrote:
> >
> >> This patch will appear in 3.7-rc2 when I send the fixes to Linus post
> >> rc1, I guess early next week.
> >
> > I guess you
On Tue, Jul 31, 2012 at 01:11:01PM -0300, Herton Ronaldo Krzesinski wrote:
> Hi, this doesn't build on 3.2:
> linux-stable/sound/soc/soc-dapm.c: In function 'soc_dapm_shutdown_codec':
> linux-stable/sound/soc/soc-dapm.c:2982:18: error: 'struct snd_soc_card' has
> no member named 'dapm_mutex'
> l
On Sun, Jul 29, 2012 at 8:26 PM, Jon Mason wrote:
> +static void ntb_tx_copy_task(struct ntb_transport_qp *qp,
> +struct ntb_queue_entry *entry,
> +void *offset)
> +{
> + struct ntb_payload_header *hdr = offset;
> +
> + offset
Hi Shea,
> > include /sys/kernel/debug/usb/devices details for this device.
>
> Not sure, which device it is, so here's all of bus 4:
> T: Bus=04 Lev=04 Prnt=04 Port=02 Cnt=03 Dev#= 9 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=05ac ProdID=821
On Tue, Jul 31, 2012 at 3:57 PM, Mike Frysinger wrote:
> On Tue, Jul 31, 2012 at 9:54 AM, Damien Cassou wrote:
>> The various devm_ functions allocate memory that is released when a driver
>> detaches. This patch uses these functions for data that is allocated in
>> the probe function of a platf
On Tue, Jul 31, 2012 at 11:58:43AM -0400, Konrad Rzeszutek Wilk wrote:
> So in my head I feel that it is Ok to:
> 1) address the concerns that zcache has before it is unstaged
> 2) rip out the two-engine system with a one-engine system
>(and see how well it behaves)
> 3) sysfs->debugfs as neede
On Tue, Jul 31, 2012 at 04:39:41PM +0100, Mark Brown wrote:
> On Tue, Jul 31, 2012 at 04:32:35PM +0200, Thierry Reding wrote:
> > On Tue, Jul 31, 2012 at 03:26:07PM +0100, Mark Brown wrote:
>
> > > This is framework code - it doesn't have much option. Disabling HOTPLUG
> > > is totally reasonable
On 07/31/2012 12:12 PM, Marcel Holtmann wrote:
Hi Shea,
include /sys/kernel/debug/usb/devices details for this device.
Not sure, which device it is, so here's all of bus 4:
T: Bus=04 Lev=04 Prnt=04 Port=02 Cnt=03 Dev#= 9 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64
On Tue, Jul 31, 2012 at 7:15 AM, Heiko Carstens
wrote:
> From: Heiko Carstens
>
> The LO_ARG define needs to consider endianness also for 32 bit builds.
>
> The "bpf_fancy" test case didn't work on s390 in 32 bit and compat mode
> because the LO_ARG define resulted in a BPF program which read the
On Tue, Jul 31, 2012 at 09:19:54AM -0700, Greg Kroah-Hartman wrote:
> On Tue, Jul 31, 2012 at 04:39:41PM +0100, Mark Brown wrote:
> > On Tue, Jul 31, 2012 at 04:32:35PM +0200, Thierry Reding wrote:
> > > can gracefully handle its platform data being discarded.
> > Sure there is - take a copy of t
On Tue, Jul 31, 2012 at 08:49:21AM -0700, H. Peter Anvin wrote:
> On 07/31/2012 03:42 AM, Konrad Rzeszutek Wilk wrote:
> >
> > [PATCH 3/3] x86: Let extend_brk return a NULL pointer instead of
> >
> >makes extend_brk not do BUG_ON and instead just return NULL. This allows
> >us to handle the bootup
On Mon, 2012-07-30 at 21:33 -0700, H. Peter Anvin wrote:
> I'm wondering if we shouldn't just kill the affected CPUID bits if osxsave is
> off...
Yes, I considered clearing AVX bit (and any future xsave feature bits)
as part of the parsing "noxsave" parameter in x86_xsave_setup().
But thought ch
On Wed, Jul 25, 2012 at 06:38:11PM +0400, Glauber Costa wrote:
> Hi,
>
> This is the slab part of the kmem limitation mechanism in its last form. I
> would like to have comments on it to see if we can agree in its form. I
> consider it mature, since it doesn't change much in essence over the last
On Tue, Jul 31, 2012 at 3:41 AM, Konstantin Khlebnikov
wrote:
>
> This patchset kills some VM_* flags in vma->vm_flags,
> as result there appears five free bits.
All of these patches make sense and look good to me. I assume I'll get
this through Andrew for 3.7?
Andrew, you can consider them all
On Tue, Jul 31, 2012 at 11:35:33AM +0800, Jianbin Kang wrote:
> > I've tried to make it all generic enough that non-Intel NTBs should plug in
> > with
> > minimal changes to ntb_hw.c. If their design is too divergent, then a
> > slight
> > redesign of ntb_hw.c might be necessary. But from what
On 07/31/2012 04:32 AM, Alex Courbot wrote:
> On 07/31/2012 07:45 AM, Stephen Warren wrote:
...
>> If the nodes have a unit address (i.e. end in "@n"), which they will
>> have to if all named "step" and there's more than one of them, then they
>> will need a matching reg property. Equally, the pare
On 07/31/2012 04:31 AM, Josh Boyer wrote:
These should be CC'd to stable, right? CAI hit this with a 3.5-rcX
kernel, and the hrtimer stuff was backported to 3.4 and before I
thought.
Yes. But I'm just looking for feedback on the approach for now, this
isn't for submission yet.
thanks
-john
From: Damien Cassou
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Damien Cassou
---
drivers/vi
These patches introduce devm_ functions in some video drivers.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.
From: Damien Cassou
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Damien Cassou
---
drivers/vi
From: Damien Cassou
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Damien Cassou
---
drivers/vi
From: Damien Cassou
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Damien Cassou
---
drivers/vi
From: Damien Cassou
The various devm_ functions allocate memory that is released when a driver
detaches. This patch uses these functions for data that is allocated in
the probe function of a platform device and is only freed in the remove
function.
Signed-off-by: Damien Cassou
---
drivers/vi
>>> On 31.07.12 at 18:15, Konrad Rzeszutek Wilk wrote:
> On Tue, Jul 31, 2012 at 08:49:21AM -0700, H. Peter Anvin wrote:
>> This means you're either abusing the brk allocator to do something
>> it is not meant to do... which may mean you can a failure in *other*
>> code, or you have a bug in your
On Tue, Jul 31, 2012 at 05:43:16AM +0100, Ben Hutchings wrote:
> 3.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Mel Gorman
>
> commit a6bc32b899223a877f595ef9ddc1e89ead5072b8 upstream.
We need also to pick recent fix dc32f63453f56d0
On 07/31/2012 08:30 PM, Frederic Weisbecker wrote:
> On Wed, Jul 25, 2012 at 06:38:11PM +0400, Glauber Costa wrote:
>> Hi,
>>
>> This is the slab part of the kmem limitation mechanism in its last form. I
>> would like to have comments on it to see if we can agree in its form. I
>> consider it matu
On Tue, Jul 31, 2012 at 05:22:30PM +0100, Mark Brown wrote:
> On Tue, Jul 31, 2012 at 09:19:54AM -0700, Greg Kroah-Hartman wrote:
> > On Tue, Jul 31, 2012 at 04:39:41PM +0100, Mark Brown wrote:
> > > On Tue, Jul 31, 2012 at 04:32:35PM +0200, Thierry Reding wrote:
>
> > > > can gracefully handle it
On Mon, Jul 30, 2012 at 10:31:27AM -0700, Greg Kroah-Hartman wrote:
> From: Greg KH
>
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Mel Gorman
>
> commit a6bc32b899223a877f595ef9ddc1e89ead5072b8 upstream.
We need also to pick r
On 07/31/2012 09:27 AM, Suresh Siddha wrote:
On Mon, 2012-07-30 at 21:33 -0700, H. Peter Anvin wrote:
I'm wondering if we shouldn't just kill the affected CPUID bits if osxsave is
off...
Yes, I considered clearing AVX bit (and any future xsave feature bits)
as part of the parsing "noxsave" pa
Sorry for the delay, but Peter felt very strongly about the last
patch, and I wanted to give it at least a day's baking time in
linux-next before I submitted a pull request to you.
Also note that that are some minor merge conflicts. See my proposed resolution
here:
http://git.kernel.org/?p=linu
Hello.
On 07/31/2012 05:31 PM, Lee Jones wrote:
Subject doesn't parse for me...
> The platform attempts to register platform device 'snd_soc_u8500'
> which doesn't actually exist. Here we change the reference to the
> correct one 'snd_soc_mop500'.
> Signed-off-by: Lee Jones
WBR, Sergei
--
On Tue, Jul 31, 2012 at 09:42:45AM -0700, Greg Kroah-Hartman wrote:
> On Tue, Jul 31, 2012 at 05:22:30PM +0100, Mark Brown wrote:
> > Hrm? I'm not sure I understand the direct relevance here - we're
> > talking about platform data.
> The platform data was marked __devdata, and you said it could
On 12-07-26 01:02 PM, Randy Dunlap wrote:
>
> The added y/n/m are clear, but the "!FRV FRV" is confusing,
> isn't it?
>
>
Yes. But that is easily fixable.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More major
On Tue, Jul 31, 2012 at 01:42:04PM -0300, Herton Ronaldo Krzesinski wrote:
> On Tue, Jul 31, 2012 at 05:43:16AM +0100, Ben Hutchings wrote:
> > 3.2-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Mel Gorman
> >
> > commit a6bc32b8
On Tue, Jul 31, 2012 at 01:43:37PM -0300, Herton Ronaldo Krzesinski wrote:
> On Mon, Jul 30, 2012 at 10:31:27AM -0700, Greg Kroah-Hartman wrote:
> > From: Greg KH
> >
> > 3.0-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Mel Gor
On Tue, Jul 31, 2012 at 06:00:51PM +0100, Mel Gorman wrote:
> On Tue, Jul 31, 2012 at 01:42:04PM -0300, Herton Ronaldo Krzesinski wrote:
> > On Tue, Jul 31, 2012 at 05:43:16AM +0100, Ben Hutchings wrote:
> > > 3.2-stable review patch. If anyone has any objections, please let me
> > > know.
> > >
On Tue, Jul 31, 2012 at 10:02 AM, chetan loke wrote:
> On Tue, Jul 31, 2012 at 9:45 AM, Bjorn Helgaas wrote:
>> On Mon, Jul 30, 2012 at 12:15 PM, Jon Mason wrote:
>>>
>>> I've tried to make it all generic enough that non-Intel NTBs should plug in
>>> with
>>> minimal changes to ntb_hw.c. If th
On Tue, Jul 31, 2012 at 06:49:50AM +0200, Oliver Neukum wrote:
> On Monday 30 July 2012 15:34:06 Sarah Sharp wrote:
> > Hi Denis,
> >
> > Can you send me the output of `sudo dmidecode`? I'd like to see if I
> > can make a more general patch apply to the Intense-PC.
>
> As this is for shutdown, w
On Tue, Jul 31, 2012 at 10:18:56AM -0500, Seth Forshee wrote:
> On Sun, Jul 29, 2012 at 09:59:00PM +0100, Matthew Garrett wrote:
> > On Sun, Jul 29, 2012 at 09:52:51PM +0100, David Woodhouse wrote:
> > > On Sun, 2012-07-29 at 20:39 +0100, Matthew Garrett wrote:
> > > > And it looks like intel_lvds-
On Tue, Jul 31, 2012 at 11:16:00AM -0400, Dave Jones wrote:
>
> PWM Support (PWM) [N/y/?] (NEW) ?
>
> CONFIG_PWM:
>
> This enables PWM support through the generic PWM framework.
>
>
> Well that's.. enlightening.
Oh, there's one more enlightening sentence in the help:
"You only need to enable
On Tue, Jul 31, 2012 at 07:45:29AM -0600, Bjorn Helgaas wrote:
> On Mon, Jul 30, 2012 at 12:15 PM, Jon Mason wrote:
> > On Mon, Jul 30, 2012 at 10:50:13AM -0600, Bjorn Helgaas wrote:
> >> On Sun, Jul 29, 2012 at 6:26 PM, Jon Mason wrote:
> >> > A PCI-Express non-transparent bridge (NTB) is a poin
On Tue, Jul 31, 2012 at 04:05:39PM +0300, Tomi Valkeinen wrote:
> > Use cancel_delayed_work() instead of __cancel_delayed_work() and mark
> > the latter deprecated.
>
> I used __cancel_delayed_work() in drivers/video/omap2/dss/dsi.c as the
> cancel is done in an interrupt handler. Is it safe to us
On 07/31/2012 02:54 AM, James Courtier-Dutton wrote:
On 31 July 2012 07:35, John Stultz wrote:
So CAI Qian noticed recent boot trouble on a machine that had its CMOS
clock configured for the year 8200.
See: http://lkml.org/lkml/2012/7/29/188
While running with a crazy CMOS clock isn't advised,
On Tue, Jul 31, 2012 at 11:45:02AM -0400, Steven Rostedt wrote:
> On Tue, 2012-07-31 at 08:18 -0700, Paul E. McKenney wrote:
> > On Tue, Jul 31, 2012 at 10:56:23AM -0400, Steven Rostedt wrote:
> > > On Tue, 2012-07-31 at 10:51 -0400, Steven Rostedt wrote:
> > >
> > > > > OK, I will bite. How abou
On 07/31/2012 10:14 AM, Feng Tang wrote:
> In commit 99b725084 "ACPI processor hotplug: Delay acpi_processor_start()
> call for hotplugged cores", acpi_processor_hotplug(pr) was wrongly replaced
> by acpi_processor_cst_has_changed() inside the acpi_cpu_soft_notify(). This
> patch will restore it b
On 07/30/2012 12:03 PM, Mark Brown wrote:
> On Mon, Jul 30, 2012 at 11:05:08AM -0600, Stephen Warren wrote:
>> On 07/29/2012 02:38 PM, Mark Brown wrote:
>>> On Fri, Jul 27, 2012 at 01:02:56PM -0600, Stephen Warren wrote:
>
1) regmap_add_irq_chips() calls regmap_add_irq_chip() with irq==0 rath
On Tue, Jul 31, 2012 at 11:20:53AM -0600, Stephen Warren wrote:
> I agree in general, but I don't see how this is a regression in this
> change - the arizona pdata doesn't specify an IRQ base anywhere, and
> hence the IRQ base is already dynamically allocated...
> The (regmap-irq) API (in the pat
On 07/30/2012 10:26 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120730:
>
on i386:
drivers/built-in.o: In function `radio_tea5777_set_freq':
radio-tea5777.c:(.text+0x4d8704): undefined reference to `__udivdi3'
--
~Randy
--
To unsubscribe from this list: send the line "unsubs
On Tue, 2012-07-31 at 10:17 -0700, Paul E. McKenney wrote:
> rcu: Permit RCU_NONIDLE() to be used from interrupt context
>
> There is a need to use RCU from interrupt context, but either before
> rcu_irq_enter() is called or after rcu_irq_exit() is called. If the
> interrupt occurs from idle, th
On 07/30/2012 11:15 PM, Pekka Enberg wrote:
> This patch adds a comment on top of the schedule() function to explain
> to scheduler newbies how the main scheduler function is entered.
>
> Explained-by: Ingo Molnar
> Explained-by: Peter Zijlstra
> Signed-off-by: Pekka Enberg
> ---
> kernel/sch
On Tue, Jul 31, 2012 at 07:07:41PM +0200, Borislav Petkov wrote:
> On Tue, Jul 31, 2012 at 11:16:00AM -0400, Dave Jones wrote:
> >
> > PWM Support (PWM) [N/y/?] (NEW) ?
> >
> > CONFIG_PWM:
> >
> > This enables PWM support through the generic PWM framework.
> >
> >
> > Well that's.. enlightenin
On Tue, Jul 31, 2012 at 12:02:20PM -0400, chetan loke wrote:
> On Tue, Jul 31, 2012 at 9:45 AM, Bjorn Helgaas wrote:
> > On Mon, Jul 30, 2012 at 12:15 PM, Jon Mason wrote:
> >>
> >> I've tried to make it all generic enough that non-Intel NTBs should plug
> >> in with
> >> minimal changes to ntb_
On Tue, 2012-07-31 at 09:43 -0700, H. Peter Anvin wrote:
> My main reason for thinking that it would be good to clear the bits is
> that it plays a lot nicer with alternatives and with static_cpu_has().
Fair enough. Neil, can you please drop the previous patch and Peter,
please queue this for v3.
On Tue, 2012-07-31 at 16:57 +0200, Ingo Molnar wrote:
>
> 'callback', while a longer word, is almost always used as a noun
> within the kernel - and it also has a pretty narrow meaning.
An altogether different naming would be something like:
struct user_kernel_tracking {
int want_uk_tr
Now i got it working - sorry used old gdb.
This is the backtrace:
Core was generated by `/usr/bin/qemu-system-x86_64 -id 103 -chardev
socket,id=qmp,path=/var/run/qemu-s'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f6ca10faed8 in ?? () from /lib/libc.so.6
(gdb) where
#0
On Tue, Jul 31, 2012 at 05:41:51PM +0100, Jan Beulich wrote:
> >>> On 31.07.12 at 18:15, Konrad Rzeszutek Wilk
> >>> wrote:
> > On Tue, Jul 31, 2012 at 08:49:21AM -0700, H. Peter Anvin wrote:
> >> This means you're either abusing the brk allocator to do something
> >> it is not meant to do... whi
On Tue, Jul 31, 2012 at 01:26:38PM -0400, Steven Rostedt wrote:
> Then shouldn't this not have a prompt and just be selected by those
> PWM drivers below?
It gives an empty menu due to the deps of the single PWM drivers.
But the whole CONFIG_PWM thing should simply depend on !X86 so that it
doesn
Interrupt handler apds990x_irq in APDS990x sensor driver
invokes mutex_lock that is might sleep operation.
Found by Linux Driver Verification project (linuxtesting.org)
within my participation in the GSoC 2012 program.
static irqreturn_t apds990x_irq(int irq, void *data)
{
struct apds99
On Tue, Jul 31, 2012 at 01:24:57PM -0400, Steven Rostedt wrote:
> On Tue, 2012-07-31 at 10:17 -0700, Paul E. McKenney wrote:
>
> > rcu: Permit RCU_NONIDLE() to be used from interrupt context
> >
> > There is a need to use RCU from interrupt context, but either before
> > rcu_irq_enter() is called
* John Stultz wrote:
> Hey Thomas, Ingo,
> Here's updated time/jiffies patches including Ingo's
> feedback for tip/timers/core.
>
> Let me know if there's any further tweaks you'd like to see.
The code looks very nice now. I've applied them to -tip and
pushed them out.
Thanks,
On Tue, Jul 31, 2012 at 03:35:07PM +, Myklebust, Trond wrote:
> On Tue, 2012-07-31 at 16:19 +0100, Mel Gorman wrote:
> > On Tue, Jul 31, 2012 at 02:37:24PM +, Myklebust, Trond wrote:
> > > On Tue, 2012-07-31 at 11:33 +0100, Mel Gorman wrote:
> > > > On Tue, Jul 31, 2012 at 02:24:41PM +1000,
On 07/30/2012 11:35 PM, John Stultz wrote:
I've also only been able to lightly test. If you want to try this out
you can add the following to timekeeping_init after the
read_persistent_clock() call:
now.tv_sec = 19646928LL;
Prarit noted that I implemented these patches against 3.5 (w
Am 31.07.2012 16:54, schrieb Avi Kivity:
On 07/31/2012 02:59 PM, Stefan Priebe - Profihost AG wrote:
Hello list,
i hope it is correct to list the maintainers of kvm. While trying to
install ubuntu 12.04 amd64 on a kvm based vm the KVM process segfaults
while ubuntu tries to detect the HW:
kvm[2
This patch is dropped for now as cancel_delayed_work() cannot be
called from irq context as pointed out by Tomi Valkeinen. git branch
accordingly updated. I'm working on another patchset to remove the
restriction.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe li
>From 18fe17017c7de052f116ef771dc8c4088f0d1ebb Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Tue, 31 Jul 2012 10:53:21 -0700
Convert delayed_work users doing cancel_delayed_work() followed by
queue_delayed_work() to mod_delayed_work().
Most conversions are straight-forward. Ones worth mentioni
Commit-ID: b9403130a5350fca59a50ed11c198cb8c7e54119
Gitweb: http://git.kernel.org/tip/b9403130a5350fca59a50ed11c198cb8c7e54119
Author: Michael Wang
AuthorDate: Thu, 12 Jul 2012 16:10:13 +0800
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:00:16 +0200
sched/cleanups: Add load ba
Commit-ID: 7740dfc0363a70546ef25c0383aca252f95a91d2
Gitweb: http://git.kernel.org/tip/7740dfc0363a70546ef25c0383aca252f95a91d2
Author: Andrew Morton
AuthorDate: Sat, 21 Jul 2012 10:53:46 +1000
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:02:03 +0200
perf/x86/intel/uncore: Mak
Commit-ID: d07bdfd322d307789f15b427dbcc39257665356f
Gitweb: http://git.kernel.org/tip/d07bdfd322d307789f15b427dbcc39257665356f
Author: Peter Zijlstra
AuthorDate: Tue, 10 Jul 2012 09:42:15 +0200
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:02:04 +0200
perf/x86: Fix USER/KERNEL
Commit-ID: e6dab5ffab59e910ec0e3355f4a6f29f7a7be474
Gitweb: http://git.kernel.org/tip/e6dab5ffab59e910ec0e3355f4a6f29f7a7be474
Author: Andrew Vagin
AuthorDate: Wed, 11 Jul 2012 18:14:58 +0400
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:02:05 +0200
perf/trace: Add ability to
Commit-ID: a7ea3bbf5d58f4df2265d312f91d5769eabc8144
Gitweb: http://git.kernel.org/tip/a7ea3bbf5d58f4df2265d312f91d5769eabc8144
Author: Catalin Marinas
AuthorDate: Fri, 27 Jul 2012 14:48:09 -0400
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:09:12 +0200
time/jiffies: Allow CLOC
Commit-ID: 02ab20ae38337b99b5c29c81090f594b8fd61283
Gitweb: http://git.kernel.org/tip/02ab20ae38337b99b5c29c81090f594b8fd61283
Author: John Stultz
AuthorDate: Fri, 27 Jul 2012 14:48:10 -0400
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:09:12 +0200
time/jiffies: Rename ACTHZ t
Commit-ID: d4e3ab384b2343c7074f713ac330f839c38c52ee
Gitweb: http://git.kernel.org/tip/d4e3ab384b2343c7074f713ac330f839c38c52ee
Author: John Stultz
AuthorDate: Fri, 27 Jul 2012 14:48:11 -0400
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:09:13 +0200
time: Clean up stray newline
On Tue, Jul 31, 2012 at 09:19:16AM -0700, Greg Kroah-Hartman wrote:
> On Tue, Jul 31, 2012 at 11:58:43AM -0400, Konrad Rzeszutek Wilk wrote:
> > So in my head I feel that it is Ok to:
> > 1) address the concerns that zcache has before it is unstaged
> > 2) rip out the two-engine system with a one-e
Commit-ID: 6d0ef903e2bda70da124c10d8ad89f2382c87991
Gitweb: http://git.kernel.org/tip/6d0ef903e2bda70da124c10d8ad89f2382c87991
Author: John Stultz
AuthorDate: Fri, 27 Jul 2012 14:48:12 -0400
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:09:14 +0200
time: Clean up offs_real/wal
On Tue, Jul 31, 2012 at 1:27 PM, Jon Mason wrote:
>
> I don't see the benefit of having the driver in staging. Any vendors
> who would notice the ntb driver in staging would be sitting on these
> mailing lists and hopefully have planety of comments on the design.
> Stashing the driver in staging
Commit-ID: 4e250fdde9be50581c7dd5fed88c9b9960615314
Gitweb: http://git.kernel.org/tip/4e250fdde9be50581c7dd5fed88c9b9960615314
Author: John Stultz
AuthorDate: Fri, 27 Jul 2012 14:48:13 -0400
Committer: Ingo Molnar
CommitDate: Tue, 31 Jul 2012 17:09:14 +0200
time: Remove all direct refe
This hashtable implementation is using hlist buckets to provide a simple
hashtable to prevent it from getting reimplemented all over the kernel.
Signed-off-by: Sasha Levin
---
include/linux/hashtable.h | 46 +
1 files changed, 46 insertions(+), 0 del
There are quite a few places in the kernel which implement a hashtable
in a very similar way. Instead of having implementations of a hashtable
all over the kernel, we can re-use the code.
This patch series introduces a very simple hashtable implementation, and
modifies three (random) modules to us
Switch workqueues to use the new hashtable implementation. This reduces the
amount of
generic unrelated code in the workqueues.
Signed-off-by: Sasha Levin
---
kernel/workqueue.c | 91
1 files changed, 14 insertions(+), 77 deletions(-)
diff
Switch ksm to use the new hashtable implementation. This reduces the amount of
generic unrelated code in the ksm module.
Signed-off-by: Sasha Levin
---
mm/ksm.c | 29 +
1 files changed, 9 insertions(+), 20 deletions(-)
diff --git a/mm/ksm.c b/mm/ksm.c
index 47c8853
Switch user_ns to use the new hashtable implementation. This reduces the amount
of
generic unrelated code in user_ns.
Signed-off-by: Sasha Levin
---
include/linux/user_namespace.h | 11 +---
kernel/user.c | 54 +++
kernel/user_namespa
On Tue, 2012-07-31 at 10:44 -0700, Paul E. McKenney wrote:
> OK, I interpret this as excluding NMI handlers, but please let me
> know if I am still being naive. ;-)
>
You are correct. This is only called where lockdep is called (to trace
enabling of IRQS). Note, that its called before normal ir
On Tue, Jul 31, 2012 at 03:42:56PM +0800, wei_w...@realsil.com.cn wrote:
> From: Wei WANG
>
> Realtek SD/MMC card interface driver is used to access
> SD/MMC card, with the help of Realtek card reader adapter driver.
>
> Signed-off-by: Wei WANG
> ---
[ … ]
> +static void __devexit realtek_sdm
301 - 400 of 647 matches
Mail list logo