From: Pierre Ossman <pierre@ossman.eu>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: haavard.skinnemoen@atmel.com,
linux-arm-kernel@lists.arm.linux.org.uk, poorarm@shoreis.com,
linux-kernel@vger.kernel.org, avictor.za@gmail.com,
nicolas.ferre@atmel.com
Subject: Re: [PATCH 1/2] atmel-mci: Integrate AT91 specific definition in header file
Date: Sat, 13 Jun 2009 22:12:00 +0200 [thread overview]
Message-ID: <20090613221200.2e0154c7@mjolnir.ossman.eu> (raw)
In-Reply-To: <1244822310-11562-1-git-send-email-nicolas.ferre@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Fri, 12 Jun 2009 17:58:29 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> The MCI IP is shared among AVR32 and AT91 SOCs.
> AT91 has specific bit definitions in the user interface of MCI SD/MMC IP.
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> Thanks to Rob Emanuele who has begun this unification work. I take the hand on
> this header file work as I have some bits to integrate for MCI2 support.
>
Both patches applied.
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-13 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81b92e58966b864e4a26004204f43d242d9cc8aa.1244821292.git.nicolas.ferre@atmel.com>
2009-06-12 15:58 ` Nicolas Ferre
2009-06-12 15:42 ` Haavard Skinnemoen
2009-06-13 20:12 ` Pierre Ossman [this message]
[not found] ` <a54493d37159af0d7f118934e9e5599979fa2bef.1244821292.git.nicolas.ferre@atmel.com>
2009-06-12 15:58 ` [PATCH 2/2] atmel-mci: add MCI2 register definitions Nicolas Ferre
2009-06-12 15:43 ` Haavard Skinnemoen
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=20090613221200.2e0154c7@mjolnir.ossman.eu \
--to=pierre@ossman.eu \
--cc=avictor.za@gmail.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=poorarm@shoreis.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
all inboxes | Powered by JetHome®