From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] export PCI resources in sysfs
Date: Tue, 21 Dec 2004 12:18:31 -0800 [thread overview]
Message-ID: <20041221201830.GA9693@kroah.com> (raw)
In-Reply-To: <200412211156.39491.jbarnes@engr.sgi.com>
On Tue, Dec 21, 2004 at 11:56:39AM -0800, Jesse Barnes wrote:
> On Tuesday, December 21, 2004 11:09 am, Jesse Barnes wrote:
> > > How about wrapping these two #ifdef blocks into one function, and moving
> > > it up in the file under the other #ifdef. Do that for the other cleanup
> > > function, and it will drop a bunch of #ifdefs.
> >
> > Yeah, that sounds good. I really don't like adding these ifdefs, and
> > limiting their scope to a function somewhere up above would be nicer. I'll
> > do that and respin.
>
> Ok, here you go.
>
> This patch exports PCI resources to userspace in the corresponding sysfs
> device directory. It depends on the platform HAVE_PCI_MMAP code, and is
> #ifdef'd accordingly. I've also added documentation describing the sysfs PCI
> device file layout.
>
> Signed-off-by: Jesse Barnes <jbarnes@sgi.com>
Looks good, I made one tiny change:
> +#else /* !HAVE_PCI_MMAP */
> +static void pci_create_resource_files(struct pci_dev *dev) { return; }
> +static void pci_remove_resource_files(struct pci_dev *dev) { return; }
> +#endif /* HAVE_PCI_MMAP */
I made these inline to have the compiler just "make them go away" for
when that define isn't enabled.
Applied to my trees,
thanks,
greg k-h
prev parent reply other threads:[~2004-12-21 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 17:43 [PATCH] export PCI resources in sysfs Jesse Barnes
2004-12-21 18:43 ` Greg KH
2004-12-21 19:09 ` Jesse Barnes
2004-12-21 19:56 ` Jesse Barnes
2004-12-21 20:18 ` Greg KH [this message]
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=20041221201830.GA9693@kroah.com \
--to=greg@kroah.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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