From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 09/20] m68k: use the new byteorder headers
Date: Wed, 22 Oct 2008 09:01:37 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0810220900230.8356@anakin> (raw)
In-Reply-To: <1224621302.5768.0.camel@brick>
On Tue, 21 Oct 2008, Harvey Harrison wrote:
> On Tue, 2008-10-21 at 20:05 +0200, Geert Uytterhoeven wrote:
> > On Mon, 20 Oct 2008, Harvey Harrison wrote:
> > > Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> > > ---
> > > The final prerequisite patches to prevent breakage of headers-install and
> > > usage of the swabb.h functions have gone into mainline, please move your arch
> > > to the new header.
> > >
> > > b8e465f4945bc0e9f324e3bbe15f5180a8e9a6fe byteorder: add new headers for make headers-install
> > > acf0108a84edae22b99655eb2f6f6c9f7ec4d449 byteorder: use generic C version for value byteswapping
> > > 1d8cca44b6a244b7e378546d719041819049a0f9 byteorder: provide swabb.h generically in asm/byteorder.h
> > > 1a651a00e20fd4997f0b91258f6f95b7d96edcd9 byteorder: remove direct includes of linux/byteorder/swab[b].h
> > >
>
> A hunk got lost, see mainline:
>
> > commit f07767fd0f95c385108fa4c456a9cb216a424fec
> > Author: Harvey Harrison <harvey.harrison@gmail.com>
> > Date: Mon Oct 20 10:23:38 2008 -0700
> >
> > byteorder: remove direct includes of linux/byteorder/swab[b].h
> >
> > A consolidated implementation will provide this generically through
> > asm/byteorder, remove direct includes to avoid breakage when the
> > changeover to the new implementation occurs.
> >
> > This hunk was lost from commit 1d8cca44b6a244b7e378546d719041819049a0f9
> > ("byteorder: provide swabb.h generically in asm/byteorder.h")
> >
> > Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> > Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Ah, my tree didn't have that one yet.
After upgrading, kernel/rcutorture.c compiles again.
I'll let you know if more breakage pops up (I expect not, as I built
with `make -k' ;-).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2008-10-22 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1224525138.31861.206.camel@brick>
2008-10-21 18:05 ` Geert Uytterhoeven
2008-10-21 20:35 ` Harvey Harrison
2008-10-22 7:01 ` Geert Uytterhoeven [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=Pine.LNX.4.64.0810220900230.8356@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--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
all inboxes | Powered by JetHome®