From: Jens Axboe <jens.axboe@oracle.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] cleanup asm/scatterlist.h includes
Date: Tue, 30 Oct 2007 10:35:15 +0100 [thread overview]
Message-ID: <20071030093515.GI4993@kernel.dk> (raw)
In-Reply-To: <20071029145711.GO7227@stusta.de>
On Mon, Oct 29 2007, Adrian Bunk wrote:
> On Mon, Oct 29, 2007 at 02:13:01PM +0100, Jens Axboe wrote:
> > On Mon, Oct 29 2007, Adrian Bunk wrote:
> > > Not architecture specific code should not #include <asm/scatterlist.h>.
> > >
> > > This patch therefore either replaces them with
> > > #include <linux/scatterlist.h> or simply removes them if they were
> > > unused.
> >
> > Looks fine to me - what did you compile test this on?
>
> i386 all static and all modular configs (slightly different from but
> similar to allyesconfig+allmodconfig) and defconfigs of
> 24 architectures (but some of them fail to compile due to different
> problems).
Good, applied!
--
Jens Axboe
prev parent reply other threads:[~2007-10-30 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 12:49 [2.6 patch] cleanup asm/scatterlist.h includes Adrian Bunk
2007-10-29 13:13 ` Jens Axboe
2007-10-29 14:57 ` Adrian Bunk
2007-10-30 9:35 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071030093515.GI4993@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox