mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Where did find_bus() go in 2.6.18?
Date: Tue, 21 Nov 2006 17:15:01 +0300	[thread overview]
Message-ID: <200611211715.01963.a1426z@gawab.com> (raw)

Greg KH wrote:
> On Mon, Nov 20, 2006 at 04:13:22PM +0200, Paul Sokolovsky wrote:
> > And suddenly - oops, in 2.6.18 we lose ability to query the highest
> > level of hierarchy, namely bus set. And on what criterion? "unused".
>
> Please go read Documenation/stable_api_nonsense.txt for why the
> in-kernel apis always change.  It's how Linux works.
>
> > Suddenly, concrete building of LDM appears to be shaking. And reasonable
> > question here is: is this a trend?

Good question.

> > > Also, any reason why your drivers aren't in the mainline kernel yet? 
> >
> > One reason is of course because it's not that easy to get something
> > into mainline. ;-)
>
> Why do you feel this way?  Is it a proceedural thing?  A technical
> thing?  A time thing?
>
> We want to make it as easy as possible to get code into the tree, please
> submit it and be persistant to get it there.

Persistent as in: get down on your knees and say "please, please, pretty 
please"?

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?

There should probably be some guideline to indicate what kind of code is 
acceptable and what's not.  You know, something like a constitution.  
Otherwise, we'll probably have a situtation like the jungle, where the weak 
are silently being killed off.

Is that the kind of evolution you are aiming for?

BTW, no troll, really.


Thanks!

--
Al


             reply	other threads:[~2006-11-21 14:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 14:15 Al Boldi [this message]
2006-11-21 14:32 ` Arjan van de Ven
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=200611211715.01963.a1426z@gawab.com \
    --to=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®