All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: David Lin <dlin@marvell.com>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>, Pete Hsieh <peteh@marvell.com>,
	Chor Teck Law <ctlaw@marvell.com>
Subject: Re: [PATCH] Add new mac80211 driver mwlwifi.
Date: Sun, 06 Sep 2015 16:24:45 +0300	[thread overview]
Message-ID: <877fo3he8y.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1433598191.2467.65.camel@sipsolutions.net> (Johannes Berg's message of "Sat, 06 Jun 2015 15:43:11 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Thu, 2015-06-04 at 04:57 +0000, David Lin wrote:
>
>>  drivers/net/wireless/mwlwifi/Kconfig        |   17 +
>
> Does this driver has any relation to mwifiex? Perhaps the same
> maintainer team, etc.? Could consider moving all the Marvell drivers
> into one directory, but not really necessary I guess.

Actually I would want to start adding vendor directories for wireless
drivers, just like drivers/net/ethernet has, to cleanup the directory
structure. So for example this driver we would have
drivers/net/wireless/marvell/mwlwifi and later we would start moving
existing drivers to vendor drivers as well. Thoughts?

-- 
Kalle Valo

  parent reply	other threads:[~2015-09-06 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  4:57 [PATCH] Add new mac80211 driver mwlwifi David Lin
2015-06-06 13:43 ` Johannes Berg
2015-06-09  7:25   ` David Lin
2015-06-09  7:30     ` Johannes Berg
2015-09-06 13:24   ` Kalle Valo [this message]
2015-09-06 16:05     ` Arend van Spriel
2015-09-06 16:14       ` Arend van Spriel
2015-09-06 16:48         ` Kalle Valo
2015-09-06 16:46       ` Kalle Valo
2015-09-06 17:09         ` Larry Finger
2015-09-11 14:03     ` Chor Teck Law
2015-09-29  9:04       ` Kalle Valo

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=877fo3he8y.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ctlaw@marvell.com \
    --cc=dlin@marvell.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peteh@marvell.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.