From: Arjan van de Ven <arjan@infradead.org>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where did find_bus() go in 2.6.18?
Date: Tue, 21 Nov 2006 15:32:34 +0100 [thread overview]
Message-ID: <1164119554.31358.670.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200611211715.01963.a1426z@gawab.com>
> Persistent as in: get down on your knees and say "please, please, pretty
> please"?
no as in "listen to the code review feedback and fix things and then try
again"
>
> AFAICT, code is being ignored/rejected for the mere reason that it's not
> considered useful; but who's to say what is useful and what's not?
no things are being reject because they're not being *used*.
Subtle but important difference ;)
But yes, you need to do a moderate amount of "selling" when submitting
code. For a driver that's easy usually, "this is a driver for device X"
and "sold" if the code is reasonable.
For major subsystem changes... you need to explain why it's worth the
disruption. If you can't explain that... then what good would it be ?
--
if you want to mail me at work (and no Mr Al Boldi, you really don't want to), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-11-21 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 14:15 Al Boldi
2006-11-21 14:32 ` Arjan van de Ven [this message]
2006-11-22 14:18 ` Al Boldi
-- strict thread matches above, loose matches on Subject: below --
2006-11-19 22:34 Paul Sokolovsky
2006-11-19 23:45 ` Jiri Slaby
2006-11-20 0:12 ` Greg KH
2006-11-20 14:13 ` Re[2]: " Paul Sokolovsky
2006-11-20 17:35 ` Adrian Bunk
2006-11-21 15:08 ` Re[2]: " Paul Sokolovsky
2006-11-21 18:04 ` Adrian Bunk
2006-11-21 7:54 ` Greg KH
2006-11-20 0:13 ` Re[2]: " Paul Sokolovsky
2006-11-20 8:34 ` Arjan van de Ven
2006-11-21 18:29 ` Matthew Frost
2006-11-21 19:01 ` Evgeniy Polyakov
2006-11-21 19:41 ` Re[2]: " Paul Sokolovsky
2006-11-21 20:34 ` Matthew Frost
2006-11-20 9:35 ` pHilipp Zabel
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=1164119554.31358.670.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=a1426z@gawab.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®