From: Kalle Valo <kvalo@codeaurora.org>
To: Chor Teck Law <ctlaw@marvell.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
David Lin <dlin@marvell.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>, Pete Hsieh <peteh@marvell.com>
Subject: Re: [PATCH] Add new mac80211 driver mwlwifi.
Date: Tue, 29 Sep 2015 12:04:47 +0300 [thread overview]
Message-ID: <87a8s57g0g.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <9fcd82c278ea47cb915798ffc7bdcb0b@SC-EXCH03.marvell.com> (Chor Teck Law's message of "Fri, 11 Sep 2015 14:03:08 +0000")
Chor Teck Law <ctlaw@marvell.com> writes:
>> > 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?
>>
>
> Yes, we are ok with this folder hierarchy change. Let us know how we
> can help. Should we start with this new folder now or wait for more
> feedbacks?
Yeah, in the next version please use the new folder hierarchy for
mwlwifi.
--
Kalle Valo
prev parent reply other threads:[~2015-09-29 9:04 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
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 [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=87a8s57g0g.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 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).