From: Tilman Schmidt <tilman@imap.cc>
To: Greg KH <gregkh@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Karsten Keil <isdn@linux-pingi.de>,
isdn4linux@listserv.isdn4linux.de
Subject: Re: Can we remove pci_find_device() yet?
Date: Tue, 12 Jan 2010 17:42:14 +0100 [thread overview]
Message-ID: <4B4CA666.1050505@imap.cc> (raw)
In-Reply-To: <20100111200136.GA29955@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 2010-01-11 21:01 schrieb Greg KH:
> On Mon, Jan 11, 2010 at 08:46:50PM +0100, Tilman Schmidt wrote:
>>
>> Just an idea - as a stopgap measure, couldn't pci_find_device() be made
>> a private function of the HiSax drivers? That way, the remainder of the
>> kernel won't be polluted by it anymore, and the PCI_LEGACY config option
>> can be dropped. Something like this quick and dirty hack:
>
> Close, but if you do this, please name the function
> hisax_find_pci_device() or something, and change the drivers to use it
Sorry, but no. That would drag me into the checkpatch.pl swamp,
a place I know well enough by now to avoid it whenever possible.
Many of the calls to pci_find_device() have checkpatch problems
which of course do not go away by just substituting another
function name, so I would be obliged to restructure all those
call sites by hand for the sake of "not introducing new code
with checkpatch problems". BTDT.
So I'll drop that idea. If someone else wants to pick it up,
feel free to do so.
Regards,
Tilman
- --
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktMpmYACgkQQ3+did9BuFuJKgCggRImZ3NOTmCJUpUktreervtz
fegAniAexJirz3p/AXPB6EpsCEJn3hPL
=QwUB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-12 17:27 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 [this message]
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
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=4B4CA666.1050505@imap.cc \
--to=tilman@imap.cc \
--cc=gregkh@suse.de \
--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 \
/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).