From: David Miller <davem@davemloft.net>
To: Jose.Abreu@synopsys.com
Cc: netdev@vger.kernel.org, Joao.Pinto@synopsys.com,
jakub.kicinski@netronome.com, peppe.cavallaro@st.com,
alexandre.torgue@st.com, mripard@kernel.org, wens@csie.org,
mcoquelin.stm32@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] net: stmmac: Improvements for -next
Date: Wed, 18 Dec 2019 12:14:21 -0800 (PST) [thread overview]
Message-ID: <20191218.121421.953588361074612907.davem@davemloft.net> (raw)
In-Reply-To: <cover.1576664538.git.Jose.Abreu@synopsys.com>
From: Jose Abreu <Jose.Abreu@synopsys.com>
Date: Wed, 18 Dec 2019 11:24:42 +0100
> Misc improvements for stmmac.
>
> 1) Adds more information regarding HW Caps in the DebugFS file.
>
> 2) Allows interrupts to be independently enabled or disabled so that we don't
> have to schedule both TX and RX NAPIs.
>
> 3) Stops using a magic number in coalesce timer re-arm.
Series applied, thanks.
prev parent reply other threads:[~2019-12-18 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 10:24 [PATCH net-next v3 0/3] net: stmmac: Improvements for -next Jose Abreu
2019-12-18 10:24 ` [PATCH net-next v3 1/3] net: stmmac: Print more information in DebugFS DMA Capabilities file Jose Abreu
2019-12-18 10:24 ` [PATCH net-next v3 2/3] net: stmmac: Let TX and RX interrupts be independently enabled/disabled Jose Abreu
2019-12-18 10:24 ` [PATCH net-next v3 3/3] net: stmmac: Always use TX coalesce timer value when rescheduling Jose Abreu
2019-12-18 20:14 ` 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=20191218.121421.953588361074612907.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Joao.Pinto@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=jakub.kicinski@netronome.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=wens@csie.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).