From: Chris Wright <chris@wirex.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] PCI device list locking - take 3
Date: Thu, 19 Jun 2003 11:49:01 -0700 [thread overview]
Message-ID: <20030619114901.A23053@figure1.int.wirex.com> (raw)
In-Reply-To: <20030619181412.GA5257@kroah.com>; from greg@kroah.com on Thu, Jun 19, 2003 at 11:14:12AM -0700
* Greg KH (greg@kroah.com) wrote:
> Here's the latest version of the pci list locking patch. I've taken
> Chris's comments and addressed them by making sure we don't walk off the
> end of a deleted device in the pci_find_* and pci_get_* functions.
Looks good. Perhaps the pci_proc_detach should be earlier (i.e. before
list removal) to reflect the order in which things are added. I'm not
sure of the dependencies, but seems a good practice anyway.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2003-06-19 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 18:14 [RFC] PCI device list locking - take 3 Greg KH
2003-06-19 18:49 ` Chris Wright [this message]
2003-06-19 19:14 ` 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=20030619114901.A23053@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=greg@kroah.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