From: "Denver Gingerich" <denver@ossguy.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] fix compiler warning in dd.c
Date: Sun, 20 May 2007 22:36:48 -0400 [thread overview]
Message-ID: <6defe8840705201936s7c011750w5bd4613b33eb9c70@mail.gmail.com> (raw)
In-Reply-To: <6defe8840705091829h44b78dc2w44f07c0993469128@mail.gmail.com>
This patch had been suggested by Indan Zupancic on May 13 but is not
in 2.6.22-rc2 so I'm re-sending it. Prior to Indan's e-mail, I had
sent the same patch to the kernel janitors list. I don't care whether
you credit the patch to me or Indan.
Denver
---------- Forwarded message ----------
From: Denver Gingerich <denver@ossguy.com>
Date: May 9, 2007 9:29 PM
Subject: [PATCH] fix compiler warning in dd.c
To: kernel-janitors@lists.linux-foundation.org
Correct the following compiler warning:
warning: 'device_probe_drivers' defined but not used
Verified that there are no device_probe_drivers() calls in the kernel tree.
Signed-off-by: Denver Gingerich <denver@ossguy.com>
---
--- linux-2.6.21/drivers/base/dd.c.000 2007-05-09 18:56:24.000000000 -0400
+++ linux-2.6.21/drivers/base/dd.c 2007-05-09 20:38:12.000000000 -0400
@@ -207,19 +207,6 @@ static int __device_attach(struct device
return driver_probe_device(drv, dev);
}
-static int device_probe_drivers(void *data)
-{
- struct device *dev = data;
- int ret = 0;
-
- if (dev->bus) {
- down(&dev->sem);
- ret = bus_for_each_drv(dev->bus, NULL, dev, __device_attach);
- up(&dev->sem);
- }
- return ret;
-}
-
/**
* device_attach - try to attach device to a driver.
* @dev: device.
next parent reply other threads:[~2007-05-21 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6defe8840705091829h44b78dc2w44f07c0993469128@mail.gmail.com>
2007-05-21 2:36 ` Denver Gingerich [this message]
2007-05-21 10:41 ` Cornelia Huck
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=6defe8840705201936s7c011750w5bd4613b33eb9c70@mail.gmail.com \
--to=denver@ossguy.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
all inboxes | Powered by JetHome®