From: Greg KH <gregkh@linuxfoundation.org>
To: Johannes Czekay <johannes.czekay@fau.de>
Cc: nicolai.fischer@fau.de, jbwyatt4@gmail.com, rkovhaev@gmail.com,
hqjagain@gmail.com, gustavo@embeddedor.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH 1/6] wlan-ng: clean up line ending
Date: Wed, 27 Jan 2021 14:58:15 +0100 [thread overview]
Message-ID: <YBFxd23HvY7ziOjB@kroah.com> (raw)
In-Reply-To: <20210118010955.48663-2-johannes.czekay@fau.de>
On Mon, Jan 18, 2021 at 02:09:51AM +0100, Johannes Czekay wrote:
> This patch cleans up all the "Lines should not end with a '('" warnings.
>
> Signed-off-by: Johannes Czekay <johannes.czekay@fau.de>
> Co-developed-by: Nicolai Fischer <nicolai.fischer@fau.de>
> Signed-off-by: Nicolai Fischer <nicolai.fischer@fau.de>
> ---
> drivers/staging/wlan-ng/cfg80211.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
When you resend this series, please remember to add "staging: " to the
prefix of all of the commit so I know to pick it up.
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-27 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 1:09 [PATCH 0/6] wlan-ng: checkpatch.pl cleanup series Johannes Czekay
2021-01-18 1:09 ` [PATCH 1/6] wlan-ng: clean up line ending Johannes Czekay
2021-01-27 13:58 ` Greg KH [this message]
2021-01-18 1:09 ` [PATCH 2/6] wlan-ng: clean up spinlock_t definition Johannes Czekay
2021-01-18 1:09 ` [PATCH 3/6] wlan-ng: rename macros Johannes Czekay
2021-01-18 1:09 ` [PATCH 4/6] wlan-ng: clean up line length Johannes Czekay
2021-01-18 1:09 ` [PATCH 5/6] wlan-ng: clean up alignment Johannes Czekay
2021-01-18 1:09 ` [PATCH 6/6] wlan-ng: clean up reused macros Johannes Czekay
2021-01-19 9:33 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2020-12-22 22:20 [PATCH 0/6] wlan-ng: checkpatch.pl cleanup series Johannes Czekay
2020-12-22 22:20 ` [PATCH 1/6] wlan-ng: clean up line ending Johannes Czekay
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=YBFxd23HvY7ziOjB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gustavo@embeddedor.com \
--cc=hqjagain@gmail.com \
--cc=jbwyatt4@gmail.com \
--cc=johannes.czekay@fau.de \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolai.fischer@fau.de \
--cc=rkovhaev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox