From: David Miller <davem@davemloft.net>
To: michal.simek@xilinx.com
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
netdev@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com
Subject: Re: [PATCH] net: phy: Use tab for indentation in Kconfig
Date: Tue, 08 Aug 2017 21:05:37 -0700 (PDT) [thread overview]
Message-ID: <20170808.210537.1599851067118765908.davem@davemloft.net> (raw)
In-Reply-To: <abacdc7ec0585cfbeba240ca2780c6020cf7090a.1502184742.git.michal.simek@xilinx.com>
From: Michal Simek <michal.simek@xilinx.com>
Date: Tue, 8 Aug 2017 11:32:25 +0200
> Using tabs instead of space for indentaion
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
This really isn't appropriate for the 'net' tree, it doesn't fix
anything it just makes the spacing consistent.
Please respin this patch against net-next, thank you.
next prev parent reply other threads:[~2017-08-09 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 9:32 [PATCH] net: phy: Use tab for indentation in Kconfig Michal Simek
2017-08-08 14:10 ` Andrew Lunn
2017-08-09 4:05 ` David Miller [this message]
2017-08-11 12:50 ` Michal Simek
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=20170808.210537.1599851067118765908.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--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).