From: Luciano Coelho <coelho@ti.com>
To: linux-wireless@vger.kernel.org
Cc: arik@wizery.com, linville@tuxdriver.com
Subject: Re: [PATCH 00/16] wl12xx/wl1251/wlcore: reorganize drivers part 1
Date: Thu, 12 Apr 2012 15:42:33 +0300 [thread overview]
Message-ID: <1334234553.10398.37.camel@cumari> (raw)
In-Reply-To: <1334137083-13490-1-git-send-email-coelho@ti.com>
On Wed, 2012-04-11 at 12:37 +0300, Luciano Coelho wrote:
> Hi,
>
> This is the first batch of patches from the reorganization our drivers and
> preparation for the inclusion of the new wl18xx driver.
>
> First of all, we moved all the TI wireless drivers into a new subdirectory
> drivers/net/wireless/ti so we can keep all our drivers in the same place.
>
> Then, we started splitting the wl12xx driver into a core module (wlcore) and a
> lower driver (wl12xx). This was done because the wl18xx driver shares a lot of
> the same code. The wlcore module will eventually become a kind of common
> library for the different lower drivers to use. This patchset contains only
> the initial part of this work. More will follow soon.
>
> John, please let me know if it's okay to include the first patch, with which I
> moved stuff around, in my tree so we can keep things in sync more easily.
>
> Please review.
Applied and pushed this series to wl12xx.git/master.
--
Cheers,
Luca.
prev parent reply other threads:[~2012-04-12 12:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 9:37 [PATCH 00/16] wl12xx/wl1251/wlcore: reorganize drivers part 1 Luciano Coelho
2012-04-11 9:37 ` [PATCH 01/16] wireless/wl12xx/wl1251: move TI WLAN modules to a common ti subdirectory Luciano Coelho
2012-04-13 17:52 ` John W. Linville
2012-04-11 9:37 ` [PATCH 02/16] wl12xx/wlcore: rename wl12xx to wlcore Luciano Coelho
2012-04-11 9:37 ` [PATCH 03/16] wl12xx/wlcore: spin out the wl12xx probe from wlcore to a new wl12xx Luciano Coelho
2012-04-11 9:37 ` [PATCH 04/16] wl12xx/wlcore: initial split of probe Luciano Coelho
2012-04-11 9:37 ` [PATCH 05/16] wl12xx/wlcore: move wl1271 struct to wlcore and add ops Luciano Coelho
2012-04-11 9:37 ` [PATCH 06/16] wlcore/wl12xx: implement chip-specific partition tables Luciano Coelho
2012-04-11 9:37 ` [PATCH 07/16] wlcore/wl12xx: implement chip-specific register tables Luciano Coelho
2012-04-11 9:37 ` [PATCH 08/16] wlcore/wl12xx: add chip-specific identify chip operation Luciano Coelho
2012-04-11 9:37 ` [PATCH 09/16] wlcore/wl12xx: move get_pg_ver to the lower driver Luciano Coelho
2012-04-11 9:37 ` [PATCH 10/16] wlcore/wl12xx: move top initialization to wl12xx Luciano Coelho
2012-04-11 9:37 ` [PATCH 11/16] wlcore/wl12xx: move MAC address reading operation to lower driver Luciano Coelho
2012-04-11 9:37 ` [PATCH 12/16] wlcore/wl12xx: add command trigger and event ack operations Luciano Coelho
2012-04-11 9:38 ` [PATCH 13/16] wlcore/wl12xx: add quirk for legacy NVS support Luciano Coelho
2012-04-11 9:38 ` [PATCH 14/16] wlcore: remove some unnecessary event mailbox address reads Luciano Coelho
2012-04-11 9:38 ` [PATCH 15/16] wlcore: add quirk to disable ELP Luciano Coelho
2012-04-11 9:38 ` [PATCH 16/16] wlcore/wl12xx: create per-chip-family private storage Luciano Coelho
2012-04-12 12:42 ` Luciano Coelho [this message]
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=1334234553.10398.37.camel@cumari \
--to=coelho@ti.com \
--cc=arik@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;
as well as URLs for NNTP newsgroup(s).