From: David Brownell <david-b@pacbell.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: spi: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Wed, 29 Oct 2008 23:35:17 -0700 [thread overview]
Message-ID: <200810292335.17631.david-b@pacbell.net> (raw)
In-Reply-To: <1225330937.5970.99.camel@nga.site>
On Wednesday 29 October 2008, Kay Sievers wrote:
> From: Kay Sievers <kay.sievers@vrfy.org>
> Subject: spi: struct device - replace bus_id with dev_name(), dev_set_name()
>
> Cc: David Brownell <dbrownell@users.sourceforge.net>
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-Off-By: Kay Sievers <kay.sievers@vrfy.org>
Acked-by: David Brownell <dbrownell@users.sourceforge.net>
... OK by me if this goes into 2.6.28. There's one more use
of spi->dev.bus_id that I know about, in the spi_gpio driver
currently found in the MM tree.
prev parent reply other threads:[~2008-10-30 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 1:42 Kay Sievers
2008-10-30 6:35 ` David Brownell [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=200810292335.17631.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.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
all inboxes | Powered by JetHome®