From: Andrew Morton <akpm@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 19/22] x86: use the new byteorder headers
Date: Tue, 12 Aug 2008 23:47:03 -0700 [thread overview]
Message-ID: <20080812234703.4a9adbea.akpm@linux-foundation.org> (raw)
In-Reply-To: <1218607635.30194.115.camel@brick>
On Tue, 12 Aug 2008 23:07:15 -0700 Harvey Harrison <harvey.harrison@gmail.com> wrote:
> On Tue, 2008-08-12 at 23:02 -0700, Andrew Morton wrote:
> > On Tue, 12 Aug 2008 22:56:12 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > > I'll drop them all.
> >
> > btw, I had to rework several of these patches because everyone is
> > moving include/asm-arch/* into arch/include/asm/. Patches against
> > linux-next would be preferred please.
> >
>
> Which arches? These were all against linux-next20080811.
>
The ones which got changed in the past 24 hours I guess ;)
avr32 and xtensa, I think.
Ah, yes, I seem to have picked some trees which aren't in linux-next
for whatever reason. See mmotm's git-parisc.patch and git-xtensa.patch.
prev parent reply other threads:[~2008-08-13 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 0:27 [PATCH 19/22] x86: use the new byteorder headers Harvey Harrison
2008-08-13 3:54 ` Andrew Morton
2008-08-13 4:05 ` [PATCH] tipc: Use the appropriate swab helper rather than an internal helper Harvey Harrison
2008-08-13 4:20 ` Andrew Morton
2008-08-13 4:23 ` Harvey Harrison
2008-08-13 9:32 ` David Miller
2008-08-13 5:56 ` [PATCH 19/22] x86: use the new byteorder headers Andrew Morton
2008-08-13 5:59 ` David Miller
2008-08-13 6:05 ` Andrew Morton
2008-08-13 6:02 ` Andrew Morton
2008-08-13 6:07 ` Harvey Harrison
2008-08-13 6:47 ` Andrew Morton [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=20080812234703.4a9adbea.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.