From: Ed Wildgoose <ed@wildgooses.com>
To: Philip Prindeville <philipp@redfish-solutions.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
platform-driver-x86@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Richard Purdie <rpurdie@rpsys.net>,
Andres Salomon <dilinger@queued.net>,
Ed Wildgoose <kernel@wildgooses.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v3 1/1] alix2: supplement driver to include GPIO button support
Date: Thu, 26 Jan 2012 10:15:08 +0000 [thread overview]
Message-ID: <4F2127AC.8060407@wildgooses.com> (raw)
In-Reply-To: <4F20AE4D.2040906@redfish-solutions.com>
On 26/01/2012 01:37, Philip Prindeville wrote:
> On 1/25/12 6:08 PM, Andrew Morton wrote:
>
>> That didn't really answer my question about the whereabouts of the
>> mystery wireless driver. Oh well, it doesn't matter much.
> Oh, yeah, sorry. The driver is currently only in my tree, though I had wanted to get it into OpenWRT but after having even linux-atm upstream patches not get retrofitted into the OpenWRT sources, I've given up on submitting additional patches.
>
Any chance you would post the driver somewhere public so it's archived
for other hackers to play with?
Cheers for all your work on the Alix stuff - it still seems to have a
lot of life left, so thanks for working on it
Ed W
prev parent reply other threads:[~2012-01-26 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 19:56 [PATCH v3 1/1] alix2: supplement driver to include GPIO button support Philip Prindeville
2012-01-23 22:56 ` Andres Salomon
2012-01-25 22:57 ` Andrew Morton
2012-01-25 23:04 ` Philip Prindeville
2012-01-25 23:16 ` Andrew Morton
2012-01-25 23:47 ` Philip Prindeville
2012-01-26 1:08 ` Andrew Morton
2012-01-26 1:37 ` Philip Prindeville
2012-01-26 10:15 ` Ed Wildgoose [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=4F2127AC.8060407@wildgooses.com \
--to=ed@wildgooses.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=dilinger@queued.net \
--cc=dwmw2@infradead.org \
--cc=kernel@wildgooses.com \
--cc=philipp@redfish-solutions.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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.