Re: [PATCH] mvebu : pcie: dt: potential issue in range parsing

2014-02-14 Thread Bjorn Helgaas
On Wed, Feb 05, 2014 at 12:21:07PM -0500, Jason Cooper wrote: > > + Bjorn, linux-pci > > Bjorn, > > It looks like this didn't get Cc'd to linux-pci. Here's a link: > > http://www.spinics.net/lists/arm-kernel/msg299721.html Thanks for the heads-up; I had indeed missed this (I mostly rely on

Re: [PATCH] mvebu : pcie: dt: potential issue in range parsing

2014-02-05 Thread Jason Cooper
+ Bjorn, linux-pci Bjorn, It looks like this didn't get Cc'd to linux-pci. Here's a link: http://www.spinics.net/lists/arm-kernel/msg299721.html On Wed, Feb 05, 2014 at 04:47:10PM +0100, Thomas Petazzoni wrote: > Dear Jean-Jacques Hiblot, > > On Fri, 10 Jan 2014 11:23:51 +0100, Jean-Jacque

Re: [PATCH] mvebu : pcie: dt: potential issue in range parsing

2014-02-05 Thread Thomas Petazzoni
Dear Jean-Jacques Hiblot, On Fri, 10 Jan 2014 11:23:51 +0100, Jean-Jacques Hiblot wrote: > The second parameter of of_read_number is not the index, but a size. > As it happens, in this case it may work just fine because of the the > conversion > to u32 and the favorable endianness on this archite

Re: [PATCH] mvebu : pcie: dt: potential issue in range parsing

2014-02-04 Thread Jason Cooper
Jean-Jacques, On Fri, Jan 10, 2014 at 11:23:51AM +0100, Jean-Jacques Hiblot wrote: > The second parameter of of_read_number is not the index, but a size. > As it happens, in this case it may work just fine because of the the > conversion > to u32 and the favorable endianness on this architecture.

[PATCH] mvebu : pcie: dt: potential issue in range parsing

2014-01-10 Thread Jean-Jacques Hiblot
The second parameter of of_read_number is not the index, but a size. As it happens, in this case it may work just fine because of the the conversion to u32 and the favorable endianness on this architecture. Signed-off-by: Jean-Jacques Hiblot --- drivers/pci/host/pci-mvebu.c | 2 +- 1 file change