public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: Anton Vorontsov <cbou@mail.ru>,
	David Woodhouse <dwmw2@infradead.org>,
	<linux-kernel@vger.kernel.org>, <kernel-discuss@handhelds.org>
Subject: Re: [Kernel-discuss] Re: [PATCH 1/8] remove "#if 0" from find_bus function, export it.
Date: Fri, 4 May 2007 14:18:58 +0300	[thread overview]
Message-ID: <485866756.20070504141858@gmail.com> (raw)
In-Reply-To: <20070503231459.GB13626@suse.de>

Hello Greg,

Friday, May 4, 2007, 2:14:59 AM, you wrote:

> On Fri, May 04, 2007 at 01:31:21AM +0400, Anton Vorontsov wrote:
>> This function were placed in "#if 0" because nobody was using it.
>> We using it now.

> Why?  Shouldn't you just export the pointer you need instead?

>> See http://lwn.net/Articles/210610/

> I don't understand the need for this link, it talks about how the api
> changes all the time, something we all know :)

        No, it talked about how complete APIs regress into random
set of functions, lacking complete coverage of target domain. The
response was that when users for the specific function in question
will be in mainline, it will be resurrected. So, here it comes ;-)

> And if you really want it, and you convince me you really need it, can
> you change it to be "bus_find" to play nicer in the namespace?

> thanks,

> greg k-h


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com


      parent reply	other threads:[~2007-05-04 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 21:31 [PATCH 1/8] remove "#if 0" from find_bus function, export it Anton Vorontsov
2007-05-03 23:14 ` Greg KH
2007-05-04  0:21   ` Anton Vorontsov
2007-05-04 11:18   ` Paul Sokolovsky [this message]

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=485866756.20070504141858@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=cbou@mail.ru \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=kernel-discuss@handhelds.org \
    --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