From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] driver/core: Fix various warnings due to dev_set_name() usage
Date: Wed, 17 Jun 2009 14:06:04 +1000 [thread overview]
Message-ID: <1245211564.21602.19.camel@pasglop> (raw)
In-Reply-To: <20090617025134.GA6807@kroah.com>
On Tue, 2009-06-16 at 19:51 -0700, Greg KH wrote:
>
> These have all been fixed in linux-next for a while, and are already
> contained in the patchset I sent to Linus for inclusion in his tree
> yesterday.
>
> But thanks anyway :)
Argh, oh well ... I should have waited one more day :-)
Cheers,
Ben.
prev parent reply other threads:[~2009-06-17 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 1:45 [PATCH] driver/core: Fix various warnings due to dev_set_name() usage Benjamin Herrenschmidt
2009-06-17 2:51 ` Greg KH
2009-06-17 4:06 ` Benjamin Herrenschmidt [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=1245211564.21602.19.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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