public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Joel Becker <joel.becker@oracle.com>,
	Andries Brouwer <aeb@cwi.nl>
Subject: Re: [PATCH] fs: Prefer strlcpy() over snprintf()
Date: Fri, 9 May 2008 17:35:13 +0200	[thread overview]
Message-ID: <20080509173513.328eff12@hyperion.delvare> (raw)
In-Reply-To: <1210335354.3635.486.camel@quoit>

Hi Steven,

On Fri, 09 May 2008 13:15:54 +0100, Steven Whitehouse wrote:
> The patch looks good, but could you break this into bits? Its easier for
> me just to put the GFS2 bit through my git tree and the other bits
> should probably go via another route,

Thanks for the review. No problem, I'll split the patch and send the
individual bits to their respective maintainers now.

-- 
Jean Delvare

      reply	other threads:[~2008-05-09 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 11:42 [PATCH] fs: Prefer strlcpy() over snprintf() Jean Delvare
2008-05-09 12:15 ` Steven Whitehouse
2008-05-09 15:35   ` Jean Delvare [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=20080509173513.328eff12@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=aeb@cwi.nl \
    --cc=joel.becker@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swhiteho@redhat.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