From: Christoph Hellwig <hch@infradead.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Mike Frysinger <vapier@gentoo.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: [patch] use __asm__ and __volatile__ in i386/arm/s390 byteorder.h
Date: Tue, 19 Jun 2007 05:15:27 +0100 [thread overview]
Message-ID: <20070619041527.GA7224@infradead.org> (raw)
In-Reply-To: <20070618190009.GB25340@uranus.ravnborg.org>
On Mon, Jun 18, 2007 at 09:00:09PM +0200, Sam Ravnborg wrote:
> Do you imply that if we see asm or __asm__ in user space headers we ougth
> to warn about it?
> Seems at least sensible to me but if we introduce such a check we should
> kill all offenders first - which Mike's patches seems to trigger for some part.
Yes, we should kill the offenders first. Some of Mike's patches are moving
nicely in that directions. The biggest problem from my POV is byteawap.h
that gets dragged in in various places right now and needs to be sorted out.
next prev parent reply other threads:[~2007-06-19 4:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 22:33 [patch] use __asm__ and __volatile__ in i386/arm/s390 byteorder.h Mike Frysinger
2007-06-17 22:51 ` Arjan van de Ven
2007-06-17 23:24 ` Arnd Bergmann
2007-06-17 23:55 ` Mike Frysinger
2007-06-18 8:51 ` David Woodhouse
2007-06-18 18:11 ` Christoph Hellwig
2007-06-18 18:21 ` Mike Frysinger
2007-06-18 18:34 ` Christoph Hellwig
2007-06-18 18:39 ` Christoph Hellwig
2007-06-18 19:00 ` Sam Ravnborg
2007-06-19 4:15 ` Christoph Hellwig [this message]
[not found] <fa.Xa4Tv0RVV3kUIdHC69Jp/LpQPcg@ifi.uio.no>
[not found] ` <fa.D5W5QzyAnzzOD5Ln35+YDQKzWsE@ifi.uio.no>
[not found] ` <fa.XhJVn2uLXM0A6yjcYTr2E44DELQ@ifi.uio.no>
[not found] ` <fa.tGqwq8EAmSwz5rSn2D2AkvD+yt0@ifi.uio.no>
2007-06-18 14:27 ` Robert Hancock
2007-06-18 17:57 ` H. Peter Anvin
2007-06-18 18:12 ` Christoph Hellwig
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=20070619041527.GA7224@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sam@ravnborg.org \
--cc=vapier@gentoo.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