public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
	"Rafał Miłecki" <zajec5@gmail.com>
Subject: [PATCH 3.18 0/7] b43: first series for 3.18
Date: Thu, 31 Jul 2014 21:59:41 +0200	[thread overview]
Message-ID: <1406836788-23704-1-git-send-email-zajec5@gmail.com> (raw)

John, this patchset continues improvements for b43. It doesn't fix any
particular bug/issue, so please queue it for 3.18. There is nothing
important enough to risk breaking wireless-next for 3.17.

Rafa? Mi?ecki (7):
  b43: update flushing many writes performed in a row
  b43: don't duplicate common PHY read/write ops
  b43: flush some writes on Broadcom MIPS SoCs
  b43: N-PHY: update rev3+ gain control workarounds
  b43: N-PHY: add RF power tables for radio 0x2057 revs 9 & 14
  b43: implement PPR (Power Per Rate) management/API
  b43: N-PHY: support setting custom TX power

 drivers/net/wireless/b43/Makefile      |   1 +
 drivers/net/wireless/b43/b43.h         |  16 +++
 drivers/net/wireless/b43/bus.h         |  14 +++
 drivers/net/wireless/b43/main.c        |  17 ++-
 drivers/net/wireless/b43/phy_a.c       |   4 +-
 drivers/net/wireless/b43/phy_common.c  |  25 ++++-
 drivers/net/wireless/b43/phy_g.c       |   8 +-
 drivers/net/wireless/b43/phy_ht.c      |  20 +---
 drivers/net/wireless/b43/phy_lcn.c     |  20 +---
 drivers/net/wireless/b43/phy_lp.c      |  20 +---
 drivers/net/wireless/b43/phy_n.c       | 128 +++++++++++++++------
 drivers/net/wireless/b43/phy_n.h       |   4 +
 drivers/net/wireless/b43/ppr.c         | 199 +++++++++++++++++++++++++++++++++
 drivers/net/wireless/b43/ppr.h         |  45 ++++++++
 drivers/net/wireless/b43/tables_nphy.c | 128 +++++++++++++++++----
 drivers/net/wireless/b43/tables_nphy.h |   2 +
 16 files changed, 523 insertions(+), 128 deletions(-)
 create mode 100644 drivers/net/wireless/b43/ppr.c
 create mode 100644 drivers/net/wireless/b43/ppr.h

-- 
1.8.4.5

             reply	other threads:[~2014-07-31 19:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 19:59 Rafał Miłecki [this message]
2014-07-31 19:59 ` [PATCH 3.18 1/7] b43: update flushing many writes performed in a row Rafał Miłecki
2014-07-31 19:59 ` [PATCH 3.18 2/7] b43: don't duplicate common PHY read/write ops Rafał Miłecki
2014-07-31 19:59 ` [PATCH 3.18 3/7] b43: flush some writes on Broadcom MIPS SoCs Rafał Miłecki
2014-07-31 20:23   ` Hauke Mehrtens
2014-07-31 20:33     ` Rafał Miłecki
2014-07-31 20:34     ` Florian Fainelli
2014-07-31 20:25   ` Florian Fainelli
2014-07-31 20:34     ` Rafał Miłecki
2014-08-01  1:55       ` Florian Fainelli
2014-08-07  5:45   ` [PATCH V2 " Rafał Miłecki
2014-07-31 19:59 ` [PATCH 3.18 4/7] b43: N-PHY: update rev3+ gain control workarounds Rafał Miłecki
2014-07-31 19:59 ` [PATCH 3.18 5/7] b43: N-PHY: add RF power tables for radio 0x2057 revs 9 & 14 Rafał Miłecki
2014-07-31 19:59 ` [PATCH V2 3.18 6/7] b43: implement PPR (Power Per Rate) management/API Rafał Miłecki
2014-07-31 19:59 ` [PATCH V2 3.18 7/7] b43: N-PHY: support setting custom TX power Rafał Miłecki

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=1406836788-23704-1-git-send-email-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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