From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>,
Hin-Tak Leung <htl10@users.sourceforge.net>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Subject: Re: Guidelines regarding separate directory
Date: Thu, 30 Oct 2008 13:29:20 -0400 [thread overview]
Message-ID: <20081030172919.GA4330@tuxdriver.com> (raw)
In-Reply-To: <4909EA78.3060700@lwfinger.net>
On Thu, Oct 30, 2008 at 10:10:16AM -0700, Larry Finger wrote:
> I am planning on adding code to control the LEDs on the RTL8187 devices based on
> the latest vendor driver. From the expected size of the code, I think that
> separate files will be best.
>
> What number of files in a driver make it advisable to create a separate
> directory? Between the rtl8180 and rtl8187 drivers, there are now 15 files and I
> will be adding at least 2 more. Is this the time to create a rtl818x directory
> under drivers/net/wireless?
Yes. It should have been done long ago -- I had them all in
drivers/net/wireless due to my own misinterpretation of the policy
in the past.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-10-30 17:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 17:10 Guidelines regarding separate directory Larry Finger
2008-10-30 17:21 ` Johannes Berg
2008-10-30 20:24 ` Dave
2008-10-30 20:26 ` Johannes Berg
2008-10-30 20:44 ` Pavel Roskin
2008-10-30 20:48 ` Johannes Berg
2008-10-31 3:10 ` Pavel Roskin
2008-10-31 10:01 ` Johannes Berg
2008-10-31 16:01 ` Pavel Roskin
2008-10-31 16:13 ` Dan Williams
2008-10-31 16:24 ` Johannes Berg
2008-10-31 17:04 ` Richard Farina
2008-10-31 17:41 ` Pavel Roskin
2008-10-31 19:06 ` Richard Farina
2008-11-04 0:28 ` Pavel Roskin
2008-10-30 20:50 ` Dave
2008-10-30 17:29 ` John W. Linville [this message]
2008-10-30 23:47 ` Larry Finger
2008-10-31 10:06 ` Johannes Berg
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=20081030172919.GA4330@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=htl10@users.sourceforge.net \
--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).