All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: laerdevstudios@gmail.com
Cc: shraddha.6596@gmail.com, brcnakalin@gmail.com,
	driverdev-devel@linuxdriverproject.org,
	devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: netlogic: removed 1 multiple assignment checkpatch warning
Date: Tue, 15 Mar 2016 09:42:16 -0700	[thread overview]
Message-ID: <20160315164216.GA28895@kroah.com> (raw)
In-Reply-To: <1458058992-23450-1-git-send-email-laerdevstudios@gmail.com>

On Tue, Mar 15, 2016 at 04:23:12PM +0000, laerdevstudios@gmail.com wrote:
> From: Parth Sane <laerdevstudios@gmail.com>
> 
> diff --git a/drivers/staging/netlogic/platform_net.c b/drivers/staging/netlogic/platform_net.c
> index 7806c2b..daee1b2 100644
> --- a/drivers/staging/netlogic/platform_net.c
> +++ b/drivers/staging/netlogic/platform_net.c
> @@ -86,7 +86,8 @@ static void xlr_resource_init(struct resource *res, int offset, int irq)
>  
>  	res++;
>  	res->name = "gmac";
> -	res->start = res->end = irq;
> +	res->end = irq;
> +	res->start = res->end;
>  	res->flags = IORESOURCE_IRQ;
>  }
>  
> -- 
> 2.1.4


Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch does not have a Signed-off-by: line.  Please read the
  kernel file, Documentation/SubmittingPatches and resend it after
  adding that line.  Note, the line needs to be in the body of the
  email, before the patch, not at the bottom of the patch or in the
  email signature.

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/SubmittingPatches for what is needed in order to
  properly describe the change.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

  reply	other threads:[~2016-03-15 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 16:23 [PATCH] staging: netlogic: removed 1 multiple assignment checkpatch warning laerdevstudios
2016-03-15 16:42 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-15 16:46 laerdevstudios
2016-03-19 16:34 ` Parth Sane
2016-03-19 17:03   ` Roger H Newell
2016-03-19 17:09     ` Parth Sane
2016-03-19 17:13   ` Greg KH
2016-03-19 17:17     ` Parth Sane
2016-03-22  1:53 ` Greg KH
2016-03-11  9:22 laerdevstudios
2016-03-15 16:09 ` Michal Marek
2016-03-15 16:09   ` Michal Marek
2016-03-11  9:15 laerdevstudios
2016-03-11  9:18 ` Parth Sane

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=20160315164216.GA28895@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=brcnakalin@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=laerdevstudios@gmail.com \
    --cc=shraddha.6596@gmail.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.