linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: David Miller <davem@davemloft.net>
Cc: tilman@imap.cc, sfr@canb.auug.org.au,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	isdn@linux-pingi.de, isdn4linux@listserv.isdn4linux.de
Subject: Re: [PATCH] pci: push deprecated pci_find_device() function to last user
Date: Wed, 13 Jan 2010 20:43:31 -0800	[thread overview]
Message-ID: <20100114044331.GA29008@suse.de> (raw)
In-Reply-To: <20100113.203338.52448956.davem@davemloft.net>

On Wed, Jan 13, 2010 at 08:33:38PM -0800, David Miller wrote:
> From: Tilman Schmidt <tilman@imap.cc>
> Date: Wed, 13 Jan 2010 15:23:28 +0100 (CET)
> 
> > The ISDN4Linux HiSax driver family contains the last remaining users
> > of the deprecated pci_find_device() function. This patch creates a
> > private copy of that function in HiSax, and removes the now unused
> > global function together with its controlling configuration option,
> > CONFIG_PCI_LEGACY.
> > 
> > Impact: code reorganization, no functional change
> > Signed-off-by: Tilman Schmidt <tilman@imap.cc>
> > ---
> > Note: This patch is not, nor does it intend to be, checkpatch.pl clean.
> > The issues checkpatch.pl reports on it were already present before, and
> > are unrelated to the topic of this patch.
> 
> I'm fine with this, and Greg or whoever else can take this
> through a driver or PCI specific tree if they want:
> 
> Acked-by: David S. Miller <davem@davemloft.net>

Where do ISDN patches go through, the network tree?

Acked-by: Greg Kroah-Hartman <gregkh@suse.de>

  reply	other threads:[~2010-01-14  4:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  0:22 Can we remove pci_find_device() yet? Stephen Rothwell
2010-01-08  4:46 ` Greg KH
2010-01-11 19:46   ` Tilman Schmidt
2010-01-11 20:01     ` Greg KH
2010-01-12  0:21       ` Stephen Rothwell
2010-01-12  0:46         ` Greg KH
2010-01-12 16:42       ` Tilman Schmidt
2010-01-12 17:39         ` Greg KH
2010-01-13  9:02           ` Tilman Schmidt
2010-01-12 20:34       ` Krzysztof Halasa
2010-01-12 20:53         ` Ben Hutchings
2010-01-12 21:18           ` Greg KH
2010-01-13 15:09             ` Krzysztof Halasa
2010-01-13 14:23       ` [PATCH] pci: push deprecated pci_find_device() function to last user Tilman Schmidt
2010-01-14  4:33         ` David Miller
2010-01-14  4:43           ` Greg KH [this message]
2010-01-14  8:12             ` David Miller
2010-01-14 16:28               ` Jesse Barnes
2010-01-14 22:18                 ` [PATCH/REPOST] " Tilman Schmidt
2010-01-15 18:08                   ` Jesse Barnes
2010-01-16 11:17                     ` Stephen Rothwell
2010-01-18 16:24                 ` [PATCH/v2] " Tilman Schmidt
2010-01-14 10:18       ` Can we remove pci_find_device() yet? Andi Kleen
2010-01-14 11:02         ` Alan Cox
2010-01-14 11:03           ` Andi Kleen
2010-01-14 12:39             ` Tilman Schmidt
2010-01-20 15:11           ` Tilman Schmidt

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=20100114044331.GA29008@suse.de \
    --to=gregkh@suse.de \
    --cc=davem@davemloft.net \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=isdn@linux-pingi.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tilman@imap.cc \
    /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;
as well as URLs for NNTP newsgroup(s).