From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH] mtd: only use __xipram annotation when XIP_KERNEL is set
Date: Sat, 05 Mar 2016 09:45:21 +0100 [thread overview]
Message-ID: <8737s5wbxa.fsf@belgarion.home> (raw)
In-Reply-To: <3582240.H8v1IXn8EB@wuerfel> (Arnd Bergmann's message of "Sat, 05 Mar 2016 01:24:36 +0100")
Arnd Bergmann <arnd@arndb.de> writes:
> I guess we can bring back the macros for the case that MTD_XIP and XIP_KERNEL
> are both enabled.
>
> Arnd
I wouldn't have ICMR and ICIP exposed to drivers, Eric's original move looks
corect to me.
On the other hand, I'm wondering if xip_irqpending(), xip_currtime() and
xip_cpu_idle() should be declared as functions in mtd-xip.h, and be part of
something like arch/arm/mach-pxa/xip.c ...
Cheers.
--
Robert
next prev parent reply other threads:[~2016-03-05 8:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:41 [PATCH] mtd: only use __xipram annotation when XIP_KERNEL is set Arnd Bergmann
2016-03-05 0:02 ` Brian Norris
2016-03-05 0:10 ` Brian Norris
2016-03-05 0:10 ` Brian Norris
2016-03-05 0:24 ` Arnd Bergmann
2016-03-05 0:24 ` Arnd Bergmann
2016-03-05 8:45 ` Robert Jarzmik [this message]
2016-03-06 19:56 ` Arnd Bergmann
2016-03-05 0:19 ` Arnd Bergmann
2016-03-05 0:22 ` Brian Norris
2016-03-05 0:22 ` Brian Norris
2016-03-05 0:28 ` David Woodhouse
2016-03-05 0:43 ` Brian Norris
2016-03-17 15:56 ` Arnd Bergmann
2016-03-17 15:56 ` Arnd Bergmann
2016-03-05 0:33 ` Arnd Bergmann
2016-03-05 0:33 ` Arnd Bergmann
2016-03-07 16:43 ` Tony Lindgren
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=8737s5wbxa.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=arnd@arndb.de \
--cc=computersforpeace@gmail.com \
--cc=daniel@zonque.org \
--cc=dwmw2@infradead.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).