All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: linux-pci@atrey.karlin.mff.cuni.cz
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci_find_device and pci_find_slot mark as deprecated
Date: Tue, 9 Aug 2005 12:05:02 +0200	[thread overview]
Message-ID: <4af2d03a05080903055af870bf@mail.gmail.com> (raw)
In-Reply-To: <4af2d03a0508090258942f536@mail.gmail.com>

On 8/9/05, Jiri Slaby <jirislaby@gmail.com> wrote:
> On 8/9/05, Greg KH <greg@kroah.com> wrote:
> > On Tue, Aug 09, 2005 at 01:54:01AM +0200, Jiri Slaby wrote:
> > > This marks these functions as deprecated not to use in latest drivers (it
> > > doesn't use reference counts and the device returned by it can disappear in
> > > any time).
>
> > Anyway, no, I don't want these functions marked this way, it's only
> > going to cause build noise.  I'd much rather you, or others, send me
> > patches that remove the usage of these functions so I can just delete
> > them entirely.
> When the patch was here
> (http://www.fi.muni.cz/~xslaby/lnx/lnx-pci_find-2.6.13-r3g4_3.patch --
> it'll be certainly sliced into many pieces; of course I didn't cc you
> :( ), they told me, that the better way is to let it be, because it
> signify the driver as old api based, if there are some warnings, so I
> want people to stop using the old functions. So you want me to
> continue producing the patches, that removes it?
> 
> regards,
> jiri
>

  reply	other threads:[~2005-08-09 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42F72D4D.8030102@volny.cz>
2005-08-08 23:54 ` [PATCH] pci_find_device and pci_find_slot mark as deprecated Jiri Slaby
2005-08-09  4:11   ` Greg KH
2005-08-09  9:58     ` Jiri Slaby
2005-08-09 10:05       ` Jiri Slaby [this message]
2005-08-09 21:57       ` Greg KH
2005-08-10  0:41         ` Jiri Slaby
2005-08-10  0:50           ` Jiri Slaby
2005-08-08  0:10 Jiri Slaby

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=4af2d03a05080903055af870bf@mail.gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.