From: Christian Lamparter <chunkeey@googlemail.com>
To: Rajkumar Manoharan <rmanoharan@atheros.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath9k_htc: Add new devices into AR7010
Date: Thu, 11 Nov 2010 15:12:29 +0100 [thread overview]
Message-ID: <201011111512.30343.chunkeey@googlemail.com> (raw)
In-Reply-To: <20101111132341.GA8029@vmraj-lnx.users.atheros.com>
On Thursday 11 November 2010 14:23:41 Rajkumar Manoharan wrote:
> On Wed, Nov 10, 2010 at 06:43:57PM +0530, Rajkumar Manoharan wrote:
> > On Wed, Nov 10, 2010 at 06:05:14PM +0530, Christian Lamparter wrote:
> > > On Wednesday 10 November 2010 12:37:21 Rajkumar Manoharan wrote:
> > > > Treat PIDs (0xA704, 0x1200) as AR7010 devices.
> > >
> > > just a though, but instead of relying only on the pid and
> > > hope for no collisions. you could put a @driver_info flag
> > > for all AR7010 devices into the usb_device_id table and
> > > remove the per-device "cases".
> > >
> > Make sense. Thanks for your review. I'll resend the patch.
> >
> After adding @driver_info to replace per-device cases,
> the patch looks like cleanup one which is not compatible for stable kernel.
> So let the previous patches to be integrated, due to minimal changes.
> And I'll submit the cleanup patch separately. Is that fine?
sure?
Or is this a question directed to John?
next prev parent reply other threads:[~2010-11-11 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 11:37 [PATCH] ath9k_htc: Add new devices into AR7010 Rajkumar Manoharan
2010-11-10 12:35 ` Christian Lamparter
2010-11-10 13:13 ` Rajkumar Manoharan
2010-11-11 13:23 ` Rajkumar Manoharan
2010-11-11 14:12 ` Christian Lamparter [this message]
2010-11-11 15:21 ` Rajkumar Manoharan
2010-11-11 15:28 ` John W. Linville
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=201011111512.30343.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rmanoharan@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.