From: Jonathan Corbet <corbet@lwn.net>
To: Jose Abreu <Jose.Abreu@synopsys.com>
Cc: netdev@vger.kernel.org, Joao Pinto <Joao.Pinto@synopsys.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
"David S. Miller" <davem@davemloft.net>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-doc@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] Documentation: stmmac documentation improvements
Date: Tue, 7 Jan 2020 13:09:18 -0700 [thread overview]
Message-ID: <20200107130918.205762b6@lwn.net> (raw)
In-Reply-To: <cover.1578392890.git.Jose.Abreu@synopsys.com>
On Tue, 7 Jan 2020 11:37:17 +0100
Jose Abreu <Jose.Abreu@synopsys.com> wrote:
> [ Not sure if this should go for net-next or Documentation tree. ]
Patches for networking docs generally go through the networking trees; I'm
assuming that will happen here as well. The changes look generally good
to me, FWIW.
Thanks,
jon
next prev parent reply other threads:[~2020-01-07 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 10:37 [PATCH net-next 0/3] Documentation: stmmac documentation improvements Jose Abreu
2020-01-07 10:37 ` [PATCH net-next 1/3] MAINTAINERS: Add stmmac Ethernet driver documentation entry Jose Abreu
2020-01-07 10:37 ` [PATCH net-next 2/3] Documentation: networking: Convert stmmac documentation to RST format Jose Abreu
2020-01-07 10:37 ` [PATCH net-next 3/3] Documentation: networking: Add stmmac to device drivers list Jose Abreu
2020-01-07 20:09 ` Jonathan Corbet [this message]
2020-01-07 21:39 ` [PATCH net-next 0/3] Documentation: stmmac documentation improvements David Miller
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=20200107130918.205762b6@lwn.net \
--to=corbet@lwn.net \
--cc=Joao.Pinto@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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).