From: Simon Kelley <simon@thekelleys.org.uk>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Dan Williams <dcbw@redhat.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: orphan the atmel wireless driver
Date: Sat, 24 Jul 2010 19:59:13 +0100 [thread overview]
Message-ID: <4C4B3801.6010509@thekelleys.org.uk> (raw)
In-Reply-To: <20100723132847.GC6678@tuxdriver.com>
John W. Linville wrote:
> On Fri, Jul 23, 2010 at 10:07:35AM +0100, Simon Kelley wrote:
>> Dan Williams wrote:
>>> On Thu, 2010-07-22 at 14:31 -0400, John W. Linville wrote:
>>>> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>>> Aww, how sad :(. I'll take it since I still have some of this
>>> hardware. Not that I'll do much with it, but if the patches are simple
>>> I'm happy to test+ack them.
>>>
>> Thanks Dan, whilst I still have the hardware, I no longer have a
>> convenient PCMCIA slot into which to plug it.
>>
>> This hardware is well orphaned: it never made is past 802.11b, and there
>> have been no new models for a long time. Nevertheless, if the existing
>> code can be kept functional, that would be good.
>
> Is the existing code functional? The device I have seems to only
> half work -- I suppose I need to figure that out...
>
> John
I'm not aware of any problems. I'll try and test a new kernel when I can
find a PCMCIA-full laptop. If the problem turns out to be your hardware,
John, I can send you another card.
Cheers,
Simon.
prev parent reply other threads:[~2010-07-24 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 18:31 [PATCH] MAINTAINERS: orphan the atmel wireless driver John W. Linville
2010-07-22 22:28 ` Dan Williams
2010-07-23 9:07 ` Simon Kelley
2010-07-23 13:28 ` John W. Linville
2010-07-24 18:59 ` Simon Kelley [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=4C4B3801.6010509@thekelleys.org.uk \
--to=simon@thekelleys.org.uk \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).