From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI changes for 2.5.69
Date: Fri, 23 May 2003 00:02:15 -0700 [thread overview]
Message-ID: <20030523070215.GA9785@kroah.com> (raw)
In-Reply-To: <20030523070715.A5038@infradead.org>
On Fri, May 23, 2003 at 07:07:15AM +0100, Christoph Hellwig wrote:
> On Thu, May 22, 2003 at 03:06:01PM -0700, Greg KH wrote:
> > ChangeSet 1.1210, 2003/05/22 10:30:35-07:00, greg@kroah.com
> >
> > PCI: add pci_get_dev() and pci_put_dev()
> >
> > Move the PCI core to start using these, enabling proper reference counting
> > on struct pci_dev.
> >
> >
> > drivers/pci/bus.c | 2 +-
> > drivers/pci/hotplug.c | 2 +-
> > drivers/pci/pci-driver.c | 41 +++++++++++++++++++++++++++++++++++++++++
> > drivers/pci/probe.c | 18 ++++++++++++++++++
> > include/linux/pci.h | 2 ++
> > 5 files changed, 63 insertions(+), 2 deletions(-)
> >
> >
> > diff -Nru a/drivers/pci/bus.c b/drivers/pci/bus.c
> > --- a/drivers/pci/bus.c Thu May 22 14:50:44 2003
> > +++ b/drivers/pci/bus.c Thu May 22 14:50:44 2003
> > @@ -92,7 +92,7 @@
> > if (!list_empty(&dev->global_list))
> > continue;
> >
> > - device_register(&dev->dev);
> > + device_add(&dev->dev);
>
> This doesn't match the patch description..
Yes it does. "Move the PCI core to start..." describes exactly this
portion of the patch. We have to change from device_register() to
device_add() if we want to grab a reference count on the pci device
before we register it with the driver core. Which we do want to do,
because of the two stage process of creating and registering pci
devices.
> > +struct pci_dev *pci_get_dev (struct pci_dev *dev)
>
> Please fix up to adhere Documentation/CodingStyle (hint: placement
> of the opening brace is wrong).
CodingStyle doesn't _explicitly_ say that this is not allowed :)
I'll fix it next set of pci patches...
> > +{
> > + struct device *tmp;
> > +
> > + if (!dev)
> > + return NULL;
>
> Does it make sense to allow NULL argument here?
Just being safe. We can drop it if it really annoys you, but other
subsystems do the same thing.
greg k-h
next prev parent reply other threads:[~2003-05-23 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 22:02 [BK PATCH] PCI changes for 2.5.69 Greg KH
2003-05-22 22:05 ` [PATCH] " Greg KH
2003-05-22 22:05 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-22 22:06 ` Greg KH
2003-05-23 6:07 ` Christoph Hellwig
2003-05-23 7:02 ` Greg KH [this message]
2003-05-22 22:36 ` Dave Jones
2003-05-22 22:48 ` Greg KH
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=20030523070215.GA9785@kroah.com \
--to=greg@kroah.com \
--cc=hch@infradead.org \
--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