public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-mmc@vger.kernel.org,
	"'linux-arm-kernel@lists.infradead.org'"
	<linux-arm-kernel@lists.infradead.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Ludovic Desroches <ludovic.desroches@atmel.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] mmc: atmel rework for next
Date: Fri, 19 Aug 2011 13:03:47 -0400	[thread overview]
Message-ID: <m24o1dnxjg.fsf@bob.laptop.org> (raw)
In-Reply-To: <4E4A8E73.7050705@atmel.com> (Nicolas Ferre's message of "Tue, 16 Aug 2011 17:36:19 +0200")

Hi,

On Tue, Aug 16 2011, Nicolas Ferre wrote:
> Hi Chris,
>
> Please pull from:
>
> git://github.com/at91linux/linux-2.6-at91.git nfe/mmc_atmel
>
> This is a series that reworks the atmel-mci driver for a future merge of both at91_mci and atmel-mci drivers. Those patches have been discussed on the mailing-list.
> I added a tiny at91_mci patch also sent last week.

Thanks, all looks good -- pushed to mmc-next with some commit message
rewording.  Please wrap your commit messages to 75 cols in future, so
that they're viewable in "git log" without wrapping.

I'll repeat your warning text from one of the commit messages here for
the broader audience:

    Warning: at91rm9200 is not supported, to support it we need to use
    swab32 on data but I have no board to test it.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-08-19 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 15:36 [GIT PULL] mmc: atmel rework for next Nicolas Ferre
2011-08-19 17:03 ` Chris Ball [this message]
2011-08-22  8:28   ` Nicolas Ferre

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=m24o1dnxjg.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=plagnioj@jcrosoft.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