From: Andrew Morton <akpm@osdl.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: greg@kroah.com, linux-pci@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][UPDATE] PCI: Add pci_assign_resource_fixed -- allow fixed address assignments
Date: Thu, 27 Apr 2006 21:43:57 -0700 [thread overview]
Message-ID: <20060427214357.4eacd58f.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0604272328380.5047-100000@gate.crashing.org>
Kumar Gala <galak@kernel.crashing.org> wrote:
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 2329f94..955a96e 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -947,6 +947,9 @@ EXPORT_SYMBOL_GPL(pci_intx);
> EXPORT_SYMBOL(pci_set_dma_mask);
> EXPORT_SYMBOL(pci_set_consistent_dma_mask);
> EXPORT_SYMBOL(pci_assign_resource);
> +#ifdef CONFIG_EMBEDDED
> +EXPORT_SYMBOL(pci_assign_resource_fixed);
> +#endif
This is a good argument for putting the export at the definition site ;)
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -496,6 +496,9 @@ int pci_set_dma_mask(struct pci_dev *dev
> int pci_set_consistent_dma_mask(struct pci_dev *dev, u64 mask);
> void pci_update_resource(struct pci_dev *dev, struct resource *res, int resno);
> int pci_assign_resource(struct pci_dev *dev, int i);
> +#ifdef CONFIG_EMBEDDED
> +int pci_assign_resource_fixed(struct pci_dev *dev, int i);
> +#endif
Debatable - if we omit the ifdefs, it fails at link time or depmod time.
The ifdefs will make it warn (but not fail) at compile-time. Given that
the warning is non-fatal, the ifdefs don't add much value and are best
omitted.
next prev parent reply other threads:[~2006-04-28 4:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 17:43 [PATCH] PCI: Add pci_assign_resource_fixed -- allow fixed address assignments Kumar Gala
2006-04-27 22:34 ` Andrew Morton
2006-04-28 0:12 ` Kumar Gala
2006-04-28 0:17 ` Greg KH
2006-04-28 4:29 ` [PATCH][UPDATE] " Kumar Gala
2006-04-28 4:43 ` Andrew Morton [this message]
2006-04-28 14:52 ` Kumar Gala
2006-05-01 15:43 ` Kumar Gala
2006-05-02 13:13 ` Pavel Machek
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=20060427214357.4eacd58f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox