From: Greg Ungerer <gerg@snapgear.com>
To: Allon Stern <Allon.Stern@argonst.com>
Cc: linux-m68k <linux-m68k@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: Re: Merge headerfiles for m68k and m68knommu to arch/m68k/include/asm
Date: Fri, 12 Dec 2008 15:22:56 +1000 [thread overview]
Message-ID: <4941F530.8000003@snapgear.com> (raw)
In-Reply-To: <EB7A6806-7754-4EB5-8CCB-BCDE7380194D@argonst.com>
Allon Stern wrote:
> On Dec 9, 2008, at 12:39 PM, Geert Uytterhoeven wrote:
>> Sure, but that one is nicely protected by "#if defined
>> (__mcfisaaplus__) ||
>> defined (__mcfisac__)", right?
>
> Well, that was the patch we had to apply.
> It wasn't in the baseline kernel.org kernel.
What kernel.org version?
Its has been in for a little while.
In 2.6.28-rc8:
grep mcfisaaplus arch/m68knommu/include/asm/*
arch/m68knommu/include/asm/bitops.h:#if defined (__mcfisaaplus__) ||
defined (__mcfisac__)
arch/m68knommu/include/asm/byteorder.h:#if defined (__mcfisaaplus__) ||
defined (__mcfisac__)
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear, a McAfee Company PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
next prev parent reply other threads:[~2008-12-12 5:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081208205814.GA22697@uranus.ravnborg.org>
2008-12-08 22:53 ` Merge headerfiles for m68k and m68knommu to arch/m68k/include/asm Sam Ravnborg
2008-12-08 23:01 ` Geert Uytterhoeven
2008-12-08 23:26 ` Arnd Bergmann
2008-12-09 5:45 ` Sam Ravnborg
2008-12-09 8:24 ` Geert Uytterhoeven
2008-12-09 9:45 ` Andreas Schwab
2008-12-09 11:02 ` Arnd Bergmann
2008-12-09 18:04 ` Sam Ravnborg
2008-12-11 8:33 ` Geert Uytterhoeven
2008-12-11 9:38 ` Andreas Schwab
2008-12-11 16:48 ` Arnd Bergmann
2008-12-11 20:16 ` Geert Uytterhoeven
2008-12-13 16:16 ` Arnd Bergmann
2008-12-12 5:40 ` Greg Ungerer
2008-12-13 20:46 ` Sam Ravnborg
2008-12-13 20:43 ` Sam Ravnborg
2008-12-09 16:54 ` Allon Stern
2008-12-09 17:39 ` [uClinux-dev] " Geert Uytterhoeven
2008-12-11 15:44 ` Allon Stern
2008-12-12 5:22 ` Greg Ungerer [this message]
2008-12-13 20:52 ` Sam Ravnborg
[not found] ` <20081213205251.GC27748@uranus.ravnborg.org>
[not found] ` <20081213205828.GD27748@uranus.ravnborg.org>
2008-12-14 16:13 ` [PATCH] m68k,m68knommu: merge header files Geert Uytterhoeven
[not found] ` <49707AE0.1040803@opengear.com>
2009-01-16 12:57 ` Geert Uytterhoeven
2009-01-16 14:21 ` Greg Ungerer
2009-01-16 14:34 ` Sam Ravnborg
2009-01-16 21:53 ` Geert Uytterhoeven
2009-01-16 22:19 ` Greg Ungerer
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=4941F530.8000003@snapgear.com \
--to=gerg@snapgear.com \
--cc=Allon.Stern@argonst.com \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
--cc=zippel@linux-m68k.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