From: James Ketrenos <jketreno@linux.intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: warnings in git-wireless
Date: Tue, 05 Jun 2007 13:12:03 -0700 [thread overview]
Message-ID: <4665C393.2000507@linux.intel.com> (raw)
In-Reply-To: <20070605115701.GA5391@tuxdriver.com>
John W. Linville wrote:
> On Tue, Jun 05, 2007 at 02:06:14AM -0700, Andrew Morton wrote:
>
>> Please, don't anybody dare think about thinking about letting this anywhere
>> near mainline until it has had a thorough review. Or at least, a little bit
>> of review.
>
> Don't worry -- I assure you that everyone is aware of the issues.
>
> John
Yes, we certainly don't want a driver to be "near mainline" that does things that the rest of the kernel and other drivers are doing. We should force them to stay out-of-tree until any and everything is resolved. Heaven forbid that the code should be merged, contributed, and improved upon as a community.
You'd think these guys were trying to enable folks with a driver so they can use the hardware they bought or something. Its almost laughable. What idiots.
James
next prev parent reply other threads:[~2007-06-05 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 9:06 warnings in git-wireless Andrew Morton
2007-06-05 11:57 ` John W. Linville
2007-06-05 20:12 ` James Ketrenos [this message]
2007-06-05 23:26 ` Andrew Morton
2007-06-06 7:20 ` Christoph Hellwig
2007-06-06 14:14 ` James Ketrenos
2007-06-06 20:51 ` James Ketrenos
2007-06-06 23:35 ` Andrew Morton
2007-06-06 22:33 ` James Ketrenos
2007-06-07 1:04 ` Andrew Morton
2007-06-07 1:13 ` Dave Jones
2007-06-07 0:00 ` Randy Dunlap
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=4665C393.2000507@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).