From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
ludovic.desroches@atmel.com
Cc: linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
patrice.vilchez@atmel.com
Subject: Re: [RFC PATCH 1/9] mmc: atmel-mci: change namespace
Date: Mon, 01 Aug 2011 16:19:52 +0100 [thread overview]
Message-ID: <4E36C418.1060604@atmel.com> (raw)
In-Reply-To: <20110730074807.GH25658@game.jcrosoft.org>
On 07/30/2011 08:48 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 16:29 Thu 28 Jul , ludovic.desroches@atmel.com wrote:
>> From: Ludovic Desroches<ludovic.desroches@atmel.com>
>>
>> Homogenize namespace to atmci.
>>
>> Signed-off-by: Ludovic Desroches<ludovic.desroches@atmel.com>
> prefer ATMEL_MCI
>
> ATMCI is not clear
Well it is used all over the place in the driver code. It is shorter and
in coherence with what is existing already: I will take ATMCI_ naming by
Ludovic.
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2011-08-01 15:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 14:29 [RFC PATCH 0/9] Add pdc feature to atmel-mci ludovic.desroches
2011-07-28 14:29 ` [RFC PATCH 1/9] mmc: atmel-mci: change namespace ludovic.desroches
2011-07-30 7:48 ` Jean-Christophe PLAGNIOL-VILLARD
2011-08-01 15:19 ` Nicolas Ferre [this message]
2011-07-28 14:29 ` [RFC PATCH 2/9] mmc: atmel-mci: change atmci_readl and atmci_writel macros ludovic.desroches
2011-07-28 14:29 ` [RFC PATCH 3/9] mmc: atmel-mci: indentation ludovic.desroches
2011-07-28 14:29 ` [RFC PATCH 4/9] mmc: atmel-mci: add pdc support and runtime capabilities detection ludovic.desroches
2011-07-28 14:29 ` [RFC PATCH 5/9] mmc: atmel-mci: change atmci_start_command to atmci_send_command ludovic.desroches
2011-07-28 14:29 ` [RFC PATCH 6/9] atmel_pdc: add ATMEL_PDC_SCND_BUF_OFF ludovic.desroches
2011-07-30 8:24 ` Jean-Christophe PLAGNIOL-VILLARD
2011-08-01 15:20 ` Nicolas Ferre
2011-07-28 14:29 ` [RFC PATCH 7/9] mmc: atmel-mci: use ATMEL_PDC_SCND_BUF_OFF instead of a literal value ludovic.desroches
2011-07-28 14:29 ` [RFC PATCH 8/9] mmc: atmel-mci: correct sg buffer size evaluation ludovic.desroches
2011-07-28 14:29 ` [RFC PATCH 9/9] mmc: atmel-mci: fix a potential issue about pending PDC interrupts ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 0/8] Add pdc feature to atmel-mci ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 1/8] mmc: atmel-mci: change namespace ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 2/8] mmc: atmel-mci: change atmci_readl and atmci_writel macros ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 3/8] mmc: atmel-mci: indentation ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 4/8] mmc: atmel-mci: add pdc support and runtime capabilities detection ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 5/8] mmc: atmel-mci: change atmci_start_command to atmci_send_command ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 6/8] mmc: atmel-mci: use ATMEL_PDC_SCND_BUF_OFF instead of a literal value ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 7/8] mmc: atmel-mci: correct sg buffer size evaluation ludovic.desroches
2011-08-11 15:25 ` [PATCH v2 8/8] mmc: atmel-mci: fix a potential issue about pending PDC interrupts ludovic.desroches
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=4E36C418.1060604@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=patrice.vilchez@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