From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [AT91 PULL] ioremap pull request for 3.3
Date: Tue, 29 Nov 2011 03:03:38 +0100 [thread overview]
Message-ID: <20111129020338.GJ15008@game.jcrosoft.org> (raw)
In-Reply-To: <201111281846.22837.arnd@arndb.de>
On 18:46 Mon 28 Nov , Arnd Bergmann wrote:
> On Wednesday 23 November 2011, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > this pull containt the first patch series that rework the base address
> > of a lots of drivers (aic, rtc, gpio, ecc, dma, rtt, pit, smc, shutdown, watchdog, dbgu)
> > to allow the multi soc and simplify the adding of the DT
> >
> > The following changes since commit 8454badc89ed455990b1a060d9e4ed890b9e162c:
> >
> > ARM: at91: rename at91sam9260ek_defconfig to at91sam9260_defconfig (2011-11-23 02:45:57 +0800)
> >
> > are available in the git repository at:
> > git://github.com/at91linux/linux-at91.git for-arnd-3.3-ioremap
>
> Applied into next/cleanup, thanks!
>
> I noticed that you introduce a bunch of new references to __raw_writel
> when you get rid of at91_sys_write uses in drivers. This is obviously
> the safe choice since it keeps the code behavior close to what it was.
>
> However, I think it would be good to use writel_relaxed there,
> to make the accesses more well-defined. Maybe you can do an add-on
> patch to convert the various new accessor macros over to that.
I've a pull for the reset and DT to prepare first and will do
Best Regards,
J.
prev parent reply other threads:[~2011-11-29 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 17:10 [AT91 PULL] ioremap pull request for 3.3 Jean-Christophe PLAGNIOL-VILLARD
2011-11-28 18:46 ` Arnd Bergmann
2011-11-29 2:03 ` Jean-Christophe PLAGNIOL-VILLARD [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=20111129020338.GJ15008@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=linux-arm-kernel@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).