public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: Greg KH <gregkh@suse.de>, Arjan van de Ven <arjan@infradead.org>,
	Jiri Slaby <jirislaby@gmail.com>,
	linux-kernel@vger.kernel.org, kernel-discuss@handhelds.org
Subject: Re: Where did find_bus() go in 2.6.18?
Date: Mon, 20 Nov 2006 18:35:50 +0100	[thread overview]
Message-ID: <20061120173550.GV31879@stusta.de> (raw)
In-Reply-To: <1148526308.20061120161322@gmail.com>

On Mon, Nov 20, 2006 at 04:13:22PM +0200, Paul Sokolovsky wrote:
>...
>   But note that I don't really ask mainline kernel developers how to
> fix this driver - I would actually be ashamed to do so, as I myself a
> (newbie) kernel hacker. So, the question stays the same, though I
> probably reformulate it a bit stronger now: how it came that ability
> to query buses (at all) was removed from 2.6.18?
> 
>   As it was before, it was clear that LDM consists of multiple layers,
> and each layer offers consistent and complete set of operations on it,
> like adding new object on this layer, removing, adding child, removing
> child, *and* query objects on this level or among childs. I may miss
> some accidental gaps in that picture of course, but it still was an
> integral, complete design paradigm offering full dynamicity and
> introspection.
> 
>   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". I
> would really dream that such core, the most basic APIs are not being
> defined in terms of "someone does use it right now". A method to query
> objects of core kernel data sets is just integral part of interface to
> these datasets, you cannot remove it and not cripple such interface.
> Again, it's loss of introspection, and that's not just "cleanup", it's
> a paradigm shift.
>...

As Documentation/stable_api_nonsense.txt explains, there is no stable 
kernel API. If you don't want to get the APIs your driver uses 
changed/removed you should really try to get it merged into mainline.

The find_bus() case is even more interesting since you are using it in a 
driver although it has never been exported to modules. Considering that 
you anyway have to patch the kernel for getting your driver running 
(since it won't run as a module against an unmodified kernel), you could 
simply undo my patch locally until you submit your driver for inclusion 
in mainline.

>  Paul

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-11-20 17:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 22:34 Where did find_bus() go in 2.6.18? 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 [this message]
2006-11-21 15:08         ` Paul Sokolovsky
2006-11-21 15:16           ` Arjan van de Ven
2006-11-21 18:04           ` Adrian Bunk
2006-11-21  7:54       ` Greg KH
2006-11-22  8:36         ` Re[2]: " Paul Sokolovsky
2006-11-21 19:02       ` Dmitry Torokhov
2006-11-20  0:13   ` 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
  -- strict thread matches above, loose matches on Subject: below --
2006-11-21 14:15 Al Boldi
2006-11-21 14:32 ` Arjan van de Ven
2006-11-22 14:18   ` Al Boldi

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=20061120173550.GV31879@stusta.de \
    --to=bunk@stusta.de \
    --cc=arjan@infradead.org \
    --cc=gregkh@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=kernel-discuss@handhelds.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmiscml@gmail.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