From: Jose Abreu <jose.abreu@synopsys.com>
To: netdev@vger.kernel.org
Cc: Jose Abreu <jose.abreu@synopsys.com>,
Joao Pinto <joao.pinto@synopsys.com>,
"David S . Miller" <davem@davemloft.net>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>
Subject: [PATCH net 0/5] net: stmmac: Misc fixes
Date: Tue, 8 Jan 2019 15:51:04 +0100 [thread overview]
Message-ID: <cover.1546958941.git.joabreu@synopsys.com> (raw)
Some small fixes for stmmac targeting -net. Detailed info in commit log.
Cc: Joao Pinto <jpinto@synopsys.com>
Cc: David S. Miller <davem@davemloft.net>
Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>
Jose Abreu (5):
net: stmmac: Fix PCI module removal leak
net: stmmac: dwxgmac2: Only clear interrupts that are active
net: stmmac: Check if CBS is supported before configuring
net: stmmac: Fix the logic of checking if RX Watchdog must be enabled
net: stmmac: Prevent RX starvation in stmmac_napi_poll()
drivers/net/ethernet/stmicro/stmmac/dwxgmac2_dma.c | 6 +--
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 51 +++++++++++-----------
drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c | 10 +++++
drivers/net/ethernet/stmicro/stmmac/stmmac_tc.c | 2 +
4 files changed, 41 insertions(+), 28 deletions(-)
--
2.7.4
next reply other threads:[~2019-01-08 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 14:51 Jose Abreu [this message]
2019-01-08 14:51 ` [PATCH net 1/5] net: stmmac: Fix PCI module removal leak Jose Abreu
2019-01-09 1:43 ` kbuild test robot
2019-01-08 14:51 ` [PATCH net 2/5] net: stmmac: dwxgmac2: Only clear interrupts that are active Jose Abreu
2019-01-08 14:51 ` [PATCH net 3/5] net: stmmac: Check if CBS is supported before configuring Jose Abreu
2019-01-08 14:51 ` [PATCH net 4/5] net: stmmac: Fix the logic of checking if RX Watchdog must be enabled Jose Abreu
2019-01-08 14:51 ` [PATCH net 5/5] net: stmmac: Prevent RX starvation in stmmac_napi_poll() Jose Abreu
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=cover.1546958941.git.joabreu@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=joao.pinto@synopsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.