From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: w.d.hubbs@gmail.com, devel@driverdev.osuosl.org, kirk@reisers.ca,
speakup@linux-speakup.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com, samuel.thibault@ens-lyon.org,
chris@the-brannons.com
Subject: Re: [PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations
Date: Thu, 9 Mar 2017 14:25:42 +0100 [thread overview]
Message-ID: <20170309132541.GB8690@kroah.com> (raw)
In-Reply-To: <20170303201709.19997-2-arushisinghal19971997@gmail.com>
On Sat, Mar 04, 2017 at 01:47:04AM +0530, Arushi Singhal wrote:
> This patch fixes the warnings reported by checkpatch.pl
> for please use a blank line after function/struct/union/enum
> declarations.
>
> Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
> ---
> drivers/staging/speakup/main.c | 1 +
> drivers/staging/speakup/serialio.c | 1 +
> drivers/staging/speakup/speakup_dtlk.c | 1 +
> 3 files changed, 3 insertions(+)
You seem to have sent me many different series of patches for this
driver, some of them the same, some different, some duplicates. I have
no idea what to apply and what not to apply, so I'm dropping them all
from my patch queue. Please fix up and resend a _single_ patch series
with your patches so I know what to review and possibly apply.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-09 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 20:17 [PATCH 0/6] multiple checkpatch issues Arushi Singhal
2017-03-03 20:17 ` [PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations Arushi Singhal
2017-03-09 13:25 ` Greg KH [this message]
[not found] ` <CA+XqjF_S9X5SmFo=AdSbPR8JnQvZzEye-xSnneF5eCm-6_G86Q@mail.gmail.com>
2017-03-09 16:24 ` Greg KH
2017-03-09 16:24 ` Greg KH
2017-03-03 20:17 ` [PATCH 2/6] staging: speakup: Logical continuations should be on the previous line Arushi Singhal
2017-03-03 20:17 ` [PATCH 3/6] staging: speakup: Blank lines removed after an open brace '{' Arushi Singhal
2017-03-03 20:17 ` [PATCH 4/6] staging: speakup: Avoid multiple assignments on same line Arushi Singhal
2017-03-03 20:17 ` [PATCH 5/6] staging: speakup: fixes braces {} should be used on all arms of this statement Arushi Singhal
2017-03-03 20:17 ` [PATCH 6/6] staging: speakup: Comparison to NULL could be written Arushi Singhal
-- strict thread matches above, loose matches on Subject: below --
2017-03-03 18:37 [PATCH 0/6] multiple checkpatch issues Arushi Singhal
2017-03-03 18:37 ` [PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations Arushi Singhal
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=20170309132541.GB8690@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.