From: Oleg Nesterov <oleg@redhat.com>
To: Christopher Yeoh <cyeoh@au1.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cleanup of rw_copy_check_uvector and compat_rw_copy_check_uvector
Date: Thu, 5 Apr 2012 18:40:03 +0200 [thread overview]
Message-ID: <20120405164003.GA25667@redhat.com> (raw)
In-Reply-To: <20120201123422.57af1859@Gantu.yeoh.info>
On 02/01, Christopher Yeoh wrote:
>
> On Mon, 30 Jan 2012 14:01:28 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > Yes please. Put oneself in the position of a developer reading the
> > changelog two years from now.
> >
> > Also, please use our conventional comment layout style in fs.h.
>
> Updated changelog and patch below. Differences from last patch
Looks like this (imho good) cleanup was forgotten.
Christopher, perhaps you can re-send?
Oleg.
prev parent reply other threads:[~2012-04-05 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 4:21 [PATCH] Cleanup of rw_copy_check_uvector and compat_rw_copy_check_uvector Christopher Yeoh
2012-01-30 17:23 ` Oleg Nesterov
2012-01-30 22:01 ` Andrew Morton
2012-02-01 2:04 ` Christopher Yeoh
2012-04-05 16:40 ` Oleg Nesterov [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=20120405164003.GA25667@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cyeoh@au1.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).