From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: Joachim Eastwood <joachim.eastwood@jotron.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
voice <voice.shen@atmel.com>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [GIT PULL] at91: fixes for 3.6 (take 1)
Date: Mon, 27 Aug 2012 10:03:45 +0200 [thread overview]
Message-ID: <503B29E1.5080901@atmel.com> (raw)
In-Reply-To: <5037A4F3.9090608@atmel.com>
On 08/24/2012 05:59 PM, Nicolas Ferre :
> The following changes since commit d9875690d9b89a866022ff49e3fcea892345ad92:
>
> Linux 3.6-rc2 (2012-08-16 14:51:24 -0700)
>
> are available in the git repository at:
>
> git://github.com/at91linux/linux-at91.git tags/at91-fixes
>
> for you to fetch changes up to 0d4d1e37ca732615717d4434b58682f81a6bb61c:
>
> ARM: at91/feature-removal-schedule: delay at91_mci removal (2012-08-24 10:45:07 +0200)
>
> ----------------------------------------------------------------
> Fixes for AT91 related to:
> - move to sparse IRQ: some drivers were forgotten
> - a build error in sound driver & a DTS typo
> - the delay for removal of old at91_mci driver
>
> ----------------------------------------------------------------
> Bo Shen (1):
> ARM: at91/dts: remove partial parameter in at91sam9g25ek.dts
>
> Joachim Eastwood (1):
> ASoC: atmel-ssc: include linux/io.h for raw io
Hi,
As per Mark's suggestion, this one will go through ASoC tree. So I have
removed it from the tag. I resend a pull request now.
Best regards,
> Ludovic Desroches (3):
> ARM: at91: fix system timer irq issue due to sparse irq support
> ARM: at91: fix rtc-at91sam9 irq issue due to sparse irq support
> ARM: at91/feature-removal-schedule: delay at91_mci removal
>
> Nicolas Ferre (1):
> ARM: at91/clock: fix PLLA overclock warning
>
> Documentation/feature-removal-schedule.txt | 2 +-
> arch/arm/boot/dts/at91sam9g25ek.dts | 2 +-
> arch/arm/mach-at91/at91rm9200_time.c | 2 +-
> arch/arm/mach-at91/at91sam9260_devices.c | 6 +++++-
> arch/arm/mach-at91/at91sam9261_devices.c | 6 +++++-
> arch/arm/mach-at91/at91sam9263_devices.c | 10 ++++++++--
> arch/arm/mach-at91/at91sam9g45_devices.c | 6 +++++-
> arch/arm/mach-at91/at91sam9rl_devices.c | 6 +++++-
> arch/arm/mach-at91/clock.c | 12 ++++++++++++
> drivers/rtc/rtc-at91sam9.c | 22 +++++++++++++++-------
> include/linux/atmel-ssc.h | 1 +
> 11 files changed, 59 insertions(+), 16 deletions(-)
>
> Thanks, best regards,
>
--
Nicolas Ferre
next prev parent reply other threads:[~2012-08-27 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 15:59 [GIT PULL] at91: fixes for 3.6 (take 1) Nicolas Ferre
2012-08-27 8:03 ` Nicolas Ferre [this message]
2012-08-27 8:08 ` [GIT PULL] at91: fixes for 3.6 (take 1 bis) Nicolas Ferre
2012-08-28 0:00 ` Olof Johansson
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=503B29E1.5080901@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=joachim.eastwood@jotron.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
--cc=voice.shen@atmel.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;
as well as URLs for NNTP newsgroup(s).