Skip to contentSkip to conversation

Where did find_bus() go in 2.6.18?

DISCUSSION Al Boldi 2 participants 3 messages Nov 21, 2006 – Nov 22, 2006

lore
Share & tools
lore

Al Boldi

author
#0 lore raw
Quoted 9 lines · Greg KH
Quoted 2 lines · Paul Sokolovsky

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.

Quoted 2 lines

Suddenly, concrete building of LDM appears to be shaking. And reasonable question here is: is this a trend?

Good question.

Quoted 10 lines
Quoted 4 lines
Quoted 1 line

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

#1 lore raw
Quoted 3 lines

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"

Quoted 3 lines

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 ?

Signature · 2 lines
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
author
#2 lore raw
Quoted 5 lines · Arjan van de Ven
Quoted 2 lines

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"

You can't do much listening if it's being ignored.

Quoted 6 lines
Quoted 2 lines

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 ;)

Quoted 6 lines

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...

So now we have to be linguists? Some people don't have the ability to explain things easily(wordily); call it a disability, if you like.

Quoted 3 lines
Signature · 2 lines
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

I was trying to do you a favor; anyway, is something forcing you to put that line into your sig?

Thanks anyway!

--
Al