From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Rob Emanuele <poorarm@shoreis.com>
Cc: 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 14:37:32 +0200 [thread overview]
Message-ID: <4A324C0C.8070302@atmel.com> (raw)
In-Reply-To: <c8284b5b0906111316p1367a508vdb59ee7c2a8d2ff1@mail.gmail.com>
Rob Emanuele :
>> - The patch seems to do a bit too much all at once. The bug fix which
>> has already been fixed is one example, another is the clock cap
>> option -- we used to have a module parameter for the same purpose,
>> but Pierre (the MMC maintainer, who should probably be added to the
>> loop) had problems with it. If this feature was in a separate
>> patch, it could be rejected without blowing away the rest of the
>> driver.
>
> Which kernel branch should I generate the patch against to have the
> most recent set of changes?
I think that you can use current (today) linus' git tree with this
additional patch from Haavard in avr32 tree
"Add support for inverted detect pin":
http://git.kernel.org/?p=linux/kernel/git/hskinnemoen/avr32-2.6.git;a=commit;h=1c1452be2e9ae282a7316c3b23987811bd7acda6
Kind regards,
--
Nicolas Ferre
prev parent reply other threads:[~2009-06-12 12:38 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
2009-06-12 12:37 ` Nicolas Ferre [this message]
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=4A324C0C.8070302@atmel.com \
--to=nicolas.ferre@atmel.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=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