linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] New driver: rtl8723au (mac80211)
Date: Wed, 09 Sep 2015 10:16:09 -0400	[thread overview]
Message-ID: <wrfjoahb65li.fsf@redhat.com> (raw)
In-Reply-To: <55EDDC6D.80000@lwfinger.net> (Larry Finger's message of "Mon, 7 Sep 2015 13:50:21 -0500")

Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 09/07/2015 01:43 PM, Jes Sorensen wrote:
>> Kalle Valo <kvalo@codeaurora.org> writes:
>>> Hi,
>>>
>>> replying to an old thread first.
>>>
>>> Jes Sorensen <Jes.Sorensen@redhat.com> writes:
>>>
>>>> Kalle Valo <kvalo@codeaurora.org> writes:
>>>>> Jes.Sorensen@redhat.com writes:
>>>>>
>>>>>>   MAINTAINERS                          |    8 +
>>>>>>   drivers/net/wireless/Kconfig         |   19 +
>>>>>>   drivers/net/wireless/Makefile        |    2 +
>>>>>>   drivers/net/wireless/rtl8xxxu.c | 4500
>>>>>> ++++++++++++++++++++++++++++++++++
>>>>>>   drivers/net/wireless/rtl8xxxu.h      |  497 ++++
>>>>>>   drivers/net/wireless/rtl8xxxu_regs.h |  941 +++++++
>>>>>
>>>>> I think someone else already mentioned, but it would be better that has
>>>>> it's own directory. Or should this actually be under rtlwifi
>>>>> directory?
>>>>
>>>> I didn't see the need here - it's just 3 files, as long as it doesn't
>>>> have a huge hierachy of files, a new directory doesn't add much
>>>> value. If it becomes an issue later, we can move it into a
>>>> subdirectory.
>>>
>>> It's easier that the driver has it's on directory as everything
>>> (makefile, kconfig etc) is cleanly separated. And actually I would like
>>> to create a new vendor directory for realtek and have this in
>>> drivers/net/wireless/realtek/rtl8xxxu/. And later we could move rtlwifi
>>> under realtek directory as well.
>>
>> If you want to create drivers/net/wireless/realtek, that is fine with
>> me, but maybe you can go ahead and create that first and move the
>> existing drivers in there?
>
> I will submit a patch to do that.

Awesome, once I see that go in, I'll move rtl8xxxu into that directory.

Cheers,
Jes

  reply	other threads:[~2015-09-09 14:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 20:24 [PATCH v3 0/1] New driver: rtl8723au (mac80211) Jes.Sorensen
2015-03-23 20:25 ` [PATCH 1/1] " Jes.Sorensen
2015-03-23 22:51   ` Joe Perches
2015-03-24  1:25     ` Jes Sorensen
2015-04-28  8:37   ` Kalle Valo
2015-04-28 12:55     ` Kalle Valo
2015-04-28 14:27     ` Jes Sorensen
2015-04-28 15:15       ` Larry Finger
2015-09-06 13:38       ` Kalle Valo
2015-09-06 16:41         ` Larry Finger
2015-09-07 13:37           ` Kalle Valo
2015-09-07 18:43         ` Jes Sorensen
2015-09-07 18:50           ` Larry Finger
2015-09-09 14:16             ` Jes Sorensen [this message]
2015-09-29  8:56           ` Kalle Valo
2015-09-29 10:42             ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05 20:04 Xose Vazquez Perez
2015-05-05 21:40 ` Jes Sorensen
2015-05-07  9:43   ` Xose Vazquez Perez
2015-05-07 15:43     ` Larry Finger
2015-03-09 17:00 [PATCH v2 0/1] " Jes.Sorensen
2015-03-09 17:00 ` [PATCH 1/1] " Jes.Sorensen
2015-03-09 17:46   ` Johannes Berg
2015-03-09 18:35     ` Jes Sorensen
2015-03-09 19:52       ` Johannes Berg
2015-03-09 18:20   ` Joe Perches
2015-03-09 18:43     ` Jes Sorensen
2015-03-09 18:51       ` Joe Perches
2015-03-09 19:02         ` Jes Sorensen
2015-03-09 19:07           ` Joe Perches
2015-03-06 22:15 [PATCH 0/1] " Jes.Sorensen
2015-03-06 22:15 ` [PATCH 1/1] " Jes.Sorensen
2015-03-06 22:59   ` Joe Perches
2015-03-07  5:18     ` Jes Sorensen
2015-03-07  5:23       ` Joe Perches
2015-03-07  5:33         ` Jes Sorensen
2015-03-07 21:30   ` Larry Finger
2015-03-09 17:08     ` Jes Sorensen

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=wrfjoahb65li.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).