From: Pavel Roskin <proski@gnu.org>
To: Dave <kilroyd@googlemail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Larry Finger <Larry.Finger@lwfinger.net>,
John Linville <linville@tuxdriver.com>,
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 16:44:41 -0400 [thread overview]
Message-ID: <1225399481.7931.5.camel@dv> (raw)
In-Reply-To: <490A17F3.5050802@gmail.com>
On Thu, 2008-10-30 at 20:24 +0000, Dave wrote:
> Johannes Berg wrote:
> On a similar note, would anyone object to collecting the orinoco files
> in a subdirectory?
Fine with me.
> I'm looking at doing some refactoring of orinoco.c
> which I think can be split into at least 3 files.
Maybe it's too late at this point, but it would be nice to support
Orinoco USB eventually. It uses modified orinoco.c. Please keep it in
mind when splitting. It may be possible to reuse some of the new parts
in the USB driver.
> PS the existing files that would move:
> airport.c
> hermes.c
> hermes.h
> hermes_dld.c
> hermes_dld.h
> hermes_rid.h
> orinoco.c
> orinoco.h
> orinoco_cs.c
> orinoco_pci.c
orinoco_pci.c is a good candidate for removal. It only supports the
hardware that is already supported by hostap_pci.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-10-30 20:44 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 [this message]
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
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=1225399481.7931.5.camel@dv \
--to=proski@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=htl10@users.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=kilroyd@googlemail.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).