public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: [PATCH] Make Documentation/kobject.txt a little more coherent.
Date: Tue, 9 Dec 2008 08:32:14 +1030	[thread overview]
Message-ID: <200812090832.20403.rusty@rustcorp.com.au> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1159 bytes --]

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 sentencecoherent stuff.  Ever.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
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\0ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

             reply	other threads:[~2008-12-08 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 22:02 Rusty Russell [this message]
2008-12-08 22:52 ` [PATCH] Make Documentation/kobject.txt a little more coherent Eric W. Biederman

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=200812090832.20403.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --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