On Tue, Sep 18, 2012 at 1:43 PM, Eric Miao wrote:
> On Mon, Sep 17, 2012 at 6:56 PM, Linus Walleij
> wrote:
>> On Fri, Sep 14, 2012 at 4:36 AM, Wei Yongjun wrote:
>>
>>> From: Wei Yongjun
>>>
>>> Using for_each_set_bit() to simplify the code.
>>>
>>> spatch with a semantic match is used to
try_to_grab_pending() leave LINKED tagalong in delayed queue when
it deletes a work. This behavior will cause future
cwq_activate_first_delayed() increase the ->nr_active wrongly,
and may cause the whole cwq frozen.
example:
state: cwq->max_active = 1, cwq->nr_active = 1
one work in
The argument @delayed is always false in all call site,
we simply remove it.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 21 -
1 files changed, 8 insertions(+), 13 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 834aa62..d15d383 100644
On Tue, 18 Sep 2012, Ryan Mallon wrote:
On 18/09/12 15:40, Shubhrajyoti wrote:
On Tuesday 18 September 2012 07:21 AM, Ryan Mallon wrote:
Actually, I wonder if it is useful to have something like:.
Read and write differ only in the flag also it will be a deviation from
what $SUBJECT
would
Add McSPI data node to AM33XX device tree file. The McSPI module (and so
as the driver) is reused from OMAP4.
Signed-off-by: Philip, Avinash
Tested-by: Matt Porter
---
Changes since v1:
- Corrected reg offset in reg DT entry.
:100644 100644 ff3badb... 065fd54... M
On 2012-09-18 02:30, Jianpeng Ma wrote:
> On 2012-09-18 02:27 Jens Axboe Wrote:
>> On 2012-09-17 19:55, Tejun Heo wrote:
>>> (cc'ing Jens)
>>>
>>> On Mon, Sep 17, 2012 at 09:22:28AM -0400, Steven Rostedt wrote:
On Mon, 2012-09-17 at 19:33 +0800, Jianpeng Ma wrote:
> Hi all:
> I
On 18/09/12 15:40, Shubhrajyoti wrote:
> On Tuesday 18 September 2012 07:21 AM, Ryan Mallon wrote:
>> Actually, I wonder if it is useful to have something like:.
> Read and write differ only in the flag also it will be a deviation from
> what $SUBJECT
> would warrant. So could be a separate
On Mon, Sep 17, 2012 at 6:56 PM, Linus Walleij wrote:
> On Fri, Sep 14, 2012 at 4:36 AM, Wei Yongjun wrote:
>
>> From: Wei Yongjun
>>
>> Using for_each_set_bit() to simplify the code.
>>
>> spatch with a semantic match is used to found this.
>> (http://coccinelle.lip6.fr/)
>>
>> Signed-off-by:
Hi John,
On Mon, Sep 17, 2012 at 10:32:07PM -0400, John Stultz wrote:
> Just wanted to send out a few timekeeping fixes that were merged
> in 3.6 which are appropriate for -stable.
Thank you very much, I'm adding them to your last ones. I have not released
the version yet but they're not lost. I
On Tuesday 18 September 2012 07:21 AM, Ryan Mallon wrote:
> Actually, I wonder if it is useful to have something like:.
Read and write differ only in the flag also it will be a deviation from
what $SUBJECT
would warrant. So could be a separate patch.
>
> #define I2C_WRITE(_addr, _buf, _len)
On Tuesday 18 September 2012 07:15 AM, Ryan Mallon wrote:
>> ,
> Putting the whole initialiser on one line is a bit ugly. Any reason not
> to expand it over multiple lines as the previous patch (and majority of
> other drivers) does?
Will do that.
--
To unsubscribe from this list:
On Mon, Sep 17, 2012 at 9:44 PM, Yinghai Lu wrote:
> On Mon, Sep 17, 2012 at 5:12 PM, Bjorn Helgaas wrote:
>> On Sun, Sep 2, 2012 at 3:50 PM, Yinghai Lu wrote:
>
>>> -static void __init pcibios_allocate_bridge_resources(struct pci_dev *dev)
>>> +static void
> Sender : Rajagopal Venkat
> Date : 2012-09-18 14:20 (GMT+09:00)
> Title : Re: Re: [PATCH 1/3] devfreq: core updates to support devices which
> can idle
> On 17 September 2012 17:46, MyungJoo Ham wrote:
> >> On 10 September 2012 14:43, 함명주 wrote:
> >> >> Prepare devfreq core framework to support
On Monday 17 September 2012 10:52 PM, Matt Porter wrote:
> Adds pinctrl support to support OMAP platforms that boot from DT
> and rely on pinctrl support to set pinmuxes.
>
> Signed-off-by: Matt Porter
> ---
looks good to me.
you may want to repost with Mark in cc to review.
Acked-by:
On 17 September 2012 17:46, MyungJoo Ham wrote:
>> On 10 September 2012 14:43, 함명주 wrote:
>> >> Prepare devfreq core framework to support devices which
>> >> can idle. When device idleness is detected perhaps through
>> >> runtime-pm, need some mechanism to suspend devfreq load
>> >> monitoring
Hi Mauro/Sekhar
On Wed, Aug 8, 2012 at 6:00 PM, Prabhakar Lad wrote:
> This first patch replaces the obsolete preset API by timings
> API for davinci VPBE, appropriate chnages in machine file for
> dm644x in which VPBE is enabled. And the second patch adds support for
> timings API for ths7303
Hi Mauro,
On Wed, Aug 8, 2012 at 5:39 PM, Prabhakar Lad wrote:
> From: Hans Verkuil
>
> Signed-off-by: Hans Verkuil
> Signed-off-by: Lad, Prabhakar
> Signed-off-by: Manjunath Hadli
> ---
> drivers/media/video/davinci/vpif.c | 16 ++--
> drivers/media/video/davinci/vpif.h |
On Mon, 2012-09-17 at 11:00 -0700, Linda Walsh wrote:
> I was wondering, on dual processor MB's, Intel uses dedicated memory for
>
> each cpu 6 memchips in the X5XXX series, and to access the memory
> of the other chip's cores, the memory has to be transferred over the QPI
> bus.
>
> So
Sorry, update the patch.
On Tue, 2012-09-18 at 20:54 +0800, Chuansheng Liu wrote:
> In handle_edge_irq(), currently do not care about the flag IRQS_ONESHOT,
> but there are many edge interrupt handler with irq thread need it indeed,
> so implement here.
>
> Signed-off-by: liu chuansheng
> ---
>
> I can see your point, but Lars-Peter's way is the more commonly used
> approach
> so lets go with the ancient arguement of making it look like what those
> reading the code expect to see ;)
Two chained patches were sent.
[PATCH 1/2] iio: inkern: put the IIO device when it fails to allocate
When the IIO consumer tries to get specific IIO channel,
few error cases can be happened.
(a) Memory allocation failure
(b) No matched ADC channel error
(c) Invalid input arguments
This patch enables cleaning up error handling in case of (a) and (b).
In error handling code,
(a): the
The reference count of the IIO device is increased if the IIO map has
matched consumer name.
After then, it tries to allocate the iio_channel which is used by the consumer.
If it fails to allocate memory, the reference count should be decreased.
This patch enables restoring the reference
On Mon, Sep 17, 2012 at 01:29:44PM -0700, Tony Lindgren wrote:
> Commit 7d7e1eba (ARM: OMAP2+: Prepare for irqs.h removal) broke
> compile for non-omap as include plat/cpu.h was added:
>
> drivers/mfd/twl-core.c:49:22: fatal error: plat/cpu.h: No such file or
> directory
>
> This header was
> Just curios about the problem you are facing without this code?
The issue I meet is in my calling request_threaded_irq()[edge interrupt], even
with IRQS_ONESHOT,
When irq thread is handling, the interrupt is still coming, and the primary
handler is called,
It cause possible spin recursive
In response to "usbip detach -p [port_number]" user
command,vhci_shoutdown_connection gets
executed which kills tcp_tx,tcp_rx kernel threads and then vhci_device_reset
resets
all usb_device struct variables except kernel thread pointers.
so, at the time of vhci_hcd removal
On Mon, Sep 17, 2012 at 5:12 PM, Bjorn Helgaas wrote:
> On Sun, Sep 2, 2012 at 3:50 PM, Yinghai Lu wrote:
>> -static void __init pcibios_allocate_bridge_resources(struct pci_dev *dev)
>> +static void pcibios_allocate_bridge_resources(struct pci_dev *dev)
>
> This patch has a little too much
On Mon, Sep 17, 2012 at 11:10:09PM +0200, Rafael J. Wysocki wrote:
> On Monday, September 17, 2012, MyungJoo Ham wrote:
> > Sender : Rafael J. Wysocki
> > Date : 2012-09-09 07:20 (GMT+09:00)
> > Title : Re: [PATCH v3 1/2] PM / devfreq: add global PM QoS support
> > > On Thursday, August 30, 2012,
Hi Sjur,
On Thu, Sep 13, 2012 at 9:03 PM, wrote:
> From: Sjur Brændeland
>
> Some of the rproc drivers needs to know the range
> of the notification IDs used for notifying the device.
> Export a variable in struct rproc holding the
> largest allocated notification id.
>
> Signed-off-by: Sjur
On Mon, Sep 17, 2012 at 7:09 PM, Linus Walleij wrote:
> This driver does clk_prepare/unprepare at probe
> and removed, so I guess what you're trying to say is that
> on your platform the clk_unprepare() process context call
> is needed to save power?
>
> Please elaborate...
Hi Linus,
Yes, we
Hi Sjur,
On Thu, Sep 13, 2012 at 9:03 PM, wrote:
> From: Sjur Brændeland
>
> Remoteproc relies on HAS_DMA, add this dependency in Kconfig.
>
> Signed-off-by: Sjur Brændeland
Applied to remoteproc-next, thanks.
Btw:
> ---
> cc: linux-kernel@vger.kernel.org
> cc: Rusty Russell
These should
stub_device_reset should set kernel thread pointers to NULL.
so that at the time of usbip_host removal stub_shoutdown_connection
doesn't try to kill kernel threads which are already killed.
Signed-off-by: navin patidar
---
drivers/staging/usbip/stub_dev.c |7 ---
1 file changed, 4
Dear RT Folks,
I'm pleased to announce the 3.0.43-rt65 stable release.
This release is just an update to the new stable 3.0.43 version
and no RT specific changes have been made.
You can get this release via the git tree at:
In handle_edge_irq(), currently do not care about the flag IRQS_ONESHOT,
but there are many edge interrupt handler with irq thread need it indeed,
so implement here.
Signed-off-by: liu chuansheng
---
kernel/irq/chip.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git
On Mon, 2012-09-17 at 15:20 +0530, Sachin Kamat wrote:
> kzalloc could return NULL. Hence add a check to avoid
> NULL pointer dereference.
>
> Signed-off-by: Sachin Kamat
> ---
> drivers/dma/pl330.c |5 +
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git
On Fri, 2012-09-07 at 12:14 +0530, Inderpal Singh wrote:
> The controller clock is being managed at AMBA bus level probe/remove and
> pm_runtime/suspend functions. The existing driver does the clock
> enable/disable
> again in the same code paths, which unneccessarily increments the usage count
This fixes below build error when CONFIG_LEDS_CLASS is not set.
LD init/built-in.o
arch/arm/plat-omap/built-in.o: In function `fpga_probe':
arch/arm/plat-omap/debug-leds.c:113: undefined reference to
`led_classdev_register'
make: *** [vmlinux] Error 1
Signed-off-by: Axel Lin
---
On Mon, 2012-08-27 at 12:40 +0800, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Using kmem_cache_zalloc() instead of kmem_cache_alloc() and memset().
>
> spatch with a semantic match is used to found this problem.
> (http://coccinelle.lip6.fr/)
>
> Signed-off-by: Wei Yongjun
> ---
>
On Mon, 2012-09-17 at 22:57 +0100, Russell King - ARM Linux wrote:
> On Mon, Sep 17, 2012 at 03:20:29PM +0530, Vinod Koul wrote:
> > On Mon, 2012-09-17 at 09:36 +0100, Russell King - ARM Linux wrote:
> > > > > I'm not saying take the slave_id out of the map. I'm saying, let the
> > > > > DMA
Hi Samuel,
Today's linux-next merge of the mfd tree got a conflict in
drivers/regulator/anatop-regulator.c between commit 3e2a928472da
("regulator: anatop: Fix wrong mask used in anatop_get_voltage_sel") from
Linus' tree and commit baa64151aecc ("regulator: anatop-regulator:
Convert to use syscon
On Mon, Sep 17, 2012 at 4:38 PM, Bjorn Helgaas wrote:
> On Sun, Sep 2, 2012 at 3:50 PM, Yinghai Lu wrote:
>> So could use it with hot-added root bus.
>>
>> Signed-off-by: Yinghai Lu
>> ---
>> arch/x86/pci/i386.c | 58
>> ---
>> 1 files
To emulate level triggered interrupts, add a resample option to
KVM_IRQFD. When specified, a new resamplefd is provided that notifies
the user when the irqchip has been resampled by the VM. This may, for
instance, indicate an EOI. Also in this mode, injection of an
interrupt through an irqfd
This enables better integration into irqfd setup where we can adjust
our lock ordering to hold irq_lock, making these callable and avoiding
irq source ID races.
Signed-off-by: Alex Williamson
---
include/linux/kvm_host.h |4
virt/kvm/irq_comm.c | 18 --
2 files
Updated with suggestions from Michael and Avi, the OADN option is
now a "resample" option. Re-working locking went surprisingly
well, lockdep clean, and now allows us to use a single irq source
ID for all resample irqfds. I hope we're close. Thanks,
Alex
---
Alex Williamson (2):
kvm:
Arve Hjønnevåg reported numerous crashes from the
"BUG_ON(timer->state != HRTIMER_STATE_CALLBACK)" check
in __run_hrtimer after it called alarmtimer_fired.
It ends up the alarmtimer code was not properly handling
possible failures of hrtimer_try_to_cancel, and because
these faulres occur when the
Now that alarmtimer_remove has been simplified, change
its name to _dequeue to better match its paired _enqueue
function.
Cc: Arve Hjønnevåg
Cc: Colin Cross
Cc: Thomas Gleixner
Signed-off-by: John Stultz
---
kernel/time/alarmtimer.c |8
1 file changed, 4 insertions(+), 4
No one is using these alarmtimer state helpers, so yank them.
Cc: Arve Hjønnevåg
Cc: Colin Cross
Cc: Thomas Gleixner
Signed-off-by: John Stultz
---
include/linux/alarmtimer.h | 28
1 file changed, 28 deletions(-)
diff --git a/include/linux/alarmtimer.h
Arve Hjønnevåg reported numerous crashes from the
"BUG_ON(timer->state != HRTIMER_STATE_CALLBACK)" check
in __run_hrtimer after it called alarmtimer_fired.
Looking at the code, I realized much of the logic duplicated
the hrtimer code, and that by multiplexing numerous alarmtimers
onto a single
On 09/17/2012 11:36 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 11, 2012 at 04:27:17PM +0200, Jiri Olsa escreveu:
>> On Mon, Sep 10, 2012 at 03:53:51PM +0800, Yan, Zheng wrote:
>>
>> Would it be possible to have all '*add_event' more obvious for usage.
>> Also following code is duplicated
On Sun, 2012-09-16 at 11:55 +0300, Avi Kivity wrote:
> On 09/14/2012 12:30 AM, Andrew Theurer wrote:
>
> > The concern I have is that even though we have gone through changes to
> > help reduce the candidate vcpus we yield to, we still have a very poor
> > idea of which vcpu really needs to run.
On 09/17/2012 12:38 PM, Stefano Stabellini wrote:
> Add a doc to describe the Xen ARM device tree bindings
>
>
> Changes in v5:
>
> - add a comment about the size of the grant table memory region;
> - add a comment about the required presence of a GIC node;
> - specify that the described
Dear RT Folks,
I'm pleased to announce the 3.2.29-rt44 stable release.
This release is just an update to the new stable 3.2.29 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On 09/17/2012 07:32 PM, John Stultz wrote:
Just wanted to send out a few timekeeping fixes that were merged
in 3.6 which are appropriate for -stable.
And I did it again.
The subject of this should have been:
"2.6.32-stable timekeeping fixes merged in 3.6"
Apologies for any confusion.
On 09/17/2012 06:38 PM, John Stultz wrote:
Just wanted to send out a few timekeeping fixes that were merged
in 3.6 which are appropriate for -stable.
Manabu Ori noted that the subject here should have been:
"2.6.34-stable timekeeping fixes merged in 3.6"
My brain is apparently more
This is a -stable backport of 4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b
Unexpected behavior could occur if the time is set to a value large
enough to overflow a 64bit ktime_t (which is something larger then the
year 2262).
Also unexpected behavior could occur if large negative offsets are
This is a -stable backport of cee58483cf56e0ba355fdd97ff5e8925329aa936
Andreas Bombe reported that the added ktime_t overflow checking added to
timespec_valid in commit 4e8b14526ca7 ("time: Improve sanity checking of
timekeeping inputs") was causing problems with X.org because it caused
timeouts
This is a -stable backport of bf2ac312195155511a0f79325515cbb61929898a
If update_wall_time() is called and the current offset isn't large
enough to accumulate, avoid re-calling timekeeping_adjust which may
change the clock freq and can cause 1ns inconsistencies with
Just wanted to send out a few timekeeping fixes that were merged
in 3.6 which are appropriate for -stable.
This queue backports the following fixes:
-
cee58483cf56e0ba355fdd97ff5e8925329aa936time: Move ktime_t overflow
checking into
* Tony Lindgren [120917 15:27]:
> * Paul Walmsley [120917 15:25]:
> > On Mon, 17 Sep 2012, Tony Lindgren wrote:
> >
> > > We need to queue this ASAP and before other patches to fix the
> > > build breakage in linux next. Then you can merge in that commit
> > > too, does that work for you?
> >
Hi all,
Today's linux-next merge of the sound-asoc tree got a conflict in
arch/arm/mach-imx/mach-imx27_visstrim_m10.c between commit b6c14dc29757
("[media] Visstrim M10: Add support for Coda") from the v4l-dvb tree and
commit d41789b2660e ("ASoC: mx27vis: retrieve gpio numbers from
On Tue, Sep 18, 2012 at 5:30 AM, Dave Chinner wrote:
> On Mon, Sep 17, 2012 at 03:18:34PM +0800, zwu.ker...@gmail.com wrote:
>> From: Zhi Yong Wu
>>
>> NOTE:
>>
>> The patchset is currently post out mainly to make sure
>> it is going in the correct direction and hope to get some
>> helpful
Dear RT Folks,
I'm pleased to announce the 3.4.11-rt19 stable release.
This release is just an update to the new stable 3.4.11 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Mon, Sep 17, 2012 at 09:30:54PM +0800, Samuel Ortiz wrote:
> Hi Dong,
>
> On Mon, Sep 17, 2012 at 06:10:29PM +0800, Dong Aisheng wrote:
> > Hi Samuel,
> >
> > On Wed, Sep 05, 2012 at 01:54:12PM +0800, Shawn Guo wrote:
> > > Hi Samuel,
> > >
> > > The series needs to go via mfd or arm-soc
On 17/09/12 23:58, Shubhrajyoti D wrote:
> Convert the struct i2c_msg initialization to C99 format. This makes
> maintaining and editing the code simpler. Also helps once other fields
> like transferred are added in future.
>
> Signed-off-by: Shubhrajyoti D
> ---
>
omap_device_get_by_hwmod_name() returns ERR_PTR on error.
Signed-off-by: Axel Lin
---
drivers/cpufreq/omap-cpufreq.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/omap-cpufreq.c b/drivers/cpufreq/omap-cpufreq.c
index 6e22f44..65f8e9a 100644
---
On 17/09/12 23:58, Shubhrajyoti D wrote:
> Convert the struct i2c_msg initialization to C99 format. This makes
> maintaining and editing the code simpler. Also helps once other fields
> like transferred are added in future.
>
> Signed-off-by: Shubhrajyoti D
> ---
>
On 17/09/12 23:58, Shubhrajyoti D wrote:
> Convert the struct i2c_msg initialization to C99 format. This makes
> maintaining and editing the code simpler. Also helps once other fields
> like transferred are added in future.
>
> Signed-off-by: Shubhrajyoti D
> ---
>
This is a -stable backport of cee58483cf56e0ba355fdd97ff5e8925329aa936
Andreas Bombe reported that the added ktime_t overflow checking added to
timespec_valid in commit 4e8b14526ca7 ("time: Improve sanity checking of
timekeeping inputs") was causing problems with X.org because it caused
timeouts
Just wanted to send out a few timekeeping fixes that were merged
in 3.6 which are appropriate for -stable.
This queue backports the following fixes:
-
cee58483cf56e0ba355fdd97ff5e8925329aa936time: Move ktime_t overflow
checking into
This is a -stable backport of bf2ac312195155511a0f79325515cbb61929898a
If update_wall_time() is called and the current offset isn't large
enough to accumulate, avoid re-calling timekeeping_adjust which may
change the clock freq and can cause 1ns inconsistencies with
This is a -stable backport of 4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b
Unexpected behavior could occur if the time is set to a value large
enough to overflow a 64bit ktime_t (which is something larger then the
year 2262).
Also unexpected behavior could occur if large negative offsets are
At 09/17/2012 07:07 PM, Ingo Molnar Wrote:
>
> * Jerry Snitselaar wrote:
>
>> Commit 13ad20c1 "x86 cpu_hotplug: unmap cpu2node when the cpu is
>> hotremoved" in linux-next added code to acpi_unmap_lsapic() that
>> causes section mismatch warnings:
>>
>> WARNING: vmlinux.o(.text+0x694f2):
At 09/05/2012 07:11 AM, Andrew Morton Wrote:
> On Mon, 03 Sep 2012 16:12:12 +0800
> Wen Congyang wrote:
>
>> If we don't debug per_cpu maps, the cpu's node is stored in per_cpu variable
>> numa_node. If node is NUMA_NO_NODE, it means the caller want to clear the
>> cpu's node. So we should also
On Mon, 2012-09-17 at 20:05 +0200, Peter Senna Tschudin wrote:
> From: Peter Senna Tschudin
>
> Convert a nonnegative error return code to a negative one, as returned
> elsewhere in the function.
>
> A simplified version of the semantic match that finds this problem is as
> follows:
2012/9/18 Andreas Pretzsch :
> commit e7c706b1e5ccf28eaaf76c7a4613e80b0ca52863 migrated the allocation
> of struct mc13xxx to devm_* functions, but left a kfree(mc13xxx) in the
> mc13xxx_common_init error path. Remove it to prevent memory corruption.
>
> Signed-off-by: Andreas Pretzsch
On Mon, 2012-09-17 at 13:41 +1000, Stephen Rothwell wrote:
> Hi Nicholas,
>
> After merging the target-updates tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/target/target_core_transport.c: In function
> 'transport_get_sense_buffer':
>
On 09/17/2012 04:49 PM, Andy Lutomirski wrote:
On Mon, Sep 17, 2012 at 3:04 PM, John Stultz wrote:
This item has been on my todo list for a number of years.
One interesting bit of the timekeeping code is that we internally
keep sub-nanosecond precision. This allows for really fine
grained
this following function is missing a important NULL check. if DMI is not
available or not enabled in the kernel config (which is common in my
case, since its a ARM Platform with XHCI support)
the xhci-hcd driver will crash due nullpointer access since
dmi_get_system_info returns always NULL if
this following function is missing a important NULL check. if DMI is not
available or not enabled in the kernel config (which is common in my
case, since its a ARM Platform with XHCI support)
the xhci-hcd driver will crash due nullpointer access since
dmi_get_system_info returns always NULL if
On Mon, Sep 17, 2012 at 5:20 PM, John Stultz wrote:
> On 09/17/2012 04:49 PM, Andy Lutomirski wrote:
>>
>> On Mon, Sep 17, 2012 at 3:04 PM, John Stultz
>> wrote:
>>>
>>> Anyway, I'd greatly appreciate any thoughts or feedback on this
>>> approach.
>>
>> I haven't looked in any great detail, but
>Mon, Sep 17, 2012 at 06:12:14PM CEST, shemmin...@vyatta.com wrote:
>>On Mon, 17 Sep 2012 17:10:17 +0200
>>Jiri Pirko wrote:
>>
>>> In my case I have following problem. sky2_set_multicast() sets registers
>>> GM_MC_ADDR_H[1-4] correctly to:
>>> 0800 0001 0410
>>> However, when adapter gets
Just wanted to send out a few timekeeping fixes that were merged
in 3.6 which are appropriate for -stable.
This queue backports the following fixes:
-
cee58483cf56e0ba355fdd97ff5e8925329aa936time: Move ktime_t overflow
checking into
On 2012-09-18 02:27 Jens Axboe Wrote:
>On 2012-09-17 19:55, Tejun Heo wrote:
>> (cc'ing Jens)
>>
>> On Mon, Sep 17, 2012 at 09:22:28AM -0400, Steven Rostedt wrote:
>>> On Mon, 2012-09-17 at 19:33 +0800, Jianpeng Ma wrote:
Hi all:
I used blktrace to trace some io.But i can't find
On Sun, Sep 2, 2012 at 3:50 PM, Yinghai Lu wrote:
> During testing remove/rescan root bus 00, found
> [ 338.142574] bus: 'pci': really_probe: probing driver ata_piix with device
> :00:01.1
> [ 338.146788] ata_piix :00:01.1: device not available (can't reserve [io
> 0x01f0-0x01f7])
>
2012/09/15 5:14, Andrew Morton wrote:
On Fri, 14 Sep 2012 20:00:09 +0900
Yasuaki Ishimatsu wrote:
@@ -187,9 +184,10 @@ void register_page_bootmem_info_node(struct pglist_data
*pgdat)
end_pfn = pfn + pgdat->node_spanned_pages;
/* register_section info */
- for (; pfn <
On Mon, 17 Sep 2012, Andrew Morton wrote:
> On Sat, 15 Sep 2012 15:50:07 +0200
> Sasha Levin wrote:
>
> > Hi all,
> >
> > While fuzzing with trinity within a KVM tools guest on a linux-next kernel,
> > I
> > got the lockdep warning at the bottom of this mail.
> >
> > I've tried figuring out
The I2C core provides a means to instantiate devices from userspace
using sysfs attributes. Provide the same mechanism for SPI devices.
Signed-off-by: Guenter Roeck
---
This helped me tremendously for testing new SPI master and client drivers.
Maybe it is useful for others as well.
ping: Any
On Mon, Sep 17, 2012 at 3:04 PM, John Stultz wrote:
> This item has been on my todo list for a number of years.
>
> One interesting bit of the timekeeping code is that we internally
> keep sub-nanosecond precision. This allows for really fine
> grained error accounting, which allows us to keep
Hi,
On Tuesday 18 September 2012 07:46:27 harryxiyou wrote:
> 2012/9/17 Tekkaman Ninja :
> > This is a Chinese translated version of
> > Documentation/video4linux/omap3isp.txt
> >
> > Signed-off-by: Fu Wei
>
> Acked-by: Harry Wei
I'll trust the ack, as I don't understand a word of the
2012/9/17 Tekkaman Ninja :
> This is a Chinese translated version of Documentation/video4linux/omap3isp.txt
>
> Signed-off-by: Fu Wei
>
Acked-by: Harry Wei
--
Thanks
Harry Wei
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, Sep 17, 2012 at 1:42 PM, Dan Magenheimer
wrote:
>> From: Nitin Gupta [mailto:ngu...@vflare.org]
>> Subject: Re: [RFC] mm: add support for zsmalloc and zcache
>>
>> The problem is that zbud performs well only when a (compressed) page is
>> either PAGE_SIZE/2 - e or PAGE_SIZE - e, where e
On Mon, Sep 17, 2012 at 6:41 AM, Linus Walleij wrote:
> 2012/9/16 Tekkaman Ninja :
>
>> Fixes some translation error in Documentation/zh_CN/gpio.txt
>> The modification is based on Dong Aisheng 's
>> corrections:
>> 1.Two "OUTPUT" is incorrectly translated as "输入";
>> 2.five improvement
On Mon, Sep 17, 2012 at 1:33 AM, Tekkaman Ninja wrote:
> Remove 3 byte redundant code at the head of
> the Documentation/zh_CN/arm/booting
>
> When I see the file Documentation/zh_CN/arm/booting using
> Bless(binary Viewer),I find 3 byte redundant in it. So I
> make a patch to correcting that
On Sun, Sep 2, 2012 at 3:50 PM, Yinghai Lu wrote:
> So could use it with hot-added root bus.
>
> Signed-off-by: Yinghai Lu
> ---
> arch/x86/pci/i386.c | 58
> ---
> 1 files changed, 41 insertions(+), 17 deletions(-)
>
> diff --git
On 09/10/12 15:24, Stephen Boyd wrote:
> Remove the offset from ipi_msg_type and assume that SGI0 is the
> wakeup interrupt now that all WFI hotplug users call
> gic_raise_softirq() with 0 instead of 1. This allows us to
> track how many wakeup interrupts are sent and also removes the
> unknown
On Sat, 15 Sep 2012 15:50:07 +0200
Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity within a KVM tools guest on a linux-next kernel, I
> got the lockdep warning at the bottom of this mail.
>
> I've tried figuring out where it was introduced, but haven't found any sign
> that
> any
> > Should I keep the sysfs layout of LP5521 and LP5523?
> > When we change the device attributes, do we have to consider the
> backward compatibility?
>
> The ABI is a contract so basically yes, you need real good reasons
> (like security concerns) to change the ABI.
>
> That said, the lm3533
> Actually, I'm not sure about the impact with changing the sysfs
> interface. I guess we need some input from the driver authors.
As you already noticed, I can't contact authors.
Mail accounts don't exist anymore.
>
> Personally I vote for the simple firmware interface there, since it
> looks
On Thu, Sep 13, 2012 at 04:18:41PM +0200, Daniel Vetter wrote:
> Hi Dave,
>
> The big ticket item here is the new i915 modeset infrastructure.
> Shockingly it didn't not blow up all over the place (i.e. I've managed to
> fix the ugly issues before merging). 1-2 smaller corner cases broke, but
>
Dave Airlie recently discovered a locking bug in the fbcon layer,
where a timer_del_sync (for the blinking cursor) deadlocks with the
timer itself, since both (want to) hold the console_lock:
https://lkml.org/lkml/2012/8/21/36
Unfortunately the console_lock isn't a plain mutex and hence has no
Instead of BUG_ON(in_interrupt()), since that doesn't check for all
the newfangled stuff like preempt.
Note that this is valid since the console_sem is essentially used like
a real mutex with only two twists:
- we allow trylock from hardirq context
- across suspend/resume we lock the logical
1 - 100 of 1254 matches
Mail list logo
