From: Tabi Timur-B04825 <B04825@freescale.com>
To: Greg KH <greg@kroah.com>
Cc: <kay.sievers@vrfy.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] driver-core: document restrictions on device_rename()
Date: Fri, 10 Dec 2010 16:47:49 -0700 [thread overview]
Message-ID: <E9E64D4D-F204-4EEE-B0F4-FE106B7BD8CA@freescale.com> (raw)
In-Reply-To: <20101210231254.GA9845@kroah.com>
I'm on vacation, so it'll have to wait until Monday.
On Dec 10, 2010, at 4:17 PM, "Greg KH" <greg@kroah.com> wrote:
> On Wed, Dec 01, 2010 at 05:40:54PM -0600, Timur Tabi wrote:
>> Add text, courtesy of Kay Sievers, that provides some background on
>> device_rename() and why it shouldn't be used.
>>
>> Signed-off-by: Timur Tabi <timur@freescale.com>
>> ---
>> drivers/base/core.c | 28 ++++++++++++++++++++++++++++
>
> This patch doesn't apply to the linux-next branch, care to refresh it so
> I can apply it?
>
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2010-12-10 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 23:40 [PATCH] driver-core: document restrictions on device_rename() Timur Tabi
2010-12-10 23:12 ` Greg KH
2010-12-10 23:47 ` Tabi Timur-B04825 [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=E9E64D4D-F204-4EEE-B0F4-FE106B7BD8CA@freescale.com \
--to=b04825@freescale.com \
--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;
as well as URLs for NNTP newsgroup(s).