public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Renzmann" <mrenzmann@madwifi.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ath9k-devel@lists.ath9k.org, ath5k-devel@lists.ath5k.org
Subject: Re: [PATCH] [PATCH 2/4] Remove Atheros 11n devices from ath5k
Date: Mon, 21 Jul 2008 07:12:57 +0200 (CEST)	[thread overview]
Message-ID: <1542.217.24.1.226.1216617177.squirrel@webmail.madwifi.org> (raw)
In-Reply-To: <20080720024554.GS17936@ruslug.rutgers.edu>

Hi.

Luis R. Rodriguez wrote:
> Remove Atheros 11n devices from being claimed by ath5k as its
> now handled by ath9k.

I must admit that I can't tell it myself due to a lack of in-depth
knowledge about both drivers, hence the question: why a new driver, rather
than adding 11n support to ath5k and have a single driver for all Atheros
chipsets?

Bye, Mike

  parent reply	other threads:[~2008-07-21  5:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20  2:43 [PATCH 0/4] Atheros IEEE 802.11n ath9k driver Luis R. Rodriguez
2008-07-20  2:45 ` [PATCH 1/4] Add new " Luis R. Rodriguez
2008-07-20  2:45   ` [PATCH] [PATCH 2/4] Remove Atheros 11n devices from ath5k Luis R. Rodriguez
2008-07-20  2:47     ` [PATCH 3/4] list.h: Add list_splice_tail() and list_splice_tail_init() Luis R. Rodriguez
2008-07-20  2:48       ` [PATCH] [PATCH 4/4] list.h: add list_cut_position() Luis R. Rodriguez
2008-07-21  5:12     ` Michael Renzmann [this message]
2008-07-21 11:58       ` [ath5k-devel] [PATCH] [PATCH 2/4] Remove Atheros 11n devices from ath5k Luis R. Rodriguez
2008-07-23 19:43   ` [PATCH 1/4] Add new Atheros IEEE 802.11n ath9k driver Johannes Berg
2008-07-23 20:09     ` Harvey Harrison
2008-07-24  2:01     ` [ath9k-devel] " Sujith
2008-07-24  3:18       ` Johannes Berg

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=1542.217.24.1.226.1216617177.squirrel@webmail.madwifi.org \
    --to=mrenzmann@madwifi.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox