linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] More Driver Core patches for 2.6.10-rc1
Date: Thu, 4 Nov 2004 16:48:25 -0800	[thread overview]
Message-ID: <1099615705170@kroah.com> (raw)
In-Reply-To: <109961570456@kroah.com>

ChangeSet 1.2449.2.4, 2004/11/04 10:28:20-08:00, tj@home-tj.org

[PATCH] driver-model: comment fix in bus.c

 df_01_driver_attach_comment_fix.patch

bus_match() was renamed to driver_probe_device() but the comment for
device_attach() wasn't updated.  This patch updates it.


Signed-off-by: Tejun Heo <tj@home-tj.org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>


 drivers/base/bus.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)


diff -Nru a/drivers/base/bus.c b/drivers/base/bus.c
--- a/drivers/base/bus.c	2004-11-04 16:30:54 -08:00
+++ b/drivers/base/bus.c	2004-11-04 16:30:54 -08:00
@@ -325,10 +325,10 @@
  *	driver_attach - try to bind driver to devices.
  *	@drv:	driver.
  *
- *	Walk the list of devices that the bus has on it and try to match
- *	the driver with each one.
- *	If bus_match() returns 0 and the @dev->driver is set, we've found
- *	a compatible pair.
+ *	Walk the list of devices that the bus has on it and try to
+ *	match the driver with each one.  If driver_probe_device()
+ *	returns 0 and the @dev->driver is set, we've found a
+ *	compatible pair.
  *
  *	Note that we ignore the -ENODEV error from driver_probe_device(),
  *	since it's perfectly valid for a driver not to bind to any devices.


  reply	other threads:[~2004-11-05  1:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05  0:35 [BK PATCH] More USB patches for 2.6.10-rc1 Greg KH
2004-11-05  0:48 ` [PATCH] More Driver Core " Greg KH
2004-11-05  0:48   ` Greg KH
2004-11-05  0:48     ` Greg KH
2004-11-05  0:48       ` Greg KH [this message]
2004-11-05  0:48         ` Greg KH
2004-11-05  0:48           ` Greg KH
2004-11-05  0:48             ` Greg KH
2004-11-05  0:48               ` Greg KH
2004-11-05  0:48                 ` Greg KH
2004-11-05  0:48                   ` Greg KH
2004-11-05  0:48                     ` Greg KH
2004-11-05  0:48                       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2004-11-12 22:58 [BK PATCH] " Greg KH
2004-11-12 23:00 ` [PATCH] " Greg KH
2004-11-12 23:00   ` Greg KH
2004-11-12 23:00     ` Greg KH
2004-11-12 23:00       ` Greg KH
2004-11-12 23:00         ` Greg KH
2004-11-12 23:00           ` Greg KH
2004-11-12 23:00             ` Greg KH
2004-11-12 23:00               ` Greg KH
2004-11-12 23:00                 ` Greg KH
     [not found]     ` <20041113000052.GC346@electric-eye.fr.zoreil.com>
     [not found]       ` <200411130020.17494.lists@kenneth.aafloy.net>
2004-11-13  0:44         ` 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=1099615705170@kroah.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).