Hi Konrad,
On Wed, Nov 28, 2012 at 04:22:05PM -0500, Konrad Rzeszutek Wilk wrote:
> I looked at the patches and you can also add
> Reviewed-by: Konrad Rzeszutek Wilk
Thanks for your review, I added the line to the patches.
> If you have a git tree I would like to test them as well. Thx.
I reb
Bool initializations should use true and false. Bool tests don't need
comparisons. Based on contributions from Joe Perches, Rusty Russell
and Bruce W Allan.
The semantic patch that makes this output is available
in scripts/coccinelle/misc/boolinit.cocci.
More information about semantic patching
On Thu, Nov 29, 2012 at 06:40:51AM +0800, Xiao Guangrong wrote:
> On 11/29/2012 05:57 AM, Marcelo Tosatti wrote:
> > On Wed, Nov 28, 2012 at 10:59:35PM +0800, Xiao Guangrong wrote:
> >> On 11/28/2012 10:12 PM, Gleb Natapov wrote:
> >>> On Tue, Nov 27, 2012 at 11:30:24AM +0800, Xiao Guangrong wrote:
On Wed, Nov 28, 2012 at 08:53:15PM +0800, Xiao Guangrong wrote:
> In loaded_vmcs_clear, loaded_vmcs->cpu is the fist parameter passed to
> smp_call_function_single, if the target cpu is downing (doing cpu hot remove),
> loaded_vmcs->cpu can become -1 then -1 is passed to smp_call_function_single
>
On Wed, Nov 28, 2012 at 08:54:14PM +0800, Xiao Guangrong wrote:
> vmcs->cpu indicates whether it exists on the target cpu, -1 means the vmcs
> does not exist on any vcpu
>
> If vcpu load vmcs with vmcs.cpu = -1, it can be directly added to cpu's percpu
> list. The list can be corrupted if the cpu
On 11/28/2012 03:05 PM, Mike Turquette wrote:
> Quoting Mark Langsdorf (2012-11-28 08:18:35)
>> On 11/28/2012 10:01 AM, Mike Turquette wrote:
>>> Quoting Shawn Guo (2012-11-28 07:17:44)
On Wed, Nov 28, 2012 at 10:58:02PM +0800, Shawn Guo wrote:
> On Wed, Nov 28, 2012 at 07:16:12AM -0600, M
> - int i = 0;
> + DEFINE_WAIT(wait);
> + struct hrtimer_sleeper t;
> + size_t i = 0;
Changing i to size_t is kind of surprising. Is that on purpose?
> - set_task_state(tsk, TASK_RUNNING);
> - remove_wait_queue(&ctx->wait, &wait);
> -
>
On Thu, Nov 29, 2012 at 07:16:50AM +0800, Xiao Guangrong wrote:
> On 11/29/2012 06:40 AM, Xiao Guangrong wrote:
> > On 11/29/2012 05:57 AM, Marcelo Tosatti wrote:
> >> On Wed, Nov 28, 2012 at 10:59:35PM +0800, Xiao Guangrong wrote:
> >>> On 11/28/2012 10:12 PM, Gleb Natapov wrote:
> On Tue, No
On Thu, Nov 29, 2012 at 01:20:37AM +0100, Peter Huewe wrote:
> - itpm = (probe == 0) ? 0 : 1;
> + itpm = (probe == 0) ? false : true;
Charming. Not that original had been better, but...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
> It seems like a better approach would be to adjust the timer somehow when
> you change c-states. The whole point of the hard and softlockup is to
> detect if scheduled code is either deadlock or hogging the cpu for too long.
>
> If the cpu is in a deep sleep, then nothing is running, right? Wh
On 11/27/2012 07:49 AM, Justin Piszcz wrote:
It looks like maybe you don't have CONFIG_PCI_MMCONFIG turned on?
===> FOR I/OAT DMA
Latest status, it _appears_ its working on the X9SRL-F now, thank you!
1) Supermicro X9SRL-F (GOOD)
[0.738510] ioatdma: Intel(R) QuickData Technology Driver 4
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Wednesday, November 28, 2012 7:05 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org
> Subject: Re: drivres/hv
>
> On Wed, Nov 28, 2012 at 11:32:52PM +, KY Srinivasan
> We can't use cmpxchg() on the ring buffer's head pointer directly, since
> it's modded to nr_events and would be susceptible to ABA. So instead we
> maintain a shadow head that uses the full 32 bits, and cmpxchg() that
> and then updated the real head pointer.
Time to update this comment to refl
On Wed, 28 Nov 2012, Linus Torvalds wrote:
> > For example, __block_write_full_page and __block_write_begin do
> > if (!page_has_buffers(page)) { create_empty_buffers... }
> > and then they do
> > WARN_ON(bh->b_size != blocksize)
> > err = get_block(inode, block, bh, 1)
>
Bool initializations should use true and false. Bool tests don't need
comparisons. Based on contributions from Joe Perches, Rusty Russell
and Bruce W Allan.
The semantic patch that makes this output is available
in scripts/coccinelle/misc/boolinit.cocci.
More information about semantic patching
Am Donnerstag, 29. November 2012, 01:25:19 schrieb Al Viro:
> On Thu, Nov 29, 2012 at 01:20:37AM +0100, Peter Huewe wrote:
> > - itpm = (probe == 0) ? 0 : 1;
> > + itpm = (probe == 0) ? false : true;
>
> Charming. Not that original had been better, but...
Yeah. Sorry it's late
On Wed, Nov 28, 2012 at 04:29:01PM +0800, Wen Congyang wrote:
>At 11/28/2012 12:08 PM, Jiang Liu Wrote:
>> On 2012-11-28 11:24, Bob Liu wrote:
>>> On Tue, Nov 27, 2012 at 8:49 PM, Tang Chen wrote:
On 11/27/2012 08:09 PM, Bob Liu wrote:
>
> On Tue, Nov 27, 2012 at 4:29 PM, Tang Chen
>>
-Original Message-
From: Bjorn Helgaas [mailto:bhelg...@google.com]
Sent: Wednesday, November 28, 2012 6:54 PM
To: Justin Piszcz
Cc: Bruno Prémont; supp...@supermicro.com; linux-kernel@vger.kernel.org; Dan
Williams
Subject: Re: Supermicro X9SRL-F - channel enumeration error & ACPI/firmwa
the card in, and it errors as usual but the SSD now on the motherboard it
does boot successfully.
Here are the errors from the kernel trying to initialize the board with
iommu enabled (retrieved via netconsole) also picture below (w/help from
boot_delay=100 && nouveau enabled):
http://h
port
> mask: 0x08)
What's the full dmesg from this machine (or is it already posted somewhere)?
It is now available here:
http://home.comcast.net/~jpiszcz/20121128/dmesg.txt
Justin.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
This is necessary because __pa() does not work on some kinds of
memory, like vmalloc() or the alloc_remap() areas on 32-bit
NUMA systems. We have some functions to do conversions _like_
this in the vmalloc() code (like vmalloc_to_page()), but they
do not work on sizes other than 4k pages. We wou
>> ==> Further issues with the X9SRL-F -- does this board support ASPM or is
>> this a Linux/ASPM implementation issue?
>> [0.632170] pci:ff: ACPI _OSC support notification failed,
> disabling
>> PCIe ASPM
>> [0.632239] pci:ff: Unable to request _O
On Wed, Nov 28, 2012 at 04:07:53PM -0800, Zach Brown wrote:
> On Wed, Nov 28, 2012 at 08:43:31AM -0800, Kent Overstreet wrote:
> > Minor refactoring, to get rid of some duplicated code
>
> A minor nit:
>
> > spin_lock_irq(&ctx->ctx_lock);
> > - ret = -EAGAIN;
> > +
> > kiocb = lookup_ki
In short, it is illegal to call __pa() on an address holding
a percpu variable. The times when this actually matters are
pretty obscure (certain 32-bit NUMA systems), but it _does_
happen. It is important to keep KVM guests working on these
systems because the real hardware is getting harder and
Cong Wang wrote:
On Wed, Nov 28, 2012 at 4:37 AM, Linda Walsh wrote:
Is this a known problem / bug, or should I file a bug on it?
Does this quick fix help?
...
Thanks!
Applied:
--- bond_main.c.orig 2012-09-30 16:47:46.0 -0700
+++ bond_main.c 2012-11-28 12:58:34.064931997 -08
On Wed, Nov 28, 2012 at 04:24:36PM -0800, Zach Brown wrote:
> > - int i = 0;
> > + DEFINE_WAIT(wait);
> > + struct hrtimer_sleeper t;
> > + size_t i = 0;
>
> Changing i to size_t is kind of surprising. Is that on purpose?
I doubt it matters due to limits on ringbuffer
On Thu, 2012-11-29 at 00:49 +0100, Rafael J. Wysocki wrote:
> On Wednesday, November 28, 2012 02:02:48 PM Toshi Kani wrote:
> > > > > > > > > Consider the following case:
> > > > > > > > >
> > > > > > > > > We hotremove the memory device by SCI and unbind it from the
> > > > > > > > > driver at t
we have to call kobject_put() to clean up the kobject after function
kobject_init(), kobject_add(), or kobject_uevent() is called.
Signed-off-by: Cong Ding
---
drivers/uio/uio.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
On Wed, Nov 28, 2012 at 04:17:59PM -0800, Zach Brown wrote:
>
> > struct kioctx {
> > atomic_tusers;
> > - int dead;
> > + atomic_tdead;
>
> Do we want to be paranoid and atomic_set() that to 0 when the ioctx is
> allocated?
I suppose
Hi Kent,
On Wed, Nov 28, 2012 at 08:43:36AM -0800, Kent Overstreet wrote:
> + * now it's safe to cancel any that need to be.
> + */
> +static void free_ioctx(struct kioctx *ctx)
...
> + aio_nr -= ctx->max_reqs;
> + spin_unlock(&aio_nr_lock);
> +
> + synchronize_rcu();
> +
> + pr_de
Revert 3.5's f21f8062201f ("tmpfs: revert SEEK_DATA and SEEK_HOLE")
to reinstate 4fb5ef089b28 ("tmpfs: support SEEK_DATA and SEEK_HOLE"),
with the intervening additional arg to generic_file_llseek_size().
In 3.8, ext4 is expected to join btrfs, ocfs2 and xfs with proper
SEEK_DATA and SEEK_HOLE sup
On Wed, 2012-11-28 at 18:02 -0700, Toshi Kani wrote:
> On Thu, 2012-11-29 at 00:49 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, November 28, 2012 02:02:48 PM Toshi Kani wrote:
> > > > > > > > > > Consider the following case:
> > > > > > > > > >
> > > > > > > > > > We hotremove the memory devi
From: Anton Vorontsov
It seems that 'ftrace_enabled' flag should not be used inside the tracer
functions. The ftrace core is using this flag for internal purposes, and
the flag wasn't meant to be used in tracers' runtime checks.
stack tracer is the only tracer that abusing the flag. So stop it f
Ingo,
This is based off of my last pull request on tip/perf/core.
Please pull the latest tip/perf/core-2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/core-2
Head SHA1: bf3071f5a054db9e5bab873355d27a7330ce5187
Anton Vorontsov (1
From: Dave Jones
WARN shouldn't be used as a means of communicating failure to a userspace
programmer.
Link: http://lkml.kernel.org/r/20120725153908.ga25...@redhat.com
Signed-off-by: Dave Jones
Signed-off-by: Steven Rostedt
---
kernel/trace/trace.c |2 --
1 file changed, 2 deletions(-)
On 11/29/2012 08:43 AM, Jaegeuk Hanse wrote:
Hi Tang,
I haven't read the patchset yet, but could you give a short describe how
you design your implementation in this patchset?
Regards,
Jaegeuk
Hi Jaegeuk,
Thanks for your joining in. :)
This feature is used in memory hotplug.
In order to i
From: Hiraku Toyooka
Trace buffer size is now per-cpu, so that there are the following two
patterns in resizing of buffers.
(1) resize per-cpu buffers to same given size
(2) resize per-cpu buffers to another trace_array's buffer size
for each CPU (such as preparing the max_tr which is
> The notifiers in the clk framework might be a better place for this than
> just simply hacking the logic into the .set_rate callback.
Ah, right. How did I forget about that nice piece?
> I haven't looked at the definition of hb_voltage_change but does the
> call graph make any clk api calls?
On Wed, Nov 28, 2012 at 05:22:03PM -0800, Hugh Dickins wrote:
>Revert 3.5's f21f8062201f ("tmpfs: revert SEEK_DATA and SEEK_HOLE")
>to reinstate 4fb5ef089b28 ("tmpfs: support SEEK_DATA and SEEK_HOLE"),
>with the intervening additional arg to generic_file_llseek_size().
>
>In 3.8, ext4 is expected t
On Wed, Nov 28, 2012 at 03:14:32PM -0800, Andrew Morton wrote:
[...]
> Compare this with the shrink_slab() shrinkers. With these, the VM can
> query and then control the clients. If something goes wrong or is out
> of balance, it's the VM's problem to solve.
>
> So I'm thinking that a better des
On Wed, Nov 28, 2012 at 02:15:05PM +0900, Minchan Kim wrote:
> Hi Nitin,
>
> On Mon, Nov 26, 2012 at 11:26:07PM -0800, Nitin Gupta wrote:
> > The commit c8f2f0db1 ("zram: Fix handling of incompressible pages")
> > introduced a bug which caused a kunmap()'ed buffer to be used in case
>
> I got con
On Nov 28, 2012, at 6:42 PM, Andrew Morton wrote:
> On Wed, 21 Nov 2012 19:52:41 -0500
> Ed Cashin wrote:
>
>> This patch series applies to today's linux-next/akpm, commit
>> d3faae60d84f586ff8937b77c8476bca1b5f8ec6.
>>
>> Ed L. Cashin (8):
>> aoe: copy fallback timing information on destinati
On Wed, Nov 28, 2012 at 03:54:45PM +0100, Jerome Marchand wrote:
> On 11/28/2012 03:35 AM, Minchan Kim wrote:
> > Lockdep complains about recursive deadlock of zram->init_lock.
> > [1] made it false positive because we can't request IO to zram
> > before setting disksize. Anyway, we should shut loc
Hi Sakari,
Thanks for the quick review.
On Thu, Nov 29, 2012 at 1:48 AM, Sakari Ailus wrote:
> Hi Prabhakar,
>
> On Wed, Nov 28, 2012 at 04:25:33PM +0530, Prabhakar Lad wrote:
>> From: Manjunath Hadli
>>
>> request_mem_region for VPSS_CLK_CTRL register and ioremap.
>> and enable clocks appropri
On Wed, Nov 28, 2012 at 07:46:31PM -0500, Benjamin LaHaise wrote:
> Hi Kent,
>
> On Wed, Nov 28, 2012 at 08:43:36AM -0800, Kent Overstreet wrote:
> > + * now it's safe to cancel any that need to be.
> > + */
> > +static void free_ioctx(struct kioctx *ctx)
> ...
> > + aio_nr -= ctx->max_reqs;
> >
On 11/27/2012 08:22 AM, Jerome Marchand wrote:
On 11/27/2012 08:26 AM, Nitin Gupta wrote:
For every allocated object, zram maintains the the handle, size,
flags and count fields. Of these, only the handle is required
since zsmalloc now provides the object size given the handle.
The flags field w
On Wed, Nov 28, 2012 at 04:47:42PM +0800, Jiang Liu wrote:
>Hi all,
> Seems it's a great chance to discuss about the memory hotplug feature
>within this thread. So I will try to give some high level thoughts about memory
>hotplug feature on x86/IA64. Any comments are welcomed!
> First o
On 11/28/2012 05:33 PM, Minchan Kim wrote:
On Wed, Nov 28, 2012 at 02:15:05PM +0900, Minchan Kim wrote:
Hi Nitin,
On Mon, Nov 26, 2012 at 11:26:07PM -0800, Nitin Gupta wrote:
The commit c8f2f0db1 ("zram: Fix handling of incompressible pages")
introduced a bug which caused a kunmap()'ed buffer
On Wed, 2012-11-28 at 13:55 +0100, Frederic Weisbecker wrote:
> 2012/11/28 Li Zhong :
> > Thank you all for the review and education.
> >
> > Below are my current understandings and an update version. Would you
> > please help to review it again and give your comments?
> >
> > Thanks, Zhong
> >
> >
On Wed, 21 Nov 2012 16:31:11 +0200
Andy Shevchenko wrote:
> When build a kernel with "make W=1" we will get a warning about missing
> initializer. It comes from kfifo usage style. The DEFINE_KFIFO macro doesn't
> initialize the buf[] field of the fifo structure. So, using C99 style helps in
> suc
Linda Walsh wrote:
>
>Cong Wang wrote:
>> On Wed, Nov 28, 2012 at 4:37 AM, Linda Walsh wrote:
>>> Is this a known problem / bug, or should I file a bug on it?
>> Does this quick fix help?
>> ...
>> Thanks!
>>
>
> Applied:
>--- bond_main.c.orig 2012-09-30 16:47:46.0 -0700
>+++ bo
Don't adjust the selector in [get|set]_voltage_sel, fix it in list_voltage()
instead.
For smps*(except smps10), the vsel reg-value and voltage mapping as below:
reg-value volt (uV) ( Assume RANGE is x1 )
0 0
1 50
2 50
3 50
On Wed, 2012-11-28 at 14:26 -0800, Chegu Vinod wrote:
> On 11/27/2012 6:23 AM, Chegu Vinod wrote:
>
> > On 11/27/2012 2:30 AM, Raghavendra K T wrote:
> > > On 11/26/2012 07:05 PM, Andrew Jones wrote:
> > > > On Mon, Nov 26, 2012 at 05:37:54PM +0530, Raghavendra K T
> > > > wrote:
> > > > > From
Signed-off-by: Axel Lin
---
drivers/regulator/palmas-regulator.c | 87 ++
1 file changed, 26 insertions(+), 61 deletions(-)
diff --git a/drivers/regulator/palmas-regulator.c
b/drivers/regulator/palmas-regulator.c
index 76eaafb..932cc05 100644
--- a/drivers/regu
On Thu, 29 Nov 2012, Jaegeuk Hanse wrote:
> On Wed, Nov 28, 2012 at 05:22:03PM -0800, Hugh Dickins wrote:
> >Revert 3.5's f21f8062201f ("tmpfs: revert SEEK_DATA and SEEK_HOLE")
> >to reinstate 4fb5ef089b28 ("tmpfs: support SEEK_DATA and SEEK_HOLE"),
> >with the intervening additional arg to generic
[ Sorry, I was offline for a while driving kids around ]
On Wed, Nov 28, 2012 at 4:38 PM, Mikulas Patocka wrote:
>
> It can happen. Take your patch (the one that moves bd_block_size_semaphore
> into blkdev_readpage, blkdev_writepage and blkdev_write_begin).
Interesting. The code *has* the block
On 11/29/2012 08:04 AM, Marcelo Tosatti wrote:
> On Wed, Nov 28, 2012 at 08:54:14PM +0800, Xiao Guangrong wrote:
>> vmcs->cpu indicates whether it exists on the target cpu, -1 means the vmcs
>> does not exist on any vcpu
>>
>> If vcpu load vmcs with vmcs.cpu = -1, it can be directly added to cpu's
NULL pointer dereference at virtual address 0008
Modules linked in: rtc_tps65910(-)
CPU: 0Not tainted (3.7.0-rc7-next-20121128-g6b1f974-dirty #7)
PC is at tps65910_rtc_alarm_irq_enable+0x20/0x2c [rtc_tps65910]
LR is at tps65910_rtc_alarm_irq_enable+0x10/0x2c [rtc_tps65910
On 11/26/2012 4:07 AM, Raghavendra K T wrote:
In some special scenarios like #vcpu <= #pcpu, PLE handler may
prove very costly, because there is no need to iterate over vcpus
and do unsuccessful yield_to burning CPU.
The first patch optimizes all the yield_to by bailing out when there
is n
On Thu, Nov 29, 2012 at 10:45 AM, Nitin Gupta wrote:
> On 11/28/2012 05:33 PM, Minchan Kim wrote:
>>
>> On Wed, Nov 28, 2012 at 02:15:05PM +0900, Minchan Kim wrote:
>>>
>>> Hi Nitin,
>>>
>>> On Mon, Nov 26, 2012 at 11:26:07PM -0800, Nitin Gupta wrote:
The commit c8f2f0db1 ("zram: Fix han
On Wed, 28 Nov 2012, Linus Torvalds wrote:
> A bigger issue is for things that emulate what blkdev.c does, and
> doesn't do the locking. I see code in md/bitmap.c that seems a bit
> suspicious, for example. That said, it's not *new* breakage, and the
> "lock at mmap/read/write() time" approach d
Nico Williams, on 11/26/2012 03:05 PM wrote:
Vlad,
You keep saying that programmers don't understand "barriers". You've
provided no evidence of this. Meanwhile memory barriers are generally
well understood, and every programmer I know understands that a
"barrier" is a synchronization primitive
On 11/28/2012 5:09 PM, Chegu Vinod wrote:
On 11/27/2012 6:23 AM, Chegu Vinod wrote:
On 11/27/2012 2:30 AM, Raghavendra K T wrote:
On 11/26/2012 07:05 PM, Andrew Jones wrote:
On Mon, Nov 26, 2012 at 05:37:54PM +0530, Raghavendra K T wrote:
From: Peter Zijlstra
In case of undercomitted scenar
The original sa1100_rtc_open/sa1100_rtc_release will be called
when the /dev/rtc0 is opened or closed.
In fact, these two functions will enable/disable the clock, and
register/unregister the irqs.
User application will use /dev/rtc0 to read the rtc time or set
the alarm. The rtc should still run in
The original calculation does not take care of week-of-month and
day-of-week. It will make rdar/rdcr not matched when set the
alarm.
Signed-off-by: Chao Xie
---
drivers/rtc/rtc-pxa.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/drivers/rtc/rtc-pxa.c b/drivers
the pxa95x rtc need access PBSR register before write to
RTTR, RCNR, RDCR, and RYCR registers.
Signed-off-by: Chao Xie
---
drivers/rtc/rtc-pxa.c | 97 +++--
1 files changed, 85 insertions(+), 12 deletions(-)
diff --git a/drivers/rtc/rtc-pxa.c b/driv
The mm-of-the-moment snapshot 2012-11-28-18-24 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On 2012/11/29 7:52, Andrew Morton wrote:
> On Wed, 21 Nov 2012 23:09:46 +0800
> Jiang Liu wrote:
>
>> Subject: Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of
>> pages occupied by memmap
>
> How are people to test this? "does it boot"?
>
I have tested this in x86_64, it does
The original pxa_rtc_open/pxa_rtc_release will be called
when the /dev/rtc0 is opened or closed.
In fact, these two functions will register/unregister the irqs.
User application will use /dev/rtc0 to read the rtc time or set
the alarm. The rtc should still run indepent of open/close the
rtc device.
On 2012-11-29 9:42, Jaegeuk Hanse wrote:
> On Wed, Nov 28, 2012 at 04:47:42PM +0800, Jiang Liu wrote:
>> Hi all,
>> Seems it's a great chance to discuss about the memory hotplug feature
>> within this thread. So I will try to give some high level thoughts about
>> memory
>> hotplug feature on
On Wed, 2012-11-28 at 16:06 -0300, Ezequiel Garcia wrote:
> On Tue, Oct 23, 2012 at 4:57 PM, Ezequiel Garcia
> wrote:
> > This is a large patchset that replaces struct memcpy with struct assignment,
> > whenever possible at drivers/media.
[]
> > A simplified version of the semantic match that fin
From: Wei Yongjun
The dereference to 'state' should be moved below the NULL test.
Signed-off-by: Wei Yongjun
---
drivers/staging/sb105x/sb_pci_mp.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/sb105x/sb_pci_mp.c
b/drivers/staging/sb105x/sb_pci_mp.c
ind
On Wed, Nov 28, 2012 at 05:22:03PM -0800, Hugh Dickins wrote:
> Revert 3.5's f21f8062201f ("tmpfs: revert SEEK_DATA and SEEK_HOLE")
> to reinstate 4fb5ef089b28 ("tmpfs: support SEEK_DATA and SEEK_HOLE"),
> with the intervening additional arg to generic_file_llseek_size().
>
> In 3.8, ext4 is expec
Hi Sakari,
Thanks for the quick review.
On Thu, Nov 29, 2012 at 1:38 AM, Sakari Ailus wrote:
> On Wed, Nov 28, 2012 at 04:25:32PM +0530, Prabhakar Lad wrote:
>> From: Manjunath Hadli
>>
>> enable PPCR, enbale ISIF out on BCR and disable all events to
>> get the correct operation from ISIF.
>>
>
Some more fixes trickled in over the past few days:
1) PIM device names can overflow the IFNAMSIZ buffer unless we
properly limit the allowed indexes, fix from Eric Dumazet.
2) Under heavy load we can OOPS in icmp reply processing due to
an unchecked inet_putpeer() call. Fix from Neal Car
On Wed, Nov 28, 2012 at 6:04 PM, Linus Torvalds
wrote:
>
> Interesting. The code *has* the block size (it's in "bh->b_size"), but
> it actually then uses the inode blocksize instead, and verifies the
> two against each other. It could just have used the block size
> directly (and then used the ino
On 2012-11-29 10:49, Wanpeng Li wrote:
> On Thu, Nov 29, 2012 at 10:25:40AM +0800, Jiang Liu wrote:
>> On 2012-11-29 9:42, Jaegeuk Hanse wrote:
>>> On Wed, Nov 28, 2012 at 04:47:42PM +0800, Jiang Liu wrote:
Hi all,
Seems it's a great chance to discuss about the memory hotplug feature
>
Hi Paul,
Today's linux-next merge of the rcu tree got a conflict in
arch/x86/kernel/ptrace.c between commit cb57a2b4cff7 ("x86-32: Export
kernel_stack_pointer() for modules") from Linus' tree and commit
98dbec158343 ("context_tracking: New context tracking susbsystem") from
the rcu tree.
I fixed
On 11/29/2012 08:04 AM, Marcelo Tosatti wrote:
> On Wed, Nov 28, 2012 at 08:54:14PM +0800, Xiao Guangrong wrote:
>> vmcs->cpu indicates whether it exists on the target cpu, -1 means the vmcs
>> does not exist on any vcpu
>>
>> If vcpu load vmcs with vmcs.cpu = -1, it can be directly added to cpu's
Hi Mauro,
On Thu, Nov 29, 2012 at 1:05 AM, Mauro Carvalho Chehab
wrote:
> Hi Laurent,
>
> Em Wed, 28 Nov 2012 14:00:14 +0100
> Laurent Pinchart escreveu:
>
>> Hi Mauro,
>>
>> Please see below.
>>
>> On Wednesday 28 November 2012 09:22:13 Mauro Carvalho Chehab wrote:
>> > Hi Prabhakar,
>> >
>> >
Joe,
Possibly your customer is running a kernel without source code on
a platform whose vendor wouldn't like to fix BIOS issue( Is that a
HP/Dell server ?).
Anyway, to see if is a payload issue or, you could change the
payload size with setpci tool to those devices and set the link
retrain
Hi Konrad,
After merging the xen-two tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
arch/x86/xen/enlighten.c: In function 'init_hvm_pv_info':
arch/x86/xen/enlighten.c:1617:16: warning: unused variable 'ebx'
[-Wunused-variable]
arch/x86/xen/enlighten.c:1617:11: warnin
From: Qing Xu
Add irqdomains for max8925's main irq, wrap irq register operations
into irqdomain's map func. it is necessary for dt support.
Also, add dt support for max8925 driver.
Signed-off-by: Qing Xu
---
drivers/mfd/max8925-core.c | 69 ++-
driv
3.6.7-rt18: kernel BUG at .../kernel/sched/core.c:3817!
Grant reported this same problem for 3.6.5-rt15.
I am seeing it on a different arm board.
Here is the BUG_ON():
asmlinkage void __sched preempt_schedule_irq(void)
{
struct thread_info *ti = current_thread_info();
/*
From: Qing Xu
add max8925 dts support into mmp2 brownstone platform
Signed-off-by: Qing Xu
---
arch/arm/boot/dts/mmp2-brownstone.dts | 158 +
arch/arm/boot/dts/mmp2.dtsi |4 +-
2 files changed, 161 insertions(+), 1 deletions(-)
diff --git a/arch/
From: Qing Xu
add max8925 dts support into mmp2 brownstone platform
Signed-off-by: Qing Xu
---
arch/arm/boot/dts/mmp2-brownstone.dts | 158 +
arch/arm/boot/dts/mmp2.dtsi |4 +-
2 files changed, 161 insertions(+), 1 deletions(-)
diff --git a/arch/
On Wed, Nov 28, 2012 at 05:27:51PM -0800, Anton Vorontsov wrote:
> On Wed, Nov 28, 2012 at 03:14:32PM -0800, Andrew Morton wrote:
> [...]
> > Compare this with the shrink_slab() shrinkers. With these, the VM can
> > query and then control the clients. If something goes wrong or is out
> > of bala
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/dma/dw_dmac.c between commit c4cabfced23f ("dmaengine: dw_dmac:
Enhance device tree support") from the slave-dma tree and commit
463a1f8b3cee ("dma: remove use of __devinit") from the driver-core tree.
I fixed it
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/gpio/gpio-tps6586x.c between commit fe39f2f4dc84 ("mfd: Implement
tps6586x gpio_to_irq") from the mfd tree and commit 3836309d9346 ("gpio:
remove use of __devinit") from the driver-core tree.
I fixed it up (see be
On 29 November 2012 09:10, Stephen Rothwell wrote:
> diff --cc drivers/dma/dw_dmac.c
> +#ifdef CONFIG_OF
> +static struct dw_dma_platform_data *
> +__devinit dw_dma_parse_dt(struct platform_device *pdev)
Do we need a separate patch to fix this place? I believe yes.
> - static int __devinit d
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/mfd/ab8500-core.c between commit 8ae754ebd5ed ("mfd: ab8500-core:
Remove unused ab8500-gpio IRQ ranges") from the mfd tree and commit
a9e9ce4c4167 ("mfd: remove use of __devinitdata") from the driver-core
tree.
I
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/mfd/da9052-core.c between commit 8bad1abd6303 ("mfd: da9052:
Introduce da9052-irq.c") from the mfd tree and commit a9e9ce4c4167 ("mfd:
remove use of __devinitdata") from the driver-core tree.
I fixed it up (see be
On 29/11/12 08:01, Alex Williamson wrote:
On Wed, 2012-11-28 at 18:21 +1100, Alexey Kardashevskiy wrote:
VFIO implements platform independent stuff such as
a PCI driver, BAR access (via read/write on a file descriptor
or direct mapping when possible) and IRQ signaling.
The platform dependent pa
This patch initializes IOMMU groups based on the IOMMU
configuration discovered during the PCI scan on POWERNV
(POWER non virtualized) platform. The IOMMU groups are
to be used later by VFIO driver (PCI pass through).
It also implements an API for mapping/unmapping pages for
guest PCI drivers and
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/mfd/sta2x11-mfd.c between various commits from the mfd tree and
commits f791be492f76 ("mfd: remove use of __devinit"), a9e9ce4c4167
("mfd: remove use of __devinitdata") and a73e5df16b52 ("mfd: remove use
of __devin
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/mfd/tps65090.c between various commits from the mfd tree and
commits 84449216b01f ("mfd: remove use of __devexit_p"), f791be492f76
("mfd: remove use of __devinit") and 4740f73fe538 ("mfd: remove use of
__devexit")
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/pci/pci.h between commit 4e15c46bdc4d ("PCI: Add pci_device_type
to pdev's device struct") from the pci tree and commit b40b97ae736c
("PCI: Remove CONFIG_HOTPLUG ifdefs") from the driver-core tree.
I fixed it up (
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/pci/quirks.c between commit 21c5fd97380b ("PCI: Add workaround
for PLX PCI 9050 BAR alignment erratum") from the pci tree and commit
15856ad50bf5 ("PCI: Remove __dev* markings") from the driver-core tree.
I fixed
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/power/ab8500_btemp.c between commit bd9e8ab2d58d ("ab8500: Add
devicetree support for btemp") from the battery tree and commit
c8afa6406e60 ("power: remove use of __devinit") from the driver-core tree.
I fixed it
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/power/ab8500_charger.c between commit 4aef72dbb2e8 ("ab8500: Add
devicetree support for charger") from the battery tree and commit
c8afa6406e60 ("power: remove use of __devinit") from the driver-core tree.
I fixed
601 - 700 of 820 matches
Mail list logo
