From: "John W. Linville" <linville@tuxdriver.com>
To: stf_xl@wp.pl
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
gwingerde@gmail.com, ivdoorn@gmail.com,
Helmut Schaa <helmut.schaa@googlemail.com>
Subject: Re: [PATCH 00/32] BBP initialization split
Date: Wed, 22 May 2013 15:01:46 -0400 [thread overview]
Message-ID: <20130522190145.GJ2113@tuxdriver.com> (raw)
In-Reply-To: <1368878635-4455-1-git-send-email-stf_xl@wp.pl>
On Sat, May 18, 2013 at 02:03:23PM +0200, stf_xl@wp.pl wrote:
> This series spits big and messy rt2800_init_bbp() procedure into small
> per chip (or few similar chips) subroutines.
Lots of refactoring here -- I trust Stanislaw, but it might be nice
to see an ACK from Gertjan, Helmut, and/or Ivo?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-05-22 19:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 12:03 [PATCH 00/32] BBP initialization split stf_xl
2013-05-18 12:03 ` [PATCH 01/32] rt2800: make rt2800_init_bbp return void stf_xl
2013-05-18 12:03 ` [PATCH 02/32] rt2800: prepare for rt2800_init_bbp spit stf_xl
2013-05-18 12:03 ` [PATCH 03/32] rt2800: add rt2800_init_bbp_305x_soc subroutine stf_xl
2013-05-18 12:03 ` [PATCH 04/32] rt2800: move 3352 bbp specific code stf_xl
2013-05-18 12:03 ` [PATCH 05/32] rt2800: move rt2800_bbp4_mac_if_ctrl to proper subroutines stf_xl
2013-05-18 12:03 ` [PATCH 06/32] rt2800: initialize BBP_R31 on " stf_xl
2013-05-18 12:03 ` [PATCH 07/32] rt2800: initialize BBP_R47 on 3352 subroutine stf_xl
2013-05-18 12:03 ` [PATCH 08/32] rt2800: initialize BBP_R65 & BBP_R66 on all subroutines (except 5592) stf_xl
2013-05-18 12:03 ` [PATCH 09/32] rt2800: initialize BBP_R68 on proper subroutines stf_xl
2013-05-18 12:03 ` [PATCH 10/32] rt2800: initialize BBP_R69 - BBP_R77 " stf_xl
2013-05-18 12:03 ` [PATCH 11/32] rt2800: initialize BBP_R70 on all subroutines (except 5592) stf_xl
2013-05-18 12:03 ` [PATCH 12/32] rt2800: initialize BBP_R74 - BBP_R80 " stf_xl
2013-05-18 12:03 ` [PATCH 13/32] rt2800: initialize BBP_R82 " stf_xl
2013-05-18 12:03 ` [PATCH 14/32] rt2800: initialize BBP_R83 " stf_xl
2013-05-18 12:03 ` [PATCH 15/32] rt2800: initialize BBP_R84 " stf_xl
2013-05-18 12:03 ` [PATCH 16/32] rt2800: initialize BBP_R86 " stf_xl
2013-05-18 12:03 ` [PATCH 17/32] rt2800: initialize BBP_R88 on proper subroutines stf_xl
2013-05-18 12:03 ` [PATCH 18/32] rt2800: initialize BBP_R91 on all subroutines (except 5592) stf_xl
2013-05-18 12:03 ` [PATCH 19/32] rt2800: initialize BBP_R92 " stf_xl
2013-05-18 12:03 ` [PATCH 20/32] rt2800: move initialization of BBP_95 & BBP_98 to 53xx subroutine stf_xl
2013-05-18 12:03 ` [PATCH 21/32] rt2800: initialize BBP_R103 on all subroutines (except 5592) stf_xl
2013-05-18 12:03 ` [PATCH 22/32] rt2800: initialize BBP_R104 on proper subroutines stf_xl
2013-05-18 12:03 ` [PATCH 23/32] rt2800: initialize BBP_R105 on all subroutines (except 5592) stf_xl
2013-05-18 12:03 ` [PATCH 24/32] rt2800: initialize BBP_R106 " stf_xl
2013-05-18 12:03 ` [PATCH 25/32] rt2800: initialize BBP_R120 on 3352 subroutine stf_xl
2013-05-18 12:03 ` [PATCH 26/32] rt2800: initialize BBP_R128 on proper subroutines stf_xl
2013-05-18 12:03 ` [PATCH 27/32] rt2800: initialize BBP_R134 & BBP_R135 on 53xx subroutine stf_xl
2013-05-18 12:03 ` [PATCH 28/32] rt2800: initialize BBP_R104 on 3352 subroutine stf_xl
2013-05-18 12:03 ` [PATCH 29/32] rt2800: initialize BBP_R108 on proper subroutines stf_xl
2013-05-18 12:03 ` [PATCH 30/32] rt2800: move 3352 specific bbp initialization stf_xl
2013-05-18 12:03 ` [PATCH 31/32] rt2800: move 3290 " stf_xl
2013-05-18 12:03 ` [PATCH 32/32] rt2800: move 53xx " stf_xl
2013-05-22 19:01 ` John W. Linville [this message]
2013-05-22 19:42 ` [PATCH 00/32] BBP initialization split Gertjan van Wingerde
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=20130522190145.GJ2113@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
--cc=users@rt2x00.serialmonkey.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.