From: Andrew Morton <akpm@linux-foundation.org>
To: Tobias_Mueller@twam.info
Cc: david-b@pacbell.net, jordan@cosmicpenguin.net,
gardner.ben@gmail.com, linux-kernel@vger.kernel.org,
Andres Salomon <dilinger@queued.net>
Subject: Re: [PATCH v2 001/001] gpio: AMD CS5535/CS5536 GPIO driver
Date: Mon, 1 Jun 2009 16:54:57 -0700 [thread overview]
Message-ID: <20090601165457.a1cc1025.akpm@linux-foundation.org> (raw)
In-Reply-To: <17be05570905301105h395689ja33afa96e7751381@mail.gmail.com>
On Sat, 30 May 2009 20:05:52 +0200
Tobias M__ller <Tobias_Mueller@twam.info> wrote:
> From: Tobias Mueller <Tobias_Mueller@twam.info>
>
> A GPIO driver for AMD Geode Companion Device CS5535/CS5536
> using the GPIO framework as a replacement for old cs5535-gpio driver.
> Signed-off-by: Tobias Mueller <Tobias_Mueller@twam.info>
Last time, I said "We'll need to discuss the migration plan - we don't
want to maintain two drivers for the same thing".
Back in February, Andres sent out a patch "cs553x-gpio: add AMD
CS5535/CS5536 GPIO driver support". AFACIT that patch does the same
thing that this one does, but differently. IIRC it had a great string
of weird-Kconfig-related build errors and I eventually dropped it.
What's the story here?
Thanks.
next prev parent reply other threads:[~2009-06-01 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 11:53 [PATCH 001/001] gpio: AMD CS5535/CS5536 GPIO driver Tobias Müller
2009-05-26 22:16 ` Andrew Morton
2009-05-30 18:05 ` [PATCH v2 " Tobias Müller
2009-06-01 23:54 ` Andrew Morton [this message]
2009-06-02 0:08 ` Andres Salomon
2009-06-02 3:02 ` Jordan Crouse
2009-06-02 8:14 ` Tobias Müller
2009-06-02 20:33 ` Andrew Morton
2009-06-09 12:27 ` Tobias Müller
2009-06-10 4:00 ` Andres Salomon
2009-06-02 0:02 ` Andrew Morton
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=20090601165457.a1cc1025.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Tobias_Mueller@twam.info \
--cc=david-b@pacbell.net \
--cc=dilinger@queued.net \
--cc=gardner.ben@gmail.com \
--cc=jordan@cosmicpenguin.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.