From: Greg KH <gregkh@linuxfoundation.org>
To: Jianshen Liu <ljishen@gmail.com>
Cc: devel@driverdev.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: ipx: fixed several no space before tabs coding style issues
Date: Thu, 28 Dec 2017 08:17:25 +0100 [thread overview]
Message-ID: <20171228071725.GA7712@kroah.com> (raw)
In-Reply-To: <1514409944-27794-1-git-send-email-ljishen@gmail.com>
On Wed, Dec 27, 2017 at 09:25:44PM +0000, Jianshen Liu wrote:
> Fixed several coding style warnings of "please, no space before tabs".
>
> Signed-off-by: Jianshen Liu <ljishen@gmail.com>
> ---
> drivers/staging/ipx/af_ipx.c | 56 ++++++++++++++++++++---------------------
> drivers/staging/ipx/ipx_proc.c | 2 +-
> drivers/staging/ipx/ipx_route.c | 6 ++---
> 3 files changed, 32 insertions(+), 32 deletions(-)
Please read drivers/staging/ipx/TODO
prev parent reply other threads:[~2017-12-28 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 21:25 [PATCH] Staging: ipx: fixed several no space before tabs coding style issues Jianshen Liu
2017-12-28 7:17 ` 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=20171228071725.GA7712@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljishen@gmail.com \
--cc=netdev@vger.kernel.org \
/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).