From: Greg KH <gregkh@linuxfoundation.org>
To: "Simon Sandström" <simon@nikanor.nu>
Cc: devel@driverdev.osuosl.org, gneukum1@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: kpc2000: fix brace issues in kpc2000_spi.c
Date: Mon, 1 Jul 2019 10:42:39 +0200 [thread overview]
Message-ID: <20190701084239.GA20886@kroah.com> (raw)
In-Reply-To: <20190627195323.28913-1-simon@nikanor.nu>
On Thu, Jun 27, 2019 at 09:53:23PM +0200, Simon Sandström wrote:
> Fixes issues found by checkpatch:
>
> - "WARNING: braces {} are not necessary for single statement blocks"
> - "WARNING: braces {} are not necessary for any arm of this statement"
>
> Signed-off-by: Simon Sandström <simon@nikanor.nu>
> ---
> drivers/staging/kpc2000/kpc2000_spi.c | 39 ++++++++++-----------------
> 1 file changed, 14 insertions(+), 25 deletions(-)
Patch does not apply to my tree :(
Please rebase it and resend.
thanks,
greg k-h
prev parent reply other threads:[~2019-07-01 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 19:53 [PATCH] staging: kpc2000: fix brace issues in kpc2000_spi.c Simon Sandström
2019-07-01 8:42 ` 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=20190701084239.GA20886@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gneukum1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@nikanor.nu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).