From: Adrian Bunk <bunk@kernel.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Sam Ravnborg <sam@ravnborg.org>,
Haavard Skinnemoen <hskinnemoen@atmel.no>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] Fix asm-avr32/dma-mapping.h breakage
Date: Wed, 24 Oct 2007 14:41:23 +0200 [thread overview]
Message-ID: <20071024124123.GD30533@stusta.de> (raw)
In-Reply-To: <20071024122120.GV14671@kernel.dk>
On Wed, Oct 24, 2007 at 02:21:20PM +0200, Jens Axboe wrote:
> On Wed, Oct 24 2007, Robert P. J. Day wrote:
> > On Wed, 24 Oct 2007, Sam Ravnborg wrote:
> >
> > > On Wed, Oct 24, 2007 at 01:24:53PM +0200, Jens Axboe wrote:
> > > > On Wed, Oct 24 2007, Haavard Skinnemoen wrote:
> > > > > Hi Linus,
> > > > >
> > > > > Sorry about sending you pull requests so rapidly, but Jens broke my
> > > > > dma-mapping.h yesterday. Or you may say the bug was there to begin with
> > > > > and Jens merely exposed it, but that makes it sound like my fault ;-)
> > > > >
> > > > > Anyway, please pull from
> > > > >
> > > > > ssh://master.kernel.org/pub/scm/linux/kernel/git/hskinnemoen/avr32-2.6.git for-linus
> > > > >
> > > > > to receive the following update.
> > > >
> > > > You should not take the blame :-)
> > > >
> > > > I'm collecting these patches, so I'll pull your fix and make sure it
> > > > gets to Linus today along with the other fixes.
> > >
> > > How about doing a "git grep asm/scatterlist"
> > > and fix all victims to use linux/scatterlist?
> > > Or you maybe did this already.
> >
> > i was just about to ask -- is this one of those cases where the asm
> > versions of scatterlist.h should have a warning/error that they should
> > not be included directly, and to include linux/scatterlist.h instead?
>
> No, using asm/scatterlist.h is perfectly fine. The problem is code using
> the sg helpers should include linux/scatterlist.h since that is where
> those are defined.
>
> If you just need the scatterlist structure definition, then
> asm/scatterlist.h is the correct include.
But there's also the general question whether it's good practice for
not architecture specific code to include asm/ headers.
For APIs available on all architectures linux/ header are the right
thing to use, and what is in the asm/ header and what in the linux/
header becomes an implementation detail that can be changed.
> Jens Axboe
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-10-24 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 11:22 [GIT PATCH] Fix asm-avr32/dma-mapping.h breakage Haavard Skinnemoen
2007-10-24 11:24 ` Jens Axboe
2007-10-24 11:29 ` Sam Ravnborg
2007-10-24 11:58 ` Jens Axboe
2007-10-24 12:15 ` Robert P. J. Day
2007-10-24 12:21 ` Jens Axboe
2007-10-24 12:41 ` Adrian Bunk [this message]
2007-10-24 12:44 ` Robert P. J. Day
2007-10-24 12:58 ` Jens Axboe
2007-10-24 12:45 ` Jens Axboe
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=20071024124123.GD30533@stusta.de \
--to=bunk@kernel.org \
--cc=hskinnemoen@atmel.no \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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