From: James Ketrenos <jketreno@linux.intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: warnings in git-wireless
Date: Wed, 06 Jun 2007 07:14:51 -0700 [thread overview]
Message-ID: <4666C15B.4050007@linux.intel.com> (raw)
In-Reply-To: <20070606072016.GA4805@infradead.org>
Christoph Hellwig wrote:
> On Tue, Jun 05, 2007 at 01:12:03PM -0700, James Ketrenos wrote:
>> 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.
>
> Maybe you should make sure your companies publishes specs
I'm flattered that you think I am high enough at Intel to do that. If it was in my power, accurate and complete specifications would be available for all of Intel's hardware--for everyone. I doubt you'll find a single Linux developer at Intel who is not fighting to try and reach that goal, including myself.
The reality is, however, (and this may shock you) I am not a vice president or head of a major division at Intel. Its true. Intel doesn't do what I want just because I snap my fingers and say it should be so.
Instead, we try and do what we can -- enable people with a driver (and a community to contribute into) so that the hardware they purchased can operate to its fullest potential on Linux. We realize within the community that some areas are difficult for people outside of Intel to initially contribute to given the lack of specs. However, there are vast quantities of features and functionality that can be enabled and improved given nothing more than the driver sources.
Anyway, its obvious from your emails that our efforts are not sufficient and you seem to resent that we're even trying. I apologize.
If you'd like to submit patches to help us make the perfect driver, we're very willing to review and merge those in.
James
next prev parent reply other threads:[~2007-06-06 16:15 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
[not found] ` <20070605020614.3f06b2ab.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2007-06-05 11:57 ` John W. Linville
[not found] ` <20070605115701.GA5391-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-05 20:12 ` James Ketrenos
2007-06-05 23:26 ` Andrew Morton
2007-06-06 7:20 ` Christoph Hellwig
2007-06-06 14:14 ` James Ketrenos [this message]
2007-06-06 20:51 ` James Ketrenos
2007-06-06 23:35 ` Andrew Morton
[not found] ` <20070606163534.6a6cffb7.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
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=4666C15B.4050007@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.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).