From: David Miller <davem@davemloft.net>
To: alexander.duyck@gmail.com
Cc: shmulik.ladkani@gmail.com, netdev@vger.kernel.org, ecree@solarflare.com
Subject: Re: [PATCH] Documentation/networking: more accurate LCO explanation
Date: Fri, 06 May 2016 12:50:20 -0400 (EDT) [thread overview]
Message-ID: <20160506.125020.467917589097597961.davem@davemloft.net> (raw)
In-Reply-To: <CAKgT0UcpbKVpip0pSaCOY7xVQ=3wwUxFing7Sht8ptH8VRB=FA@mail.gmail.com>
From: Alexander Duyck <alexander.duyck@gmail.com>
Date: Fri, 6 May 2016 09:29:56 -0700
> I don't really see the point of using an underscore before and after
> that statement. If it was only one or two words it might work for
> emphasis but the statement is large enough that starting it with an
> underscore just makes it harder to read.
Agreed.
prev parent reply other threads:[~2016-05-06 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 15:57 [PATCH] Documentation/networking: more accurate LCO explanation Shmulik Ladkani
2016-05-06 16:12 ` Edward Cree
2016-05-06 16:29 ` Alexander Duyck
2016-05-06 16:50 ` David Miller [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=20160506.125020.467917589097597961.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=ecree@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@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).