Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, Eliad Peller <eliad@wizery.com>
Subject: pull request: TI wireless drivers 2013-10-23 (for 3.13)
Date: Wed, 23 Oct 2013 10:10:52 +0300	[thread overview]
Message-ID: <1382512252.21526.16.camel@porter.coelho.fi> (raw)

[-- Attachment #1: Type: text/plain, Size: 2489 bytes --]


Hi John,

Some patches intended for 3.13.  Eliad continues upstreaming pending
patches from the internal tree.

Please let me know if you have any problems with it!


The following changes since commit a1b13b9ad3759dca24c6b721ee026c540a4e6564:

  rt2x00: rt2800pci: use module_pci_driver macro (2013-10-18 14:07:00 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/luca/wl12xx.git for-linville

for you to fetch changes up to 8d3c1fd8c3a4a4a1a319491cdd09bd7eca23ba3b:

  wlcore: save last regdom configuration on stop (2013-10-23 09:47:45 +0300)

----------------------------------------------------------------
Barak Bercovitz (3):
      wlcore: read fw panic log only in host mode
      wlcore: Allow stopping fw log in recovery
      wlcore: wakeup from ELP before starting recovery

Eliad Peller (3):
      wlcore: add ap_event_mask
      wlcore: fix started_vifs calculation
      wlcore: save last regdom configuration on stop

Ido Reis (2):
      wlcore: fwlog dynamic mem_block control
      wl12xx/wl18xx: update default fw logger's settings

Igal Chernobelsky (3):
      wl18xx: default config alignment with phy defaults
      wlcore: fix interrogate command length
      wlcore/wl18xx/wl12xx: FW log params per chip arch

Victor Goldenshtein (1):
      wlcore: print active channel in the driver_state

 drivers/net/wireless/ti/wl12xx/main.c     |   16 +++++++++---
 drivers/net/wireless/ti/wl18xx/main.c     |   32 +++++++++++++++--------
 drivers/net/wireless/ti/wlcore/acx.c      |   10 +++++---
 drivers/net/wireless/ti/wlcore/cmd.c      |   12 +++++----
 drivers/net/wireless/ti/wlcore/cmd.h      |    3 ++-
 drivers/net/wireless/ti/wlcore/conf.h     |    5 +++-
 drivers/net/wireless/ti/wlcore/debugfs.c  |   18 ++++++++++++-
 drivers/net/wireless/ti/wlcore/event.c    |    1 +
 drivers/net/wireless/ti/wlcore/hw_ops.h   |    9 +++++++
 drivers/net/wireless/ti/wlcore/init.c     |    6 +++++
 drivers/net/wireless/ti/wlcore/io.h       |    4 +--
 drivers/net/wireless/ti/wlcore/main.c     |   74 ++++++++++++++++++++++++++++++++++++++----------------
 drivers/net/wireless/ti/wlcore/scan.c     |   24 +++++++++++++++++-
 drivers/net/wireless/ti/wlcore/testmode.c |    3 ++-
 drivers/net/wireless/ti/wlcore/wlcore.h   |    9 +++++++
 drivers/net/wireless/ti/wlcore/wlcore_i.h |    2 --
 16 files changed, 175 insertions(+), 53 deletions(-)

-- 
Cheers,
Luca.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-10-23  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  7:10 Luca Coelho [this message]
2013-11-05 20:52 ` pull request: TI wireless drivers 2013-10-23 (for 3.13) 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=1382512252.21526.16.camel@porter.coelho.fi \
    --to=luca@coelho.fi \
    --cc=eliad@wizery.com \
    --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