On 09/12/2010 08:27 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the scsi-post-merge tree, today's linux-next build (powerpc
> allnoconfig, i386 defconfig and others) produced these warnings (I build
> with CONFIG_DEBUG_SECTION_MISMATCH=y):
>
> WARNING: mm/built-in.o(.text+0x25910): Se
On Sun, Sep 12, 2010 at 05:10:35PM +0200, André Schwarz wrote:
> > > BTW: would "drivers/misc" be a proper location ?
> > > Who's supposed to pick that driver up and on what list shall I post it
> > > for review ?
> >
> > You should cc spi-devel-general, and feel free to cc me. drivers/misc
> > w
Hi Yinghai,
On Sun, 12 Sep 2010 21:14:15 -0700 Yinghai Lu wrote:
>
> please check it, and it should get into core/memblock branch.
>
> Thanks
>
> Yinghai
>
> [PATCH] memblock: Fix section mismatch warning
>
> for arches that use memblock other than x86
>
> Reported-by: Stephen Rothwell
> Si
Hi all,
After merging the scsi-post-merge tree, today's linux-next build (powerpc
allnoconfig, i386 defconfig and others) produced these warnings (I build
with CONFIG_DEBUG_SECTION_MISMATCH=y):
WARNING: mm/built-in.o(.text+0x25910): Section mismatch in reference from the
function memblock_find_i
On Fri, Sep 10, 2010 at 01:56:08PM +0800, hacklu wrote:
> I didn't understand the address mask.
> it's said that: BR[BA] is the base address,the OR[AM] is the address mask,
...
> for instance, if my BR0[BA]=0111____0, OR0[AM]=__
> if I want to access the 0x7000 or the
hvc_alloc() may fail, if so exit from init() with error.
Signed-off-by: Vasiliy Kulikov
---
I cannot compile this driver at all, so it is not tested.
drivers/char/hvc_tile.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/char/hvc_tile.c b/drivers/char/hvc_
Grant, Anton,
[snip]
> >
> > Doing this in parallel will speed things up significantly.
>
> Yeah; Then I would handle it as a separate cs# and map it to enabling
> multiple CS lines at a time.
sounds reasonable - will do it that way.
>
> > BTW: would "drivers/misc" be a proper location ?
> >
