From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Heiko Carstens" <heiko.carstens@de.ibm.com>
Cc: "Cornelia Huck" <cornelia.huck@de.ibm.com>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Greg KH" <greg@kroah.com>
Subject: Re: s390: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Thu, 30 Oct 2008 15:58:21 +0100 [thread overview]
Message-ID: <ac3eb2510810300758yf0df0e8j43875dd7c98a56c@mail.gmail.com> (raw)
In-Reply-To: <20081030113831.GA3871@osiris.boeblingen.de.ibm.com>
On Thu, Oct 30, 2008 at 12:38, Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> On Thu, Oct 30, 2008 at 10:32:00AM +0100, Cornelia Huck wrote:
>> On Thu, 30 Oct 2008 01:57:07 +0100,
>> Kay Sievers <kay.sievers@vrfy.org> wrote:
>>
>> > From: Kay Sievers <kay.sievers@vrfy.org>
>> > Subject: s390: struct device - replace bus_id with dev_name(), dev_set_name()
>> >
>> > Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
>> > Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
>> > Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
>> > Signed-Off-By: Kay Sievers <kay.sievers@vrfy.org>
>>
>> Other than the fact that this patch is a bit mis-named (it just gets
>> rid of BUS_ID_SIZE), this looks fine to me.
Yeah, sorry, it's one of the 49 patches, where the subjects isn't
right, because you did the conversion already. :)
> Who is supposed to send this upstream and when?
Would be fine if it goes through the s390 tree, and gets merged there
soon so it shows up in -next.
Thanks,
Kay
next prev parent reply other threads:[~2008-10-30 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 0:57 Kay Sievers
2008-10-30 9:32 ` Cornelia Huck
2008-10-30 11:38 ` Heiko Carstens
2008-10-30 14:58 ` Kay Sievers [this message]
2008-10-30 15:46 ` Heiko Carstens
2008-10-30 15:51 ` Kay Sievers
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=ac3eb2510810300758yf0df0e8j43875dd7c98a56c@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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®