All of lore.kernel.org
 help / color / mirror / Atom feed
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>,
	outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 0/2] Use #include <linux/uaccess.h> instead of <asm/uaccess.h>
Date: Fri, 20 Feb 2015 13:18:16 +0530	[thread overview]
Message-ID: <54E6E6C0.1090605@linux.vnet.ibm.com> (raw)
In-Reply-To: <cover.1424395309.git.mahfouz.saif.elyazal@gmail.com>

Hi Aya,

On 02/20/2015 07:13 AM, Aya Mahfouz wrote:
> This patchset replaces <asm/uaccess.h> by <linux/uaccess.h>. The
> replacements is safe since the header file <linux/uaccess.h> includes
> <asm/uaccess.h>

Like Julia mentioned its a thoughtful comment. Such explanations are
encouraged. However, it will be more valuable to include the above
explanation in the changelogs of the patches also since those go into
the git log of the kernel. The cover letter contains an overview of the
patchset to help the reviewers. They do not get documented in the
history of changes to the kernel. Would you therefore be able to resend
this as a fresh version including the above lines in the changelog of
the individual patches?

Regards
Preeti U Murthy
> 
> Aya Mahfouz (2):
>   staging: i2o: Use #include <linux/uaccess.h> instead of
>     <asm/uaccess.h>
>   staging: i2o: Use #include <linux/uaccess.h> instead of
>     <asm/uaccess.h>
> 
>  drivers/staging/i2o/i2o_config.c | 3 +--
>  drivers/staging/i2o/i2o_proc.c   | 2 +-
>  2 files changed, 2 insertions(+), 3 deletions(-)
> 



  parent reply	other threads:[~2015-02-20  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  1:43 [PATCH 0/2] Use #include <linux/uaccess.h> instead of <asm/uaccess.h> Aya Mahfouz
2015-02-20  1:43 ` [PATCH 1/2] staging: i2o: " Aya Mahfouz
2015-02-20  1:44 ` [PATCH 2/2] " Aya Mahfouz
2015-02-20  7:20 ` [Outreachy kernel] [PATCH 0/2] " Julia Lawall
2015-02-20  7:48 ` Preeti U Murthy [this message]
2015-02-21  4:30   ` Aya Mahfouz

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=54E6E6C0.1090605@linux.vnet.ibm.com \
    --to=preeti@linux.vnet.ibm.com \
    --cc=mahfouz.saif.elyazal@gmail.com \
    --cc=outreachy-kernel@googlegroups.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.