All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
	 outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: rtl8192u: ieee80211: Replace <asm/string.h>  with <linux/string.h>
Date: Fri, 20 Feb 2015 14:47:10 -0500	[thread overview]
Message-ID: <54E78F3E.7010704@gmail.com> (raw)
In-Reply-To: <1424460720-6136-1-git-send-email-ksenija.stanojevic@gmail.com>

On 02/20/15 14:32, Ksenija Stanojevic wrote:
> This patch fixes the following checkpatch.pl warning:
> Use #include <linux/string.h> instead of <asm/string.h>
> 
> Signed-off-by: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
> ---
>  drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c
> index 5533221..80dfa07 100644
> --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c
> +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.c
> @@ -15,7 +15,7 @@
>  #include <linux/module.h>
>  #include <linux/init.h>
>  #include <linux/slab.h>
> -#include <asm/string.h>
> +#include <linux/string.h>
>  #include <asm/errno.h>
>  
>  #include "ieee80211.h"
> 

I just noticed you were generating two patches for very similar changes
errno.h and string.h. Since these changes are to the same file and
basically identical changes, doing them both in one patch is preferred.

Cheers,
Jes



  reply	other threads:[~2015-02-20 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 19:32 [PATCH] Staging: rtl8192u: ieee80211: Replace <asm/string.h> with <linux/string.h> Ksenija Stanojevic
2015-02-20 19:47 ` Jes Sorensen [this message]
2015-02-20 20:45   ` [Outreachy kernel] " Ksenija Stanojević
2015-02-20 20:50     ` Julia Lawall
2015-02-20 21:12     ` Jes Sorensen

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=54E78F3E.7010704@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=ksenija.stanojevic@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.