From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org
Cc: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org,
hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
flamingice-R9e9/4HEdknk1uMJSBkQmQ@public.gmane.org
Subject: Re: Please pull 'p54' branch of wireless-2.6
Date: Wed, 19 Sep 2007 15:08:35 -0700 (PDT) [thread overview]
Message-ID: <20070919.150835.35013628.davem@davemloft.net> (raw)
In-Reply-To: <46F19C3C.6090605-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
From: Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Date: Wed, 19 Sep 2007 18:01:32 -0400
> There were complaints about the nonsensical wireless/mac80211
> directory. But if there are enough files, a driver should
> definitely get its own directory. Like life, it's a balance. If
> it's just one or two C files, a directory might be overkill. If
> it's more, it definitely warrants a sub-dir.
That's generally how I see things too.
prev parent reply other threads:[~2007-09-19 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 19:55 Please pull 'p54' branch of wireless-2.6 John W. Linville
2007-09-19 20:20 ` David Miller
[not found] ` <20070919195527.GD5483-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-09-19 21:04 ` Christoph Hellwig
2007-09-19 21:12 ` David Miller
[not found] ` <20070919.141200.56568833.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-09-19 21:26 ` John W. Linville
[not found] ` <20070919212607.GA3036-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-09-19 22:01 ` Jeff Garzik
[not found] ` <46F19C3C.6090605-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2007-09-19 22:08 ` David Miller [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=20070919.150835.35013628.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=flamingice-R9e9/4HEdknk1uMJSBkQmQ@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).