From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "ksummit-2008-discuss@lists.linux-foundation.org"
<ksummit-2008-discuss@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Request for discussion on when to merge drivers
Date: Wed, 18 Jun 2008 12:34:01 -0500 [thread overview]
Message-ID: <1213810441.3515.73.camel@localhost.localdomain> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA3061C5FA5@orsmsx505.amr.corp.intel.com>
On Wed, 2008-06-18 at 10:15 -0700, Luck, Tony wrote:
> > Experience has shown that for most SCSI drivers, the authors tend to be
> > the people producing the hardware and without documentation, no-one else
> > can fix up anything other than obvious coding errors, so we can't put it
> > in the tree and hope someone else will fix it if they have a problem.
>
> Is there an opportunity for a carrot here ... a driver submitted
> *with documentation* gets a faster path into the tree?
You mean with actual how to program it information? er dunno ... never
seen one of those ...
But I suppose, theoretically, since anyone could access the
documentation to maintain it, it would be much more likely to be fixed
up in tree, yes.
James
next prev parent reply other threads:[~2008-06-18 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 15:27 Request for discussion on when to merge drivers James Bottomley
2008-06-18 17:15 ` [Ksummit-2008-discuss] " Luck, Tony
2008-06-18 17:34 ` James Bottomley [this message]
2008-06-18 17:30 ` Benny Halevy
2008-06-18 23:20 ` [Ksummit-2008-discuss] " Jiri Kosina
2008-06-19 7:34 ` Benny Halevy
2008-06-18 18:38 ` Mauro Carvalho Chehab
2008-06-18 23:31 ` Benjamin Herrenschmidt
2008-06-18 23:39 ` [Ksummit-2008-discuss] " James Bottomley
2008-06-18 23:48 ` Jiri Kosina
2008-06-19 9:13 ` Stefan Richter
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=1213810441.3515.73.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=ksummit-2008-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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