From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Straube <straube.linux@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] staging: rtl8188eu: cleanup declarations in os_intfs.c
Date: Tue, 15 Jan 2019 16:25:33 +0100 [thread overview]
Message-ID: <20190115152533.GA4323@kroah.com> (raw)
In-Reply-To: <20190115082402.8519-2-straube.linux@gmail.com>
On Tue, Jan 15, 2019 at 09:24:01AM +0100, Michael Straube wrote:
> Replace tabs with spaces and/or remove extra spaces in declarations.
> ---
> drivers/staging/rtl8188eu/os_dep/os_intfs.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
No signed off by :(
next prev parent reply other threads:[~2019-01-15 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 8:24 [PATCH 1/3] staging: rtl8188eu: remove unnecessary parentheses in os_intfs.c Michael Straube
2019-01-15 8:24 ` [PATCH 2/3] staging: rtl8188eu: cleanup declarations " Michael Straube
2019-01-15 15:25 ` Greg KH [this message]
2019-01-15 8:24 ` [PATCH 3/3] staging: rtl8188eu: add spaces around operators " Michael Straube
2019-01-15 15:25 ` 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=20190115152533.GA4323@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=straube.linux@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;
as well as URLs for NNTP newsgroup(s).