From: Jonathan Corbet <corbet@lwn.net>
To: ulfalizer.lkml@gmail.com
Cc: gregkh@linuxfoundation.org, shane.seymour@hp.com,
ulfalizer@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysfs.txt: mention that store method buffers are null-terminated
Date: Sat, 12 Sep 2015 14:19:18 -0600 [thread overview]
Message-ID: <20150912141918.6d8e4ee5@lwn.net> (raw)
In-Reply-To: <1441645574-6043-1-git-send-email-ulfalizer.lkml@gmail.com>
On Mon, 7 Sep 2015 19:06:14 +0200
ulfalizer.lkml@gmail.com wrote:
> Without knowing this, the use of sysfs_streq() becomes puzzling.
>
> The termination happens in kernfs_fop_write().
Applied to the docs tree. I moved it up a paragraph, though, since it
better fits the flow of the document there.
Thanks,
jon
prev parent reply other threads:[~2015-09-12 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 17:06 ulfalizer.lkml
2015-09-12 20:19 ` Jonathan Corbet [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=20150912141918.6d8e4ee5@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shane.seymour@hp.com \
--cc=ulfalizer.lkml@gmail.com \
--cc=ulfalizer@gmail.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®