From: Joe Perches <joe@perches.com>
To: Mark Salyzyn <salyzyn@android.com>
Cc: linux-kernel@vger.kernel.org, Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH v3 1/3] pstore: use scnprintf
Date: Tue, 06 Jan 2015 18:25:07 -0800 [thread overview]
Message-ID: <1420597507.28667.2.camel@perches.com> (raw)
In-Reply-To: <1420571907-13162-1-git-send-email-salyzyn@android.com>
On Tue, 2015-01-06 at 11:18 -0800, Mark Salyzyn wrote:
> No guarantees that the names will not exceed the
> name buffer with future adjustments.
It'd be nice to describe the changes between versions.
Typically, it's done after the --- line separating the
changelog and sign-off and the patch.
cheers, Joe
next prev parent reply other threads:[~2015-01-07 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 19:18 [PATCH v3 1/3] pstore: use scnprintf Mark Salyzyn
2015-01-07 2:25 ` Joe Perches [this message]
2015-01-07 15:47 ` Mark Salyzyn
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=1420597507.28667.2.camel@perches.com \
--to=joe@perches.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=salyzyn@android.com \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.