linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Paul Moore <paul@paul-moore.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Sabrina Dubroca <sd@queasysnail.net>,
	Paul Moore <pmoore@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] fs: namei: Use memcpy instead of strlcpy
Date: Wed, 21 Jan 2015 17:59:36 -0800	[thread overview]
Message-ID: <54C05988.8080306@roeck-us.net> (raw)
In-Reply-To: <14b0f192c78.2806.85c95baa4474aabc7814e68940a78392@paul-moore.com>

On 01/21/2015 04:44 PM, Paul Moore wrote:
> Good point.  Do you mind if I merge your patch into my existing patch instead of including it separately?
>
Sure, no problem. Go ahead.

Guenter


      reply	other threads:[~2015-01-22  1:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 22:44 [PATCH RESEND] fs: namei: Use memcpy instead of strlcpy Guenter Roeck
2015-01-22  0:44 ` Paul Moore
2015-01-22  1:59   ` Guenter Roeck [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=54C05988.8080306@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=pmoore@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=viro@zeniv.linux.org.uk \
    /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).