From: Vladimir Oltean <olteanv@gmail.com>
To: Jerry.Ray@microchip.com
Cc: andrew@lunn.ch, f.fainelli@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk
Subject: Re: [PATCH net-next v4 1/2] dsa: lan9303: Whitespace Only
Date: Sat, 10 Dec 2022 00:13:41 +0200 [thread overview]
Message-ID: <20221209221341.23mtywxgp36ol4mn@skbuf> (raw)
In-Reply-To: <MWHPR11MB169375D09616C6EC3119B972EF1C9@MWHPR11MB1693.namprd11.prod.outlook.com>
On Fri, Dec 09, 2022 at 07:25:15PM +0000, Jerry.Ray@microchip.com wrote:
> Hi Vladimir,
>
> Thank you for your comments. I will rename the patch to be more explicit and
> will address the tabs-spaces issue you pointed out.
>
> I'll look for a better Linux-based text editor this weekend. Do you have a
> recommendation?
Text editors are more of a personal choice, I'm in no position to recommend
one over another. There are quite a few which fulfill the requirements of
proper code highlighting, given the right configuration.
next prev parent reply other threads:[~2022-12-09 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 23:28 [PATCH net-next v4 0/2] dsa: lan9303: Move to PHYLINK Jerry Ray
2022-12-07 23:28 ` [PATCH net-next v4 1/2] dsa: lan9303: Whitespace Only Jerry Ray
2022-12-08 17:11 ` Vladimir Oltean
2022-12-09 19:25 ` Jerry.Ray
2022-12-09 22:13 ` Vladimir Oltean [this message]
2022-12-07 23:28 ` [PATCH net-next v4 2/2] dsa: lan9303: Migrate to PHYLINK Jerry Ray
2022-12-08 17:21 ` Vladimir Oltean
2022-12-09 18:00 ` Jerry.Ray
2022-12-09 18:07 ` Vladimir Oltean
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=20221209221341.23mtywxgp36ol4mn@skbuf \
--to=olteanv@gmail.com \
--cc=Jerry.Ray@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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