[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9c3a7c20805091155w741fc8eai761fa232bb27dedf@mail.gmail.com>
Date: Fri, 9 May 2008 11:55:25 -0700
From: "Dan Williams" <dan.j.williams@...el.com>
To: "Sebastian Siewior" <lkml@...breakpoint.cc>
Cc: "Maciej Sosnowski" <maciej.sosnowski@...el.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [ASYNC_TX] don't include <asm/> headers
On Fri, May 9, 2008 at 1:39 AM, Sebastian Siewior <lkml@...breakpoint.cc> wrote:
> * Dan Williams | 2008-04-29 23:42:46 [-0700]:
>
>
> >Thanks, I'll push this out for testing in -next / -mm.
> I can't see this in current -next and I can't remember that I got an
> email from Andrew.
>
Hi Sebastian,
Yes I had put this in the background for awhile due to other issues.
I fixed up a few merge conflicts so that it will apply against the
current tree; however, the patch causes these new warnings:
include/asm/xor_32.h:513: warning: 'xor_block_pII_mmx' defined but not used
include/asm/xor_32.h:521: warning: 'xor_block_p5_mmx' defined but not used
include/asm/xor_32.h:853: warning: 'xor_block_pIII_sse' defined but not used
include/asm-generic/xor.h:680: warning: 'xor_block_8regs' defined but not used
include/asm-generic/xor.h:688: warning: 'xor_block_32regs' defined but not used
include/asm-generic/xor.h:696: warning: 'xor_block_8regs_p' defined but not used
include/asm-generic/xor.h:704: warning: 'xor_block_32regs_p' defined
but not used
It is not immediately clear why?
--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists