From: Barry Song <21cnbao@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [Uclinux-dist-devel] [PATCH 1/2] let MTD_XIP depend on XIP_KERNEL or ROMKERNEL
Date: Sat, 16 Jan 2010 14:35:36 +0800 [thread overview]
Message-ID: <3c17e3571001152235o2a77d5b5i8300ce888df3515@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a1001150234u1080572bx89a34221770bb93c@mail.gmail.com>
On Fri, Jan 15, 2010 at 6:34 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Fri, Jan 15, 2010 at 05:29, David Woodhouse wrote:
>> On Fri, 2010-01-15 at 15:50 +0800, Barry Song wrote:
>>> Some architectures like blackfin,h8300,m68k use ROMKERNEL to describe
>>> kernel XIP, not like arm which uses XIP_KERNEL
>>
>> Surely the appropriate response to that realisation is to _fix_ the
>> inconsistency, not just work around it?
>
> agree, but this is a lot easier than trying to tell RMK to change all
> the ARM references ;)
Yes. It will be really difficult to ask the related architectures to change.
>
> this is the only place outside of the respective arch/$ARCH/ where
> either XIP_KERNEL or ROMKERNEL is utilized ...
> -mike
>
next prev parent reply other threads:[~2010-01-16 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 7:50 [PATCH 1/2] let MTD_XIP depend on XIP_KERNEL or ROMKERNEL Barry Song
2010-01-15 7:50 ` [PATCH 2/2] mtd-physmap: add support users can assign the probe type in board files Barry Song
2010-05-23 7:23 ` Mike Frysinger
2010-01-15 10:29 ` [PATCH 1/2] let MTD_XIP depend on XIP_KERNEL or ROMKERNEL David Woodhouse
2010-01-15 10:34 ` [Uclinux-dist-devel] " Mike Frysinger
2010-01-16 6:35 ` Barry Song [this message]
2010-02-02 5:48 ` Artem Bityutskiy
2010-03-22 5:40 ` Barry Song
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=3c17e3571001152235o2a77d5b5i8300ce888df3515@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@gmail.com \
/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