netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Greg KH <greg@kroah.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-pci@atrey.karlin.mff.cuni.cz, Adrian Bunk <bunk@stusta.de>,
	Andrew Morton <akpm@osdl.org>, Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error
Date: Tue, 06 Mar 2007 19:15:12 +0300	[thread overview]
Message-ID: <45ED9390.3000308@ru.mvista.com> (raw)
In-Reply-To: <20070226211401.GC3810@kroah.com>

Hello.

Greg KH wrote:

>>>>>>>3x59x-fix-pci-resource-management.patch causes the following compile 
>>>>>>>error with CONFIG_PCI=n:

>>>>>>><--  snip  -->

>>>>>>>...
>>>>>>>  CC      drivers/net/3c59x.o
>>>>>>>/home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: 
>>>>>>>In function 'vortex_init_one':
>>>>>>>/home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c:961: 
>>>>>>>error: implicit declaration of function 'pci_request_regions'
>>>>>>>/home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c:985: 
>>>>>>>error: implicit declaration of function 'pci_release_regions'
>>>>>>>make[3]: *** [drivers/net/3c59x.o] Error 1

>>>>>>   Grr, at at the same time it's happy with pci_enable_device().
>>>>>>   I'd say the problem is in <linux/pci.h>,  not in the patch.

>>>>>   Has there been any patch to fix the "unbalanced" 
>>>>>pci_{request|release}_regions() declarations? Am I suposed to create 
>>>>>such?

>>>>   Alternatively, vortex_{init|remove_one() and struct pci_driver there 
>>>>could have been put under #ifdef CONFIG_PCI (good idea anyway -- should 
>>>>reduce driver size on non-PCI systems)...

>>>    I wonder if I may count on any feedback on this -- asking linux-pci now...
>>>    The issue is as follows: with my patch pci_{request|release}_regions() may 
>>>be called with CONFIG_PCI=n (probably, this never has been a issue before) but 
>>><linux/pci.h> don't have them declared in this case -- unlike 
>>>pci_enable_device() which is just empty for CONFIG_PCI=n.
>>>    Now, what kind of approach do I take:

>>>- a "fair one", so that pci_{request|release}_regions() get "balanced"
>>>   declarations in the header like pci_enable_device();

>>>- a "local one" (and even saving non-PCI kernel from needless bloat), i.e.
>>>   #ifdef out functions that are only meaningful with CONFIG_PCI=y)?

>>>    I'm leaning to the second now...

>>I'd prefer the fair one -- add stubs to include/linux/pci.h.

> Me too, please just send me a patch adding them to pci.h so you don't
> have to have #ifdefs in your .c code.

    Erm, before I do that, could somebody explain what

#define HAVE_PCI_REQ_REGIONS 2

accompanying their declaration is for? I have't found any references to it in 
the source. Should I duplicate it for CONFIG_PCI=n case (I guess not)?

> thanks,

> greg k-h

WBR, Sergei

  reply	other threads:[~2007-03-06 16:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070111222627.66bb75ab.akpm@osdl.org>
2007-01-21 19:13 ` [-mm patch] remove one remaining "#define BCM_TSO 1" Adrian Bunk
2007-01-24 13:53 ` 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error Adrian Bunk
2007-01-24 14:12   ` Sergei Shtylyov
2007-02-17 19:26     ` Sergei Shtylyov
2007-02-17 19:32       ` Sergei Shtylyov
2007-02-26 13:22         ` Sergei Shtylyov
2007-02-26 17:26           ` Randy Dunlap
2007-02-26 21:14             ` Greg KH
2007-03-06 16:15               ` Sergei Shtylyov [this message]
2007-03-06 16:47                 ` Randy Dunlap
2007-03-09 12:54                   ` Tejun Heo

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=45ED9390.3000308@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.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;
as well as URLs for NNTP newsgroup(s).