All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tamara Diaconita <diaconitatamara@gmail.com>
Cc: aditya.shankar@microchip.com, ganesh.krishna@microchip.com,
	outreachy-kernel@googlegroups.com,
	Tamara Diaconita <diaconita.tamara@gmail.com>
Subject: Re: [PATCH] staging: wilc1000: linux_mon: Rearrange the code
Date: Thu, 9 Mar 2017 14:47:08 +0100	[thread overview]
Message-ID: <20170309134708.GA25303@kroah.com> (raw)
In-Reply-To: <20170307212751.4152-1-diaconita.tamara@gmail.com>

On Tue, Mar 07, 2017 at 11:27:51PM +0200, Tamara Diaconita wrote:
> Put a part of some lines in a new line to have less than 80 characters.
> 
> Fixed the checkpath.pl issue:
> CHECK: Line over 80 characters.
> 
> Signed-off-by: Tamara Diaconita <diaconita.tamara@gmail.com>
> ---
>  drivers/staging/wilc1000/linux_mon.c | 27 ++++++++++++++++++---------
>  1 file changed, 18 insertions(+), 9 deletions(-)

You have sent a lot of different patches for this driver over the past
few days, and I now have no idea what is, and what is not, a valid patch
:(

Can you please resend all of ythe patches I haven't applied yet, as a
patch series, properly linked together (i.e. reply-to is set), so that
they can be reviewed easily?

Remember, I have to deal with hundreds of patches, you want to make the
maintainers life _very_ easy to figure out what is, and is not, a valid
patch to apply.

thanks,

greg k-h


      reply	other threads:[~2017-03-09 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 21:27 [PATCH] staging: wilc1000: linux_mon: Rearrange the code Tamara Diaconita
2017-03-09 13:47 ` Greg KH [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=20170309134708.GA25303@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aditya.shankar@microchip.com \
    --cc=diaconita.tamara@gmail.com \
    --cc=diaconitatamara@gmail.com \
    --cc=ganesh.krishna@microchip.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.