All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: w.d.hubbs@gmail.com, chris@the-brannons.com,
	outreachy-kernel@googlegroups.com, kirk@reisers.ca,
	samuel.thibault@ens-lyon.org, speakup@linux-speakup.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] staging:speakup: Multiple checkpatch issues,
Date: Tue, 21 Mar 2017 07:11:08 +0100	[thread overview]
Message-ID: <20170321061108.GA5524@kroah.com> (raw)
In-Reply-To: <20170319131455.25007-1-arushisinghal19971997@gmail.com>

On Sun, Mar 19, 2017 at 06:44:53PM +0530, Arushi Singhal wrote:
> Improve readability by fixing multiple checkpatch.pl
> issues in speakup driver.
> 
> Arushi Singhal (2):
>   staging: speakup: Moved OR operator to previous line.
>   staging: speakup: spaces preferred around operator

You have sent many different speakup patches, in different series, and
then a bunch of individual patches all at once.  I have no idea what to
apply here, what order they go in, or even which ones should be
reviewed.

So I've dropped all of them from my patch queue.  Please resend all of
your outstanding speakup patches, in a _single_ patch series, so that
they can be reviewed in the correct order.

thanks,

greg k-h


  parent reply	other threads:[~2017-03-21  6:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 13:14 [PATCH v2 0/2] staging:speakup: Multiple checkpatch issues, Arushi Singhal
2017-03-19 13:14 ` [PATCH v2 1/2] staging: speakup: Moved OR operator to previous line Arushi Singhal
2017-03-19 13:14 ` [PATCH v2 2/2] staging: speakup: spaces preferred around operator Arushi Singhal
2017-03-21  6:11 ` Greg KH [this message]
2017-03-21  6:33   ` [PATCH v2 0/2] staging:speakup: Multiple checkpatch issues, Arushi Singhal
2017-03-21  6:55     ` Greg KH
2017-03-21  6:55       ` 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=20170321061108.GA5524@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arushisinghal19971997@gmail.com \
    --cc=chris@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@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.