From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [git patches] rt2800 drivers updates
Date: Sun, 08 Nov 2009 16:07:06 +0100 [thread overview]
Message-ID: <4AF6DE9A.1030204@gmail.com> (raw)
In-Reply-To: <200911081433.32005.bzolnier@gmail.com>
On 11/08/09 14:33, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> Another bunch of updates for rt2800 drivers, this time:
>
> - unify rt2800 drivers some more removing another 300 LOC in the process
> (rt2800pci is down to 1.5 KLOC now)
>
> - add missing RF values to rt2800pci driver
>
> - add eFuse EEPROM support to rt2800usb
> (needed for RT3070 and maybe some other chips)
>
> - fix RX descriptor naming in rt2800usb
>
> I've also merged recent rt2x00 patches from Gertjan to my tree to not
> waste time on eventually synchronizing rt2x00 / rt2800 trees later.
>
> Oh, there is also an unrelated bonus change to rt2500usb driver present
> (removal of dead link tuning code which kills 130 LOC).
>
> I'll post new patches to linux-wireless for review in few minutes.
>
>
> The following changes since commit 93f65fc385c7cca807826ce7f7a76c7429849331:
> Bartlomiej Zolnierkiewicz (1):
> rt2800: add rt2800lib (part four)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bart/misc.git rt2800
>
> Bartlomiej Zolnierkiewicz (10):
> rt2800: prepare for unification of EEPROM support code
> rt2800: unify EEPROM support code
> rt2800pci: add missing RF values to rf_vals table
> rt2800usb: reorganize code in rt2800usb_probe_hw_mode()
> rt2800: prepare for rt2800*_probe_hw_mode() unification
> rt2800: unify rt2800*_probe_hw_mode()
> rt2800usb: fix RX descriptor naming
> rt2800: add eFuse EEPROM support code to rt2800lib
> rt2800usb: add eFuse EEPROM support
> rt2500usb: remove dead link tuning code
>
> Gertjan van Wingerde (3):
> rt2x00: Mark rt2800pci as broken.
> rt2x00: Move interface type assignments to generic code.
> rt2x00: Add dynamic detection of eFuse EEPROM in rt2800pci.
>
> drivers/net/wireless/rt2x00/Kconfig | 7 +-
> drivers/net/wireless/rt2x00/rt2500usb.c | 134 ---------
> drivers/net/wireless/rt2x00/rt2800.h | 29 ++
> drivers/net/wireless/rt2x00/rt2800lib.c | 460 +++++++++++++++++++++++++++++++
> drivers/net/wireless/rt2x00/rt2800lib.h | 6 +
> drivers/net/wireless/rt2x00/rt2800pci.c | 406 ++--------------------------
> drivers/net/wireless/rt2x00/rt2800pci.h | 28 --
> drivers/net/wireless/rt2x00/rt2800usb.c | 411 +--------------------------
> drivers/net/wireless/rt2x00/rt2800usb.h | 40 ++--
> drivers/net/wireless/rt2x00/rt2x00pci.c | 2 +
> drivers/net/wireless/rt2x00/rt2x00soc.c | 5 +
> drivers/net/wireless/rt2x00/rt2x00usb.c | 2 +
> 12 files changed, 556 insertions(+), 974 deletions(-)
>
Ehm, nothing seems to be available in the git repository you pointed to. Did you push it there?
---
Gertjan.
next prev parent reply other threads:[~2009-11-08 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 13:33 [git patches] rt2800 drivers updates Bartlomiej Zolnierkiewicz
2009-11-08 15:07 ` Gertjan van Wingerde [this message]
2009-11-08 15:22 ` Bartlomiej Zolnierkiewicz
2009-11-08 18:13 ` Bartlomiej Zolnierkiewicz
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=4AF6DE9A.1030204@gmail.com \
--to=gwingerde@gmail.com \
--cc=bzolnier@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).