From: ebiederm@xmission.com (Eric W. Biederman)
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make Documentation/kobject.txt a little more coherent.
Date: Mon, 08 Dec 2008 14:52:39 -0800 [thread overview]
Message-ID: <m14p1ep9e0.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <200812090832.20403.rusty@rustcorp.com.au> (Rusty Russell's message of "Tue, 9 Dec 2008 08:32:14 +1030")
Rusty Russell <rusty@rustcorp.com.au> writes:
> While reading Documentation/kobject.txt:
>
> Note kobject_rename does perform any locking or have a solid notion of
> what names are valid so the provide must provide their own sanity checking
> and serialization.
>
> I expect better: You never see me hard with time word making sentence
> coherent stuff. Ever.
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Yes. That does sound better.
> diff --git a/Documentation/kobject.txt b/Documentation/kobject.txt
> --- a/Documentation/kobject.txt
> +++ b/Documentation/kobject.txt
> @@ -118,8 +118,8 @@ the name of the kobject, call kobject_re
>
> int kobject_rename(struct kobject *kobj, const char *new_name);
>
> -Note kobject_rename does perform any locking or have a solid notion of
> -what names are valid so the provide must provide their own sanity checking
> +kobject_rename does not perform any locking or have a solid notion of
> +what names are valid so the caller must provide their own sanity checking
> and serialization.
>
> There is a function called kobject_set_name() but that is legacy cruft and
prev parent reply other threads:[~2008-12-08 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 22:02 [PATCH] Make Documentation/kobject.txt a little more coherent Rusty Russell
2008-12-08 22:52 ` Eric W. Biederman [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=m14p1ep9e0.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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