From: Rob Emanuele <poorarm@shoreis.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Andrew Victor <avictor.za@gmail.com>,
Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
Joey Oravec <joravec@drewtech.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx
Subject: Re: [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports both MCI slots used at the same time
Date: Fri, 12 Jun 2009 11:18:10 -0700 [thread overview]
Message-ID: <c8284b5b0906121118r413bff3frd4a1d9e12e76bfca@mail.gmail.com> (raw)
In-Reply-To: <4A3219F6.6000300@atmel.com>
Hi Nicolas & Haavard,
>> Well, what is the best way to differentiate it from the at91_mci
>> driver and keep users from trying to use both drivers?
>
> I propose that we setup a kind of choice sub menu in the Kconfig for
> those two drivers when they are both supported.
>
I'll try Haavard's suggestion of making the 2 drivers mutually
exclusive and I'll remove "Unified" verbiage.
>> Who would that be as I haven't seen anyone who maintains any of those
>> boards other than the at91rm8200 (at least nothing listed in the
>> MAINTAINERS file)? The board-sam9g20ek.c platform only shows Atmel as
>> the most recent copyright.
>
> Hey, AT91 are very well maintained, SAM9 as well as at91rm9200.
> So, AT91 specific bits should be sent to this mailing-list with Andrew
> Victor in copy.
I never meant to imply that they were not maintained or even not
maintained well, only that the maintainer's contact information was
not obvious. Below is a patch to correct that listing for Andrew
Victor.
> I will also certainly add comments on this code.
>
I appreciate any comments you have.
--Rob
diff --git a/MAINTAINERS b/MAINTAINERS
index 5d460c9..a3bc13b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -472,7 +472,7 @@ M: kernel@wantstofly.org
L: linux-arm-kernel@lists.arm.linux.org.uk (subscribers-only)
S: Maintained
-ARM/ATMEL AT91RM9200 ARM ARCHITECTURE
+ARM/ATMEL AT91RM9200 & AT91SAM9* ARM ARCHITECTURES
P: Andrew Victor
M: linux@maxim.org.za
L: linux-arm-kernel@lists.arm.linux.org.uk (subscribers-only)
next prev parent reply other threads:[~2009-06-12 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 23:41 [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports both MCI slots used at the same time (was: [PATCH][Updated] New AT91 MCI Driver that supports both MCI slots used at the same time) Rob Emanuele
2009-06-11 7:54 ` [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports both MCI slots used at the same time Haavard Skinnemoen
2009-06-11 20:16 ` Rob Emanuele
2009-06-12 9:03 ` Nicolas Ferre
2009-06-12 9:29 ` Haavard Skinnemoen
2009-06-15 14:51 ` Nicolas Ferre
2009-06-12 18:18 ` Rob Emanuele [this message]
2009-06-12 12:37 ` 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=c8284b5b0906121118r413bff3frd4a1d9e12e76bfca@mail.gmail.com \
--to=poorarm@shoreis.com \
--cc=avictor.za@gmail.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=joravec@drewtech.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@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
all inboxes | Powered by JetHome®