From: "John W. Linville" <linville@tuxdriver.com>
To: Cong Wang <amwang@redhat.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [Patch V2] wireless: remove obsolete ar9170usb driver
Date: Thu, 7 Apr 2011 13:13:36 -0400 [thread overview]
Message-ID: <20110407171334.GA9692@tuxdriver.com> (raw)
In-Reply-To: <4D9D7E7C.4040703@redhat.com>
On Thu, Apr 07, 2011 at 05:06:04PM +0800, Cong Wang wrote:
> 于 2011年04月07日 16:56, Christian Lamparter 写道:
> >On Thursday 07 April 2011 09:43:01 Amerigo Wang wrote:
> >>V2: against wireless-next-2.6 and really compile tested.
> >>
> >>AR9170USB is scheduled to be removed in 2.6.40.
> >>
> >>Cc: Christian Lamparter<chunkeey@googlemail.com>
> >>Cc: Johannes Berg<johannes@sipsolutions.net>
> >>Cc: "Luis R. Rodriguez"<lrodriguez@atheros.com>
> >>Cc: "John W. Linville"<linville@tuxdriver.com>
> >>Signed-off-by: WANG Cong<amwang@redhat.com>
> >another duplicate?
> >
> >please see:
> >http://www.spinics.net/lists/linux-wireless/msg66871.html
> >[the patch from last week in case you missed that one too.]
>
> Ah, I am not in wireless list, so didn't know this.
> Why it is not in wireless-next-2.6?
Because I haven't merged it yet -- it's as simple as that.
Anyone else want to quibble over my schedule???
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-04-07 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 10:36 [Patch] wireless: remove obsolete ar9170usb driver Amerigo Wang
2011-04-06 10:45 ` Johannes Berg
2011-04-06 11:00 ` Cong Wang
2011-04-07 7:43 ` [Patch V2] " Amerigo Wang
2011-04-07 8:56 ` Christian Lamparter
2011-04-07 9:06 ` Cong Wang
2011-04-07 17:13 ` John W. Linville [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=20110407171334.GA9692@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=amwang@redhat.com \
--cc=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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 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.