All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madhumthia Prabakaran <madhumithabiw@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] Staging: vt6655: Fix line over 80 characters
Date: Mon, 4 Mar 2019 10:00:02 -0600	[thread overview]
Message-ID: <20190304160001.GA20855@madhuleo> (raw)
In-Reply-To: <20190304074530.GB22711@kroah.com>

On Mon, Mar 04, 2019 at 08:45:30AM +0100, Greg KH wrote:
> On Sun, Mar 03, 2019 at 07:19:49PM -0600, Madhumitha Prabakaran wrote:
> > Fix the warning issued by checkpatch.pl
> > WARNING: line over 80 characters
> > 
> > Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
> > ---
> >  drivers/staging/vt6655/card.h | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> You sent multiple patches with the same subject line, and no hint as to
> what order they need to be applied in.
> 
> 
> I have now removed all of your pending patches from my "to review"
> queue, please fix them up and resend them properly.
> 
> thanks,
> 
> greg k-h

I will resend all the patches.
I only have 2 patches with same subject lines, other three patches have different subject line.
So do you want me to include v2 in the patches or I can send it as same, as it is removed from your "to review" queue.

thanks,

Madhumitha



  reply	other threads:[~2019-03-04 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04  1:19 [PATCH] Staging: vt6655: Fix line over 80 characters Madhumitha Prabakaran
2019-03-04  7:42 ` [Outreachy kernel] " Julia Lawall
2019-03-04 16:02   ` Madhumthia Prabakaran
2019-03-04 17:23   ` Madhumthia Prabakaran
2019-03-04  7:45 ` Greg KH
2019-03-04 16:00   ` Madhumthia Prabakaran [this message]
2019-03-04 16:27     ` [Outreachy kernel] " Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2019-03-04  1:29 Madhumitha Prabakaran
2016-10-13 21:51 [PATCH] staging: " Varsha Rao
2016-10-14  7:27 ` Greg KH
2016-10-20 18:10   ` Varsha Rao
2016-10-24 13:29     ` Greg KH

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=20190304160001.GA20855@madhuleo \
    --to=madhumithabiw@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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.