From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] pcmcia: at91_cf: clean up and add DT support
Date: Wed, 17 Apr 2013 10:51:23 +0200 [thread overview]
Message-ID: <516E628B.1000104@atmel.com> (raw)
In-Reply-To: <CAHkwnC-aL=G9K9jttjD8Bk_ZKJ535vsGT26uCFbuFMeJUquYQw@mail.gmail.com>
On 04/17/2013 10:39 AM, Fabio Porcedda :
> On Thu, Mar 21, 2013 at 12:40 PM, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
>> These patches clean up at91_cf a bit and add DT bindings.
>> It is based on a previous series from Joachim Eastwood and other cleanup
>> patches by Fabio and Laurent.
>> I have collected them together as they are lying around for some time.
>>
>> Please tell me if It can go through PCMCIA tree or if Andrew or Greg can
>> take them.
>> Note that they are not bug fixes, so you can stack them for 3.10.
>>
>> Thanks for your help, best regards.
>>
>> v2: add 2 more cleanup patches:
>> - move to module_platform_driver_probe()
>> - little trivial indentation fix
>>
>> Fabio Porcedda (1):
>> pcmcia: at91_cf: use module_platform_driver_probe()
>>
>> Joachim Eastwood (5):
>> pcmcia: at91_cf: fix gpio_get_value in at91_cf_get_status
>> pcmcia: at91_cf: convert to dev_ print functions
>> pcmcia: at91_cf: use devm_ functions for allocations
>> pcmcia: at91_cf: clean up header includes
>> pcmcia: at91_cf: add support for DT
>>
>> Laurent Navet (1):
>> pcmcia/trivial: at91_cf: fix checkpatch error
>>
>> .../devicetree/bindings/ata/atmel-at91_cf.txt | 19 +++
>> drivers/pcmcia/Kconfig | 2 +-
>> drivers/pcmcia/at91_cf.c | 176 ++++++++++-----------
>> 3 files changed, 108 insertions(+), 89 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/ata/atmel-at91_cf.txt
>>
>> --
>> 1.8.0
>>
>
> Ping?
Andrew, Greg, can you please take this series?
Here is the post on lkml:
https://lkml.org/lkml/2013/3/21/246
Here is the first patch in patchwork (1/7):
https://patchwork.kernel.org/patch/2312691/
Tell me if I can do something else to make this applied upstream...
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2013-04-17 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 11:40 [PATCH v2 0/7] pcmcia: at91_cf: clean up and add DT support Nicolas Ferre
2013-03-21 11:40 ` [PATCH v2 1/7] pcmcia: at91_cf: fix gpio_get_value in at91_cf_get_status Nicolas Ferre
2013-03-21 11:40 ` [PATCH v2 2/7] pcmcia: at91_cf: convert to dev_ print functions Nicolas Ferre
2013-03-21 11:40 ` [PATCH v2 3/7] pcmcia: at91_cf: use devm_ functions for allocations Nicolas Ferre
2013-03-21 11:40 ` [PATCH v2 4/7] pcmcia: at91_cf: clean up header includes Nicolas Ferre
2013-03-21 11:40 ` [PATCH v2 5/7] pcmcia: at91_cf: add support for DT Nicolas Ferre
2013-03-21 11:40 ` [PATCH v2 6/7] pcmcia: at91_cf: use module_platform_driver_probe() Nicolas Ferre
2013-03-21 11:40 ` [PATCH v2 7/7] pcmcia/trivial: at91_cf: fix checkpatch error Nicolas Ferre
2013-04-17 8:39 ` [PATCH v2 0/7] pcmcia: at91_cf: clean up and add DT support Fabio Porcedda
2013-04-17 8:51 ` Nicolas Ferre [this message]
2013-04-19 22:54 ` Greg Kroah-Hartman
2013-06-05 10:04 ` Nicolas Ferre
2013-06-05 19:22 ` Greg Kroah-Hartman
2013-06-06 8:24 ` 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=516E628B.1000104@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).