From: David Miller <davem@davemloft.net>
To: biao.huang@mediatek.com
Cc: joabreu@synopsys.com, andrew@lunn.ch, peppe.cavallaro@st.com,
alexandre.torgue@st.com, mcoquelin.stm32@gmail.com,
matthias.bgg@gmail.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
yt.shen@mediatek.com, jianguo.zhang@mediatek.com,
boon.leong.ong@intel.com
Subject: Re: [v2, PATCH 0/4] complete dwmac-mediatek driver and fix flow control issue
Date: Wed, 05 Jun 2019 17:03:28 -0700 (PDT) [thread overview]
Message-ID: <20190605.170328.2300021130625279075.davem@davemloft.net> (raw)
In-Reply-To: <1559527086-7227-1-git-send-email-biao.huang@mediatek.com>
From: Biao Huang <biao.huang@mediatek.com>
Date: Mon, 3 Jun 2019 09:58:02 +0800
> Changes in v2:
> patch#1: there is no extra action in mediatek_dwmac_remove, remove it
>
> v1:
> This series mainly complete dwmac-mediatek driver:
> 1. add power on/off operations for dwmac-mediatek.
> 2. disable rx watchdog to reduce rx path reponding time.
> 3. change the default value of tx-frames from 25 to 1, so
> ptp4l will test pass by default.
>
> and also fix the issue that flow control won't be disabled any more
> once being enabled.
Series applied to net-next.
prev parent reply other threads:[~2019-06-06 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 1:58 [v2, PATCH 0/4] complete dwmac-mediatek driver and fix flow control issue Biao Huang
2019-06-03 1:58 ` [v2, PATCH 1/4] net: stmmac: dwmac-mediatek: enable Ethernet power domain Biao Huang
2019-06-03 1:58 ` [v2, PATCH 2/4] net: stmmac: dwmac-mediatek: disable rx watchdog Biao Huang
2019-06-03 1:58 ` [v2, PATCH 3/4] net: stmmac: modify default value of tx-frames Biao Huang
2019-06-03 11:40 ` Jose Abreu
2019-06-04 2:31 ` biao huang
2019-06-03 1:58 ` [v2, PATCH 4/4] net: stmmac: dwmac4: fix flow control issue Biao Huang
2019-06-06 0:03 ` 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=20190605.170328.2300021130625279075.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=biao.huang@mediatek.com \
--cc=boon.leong.ong@intel.com \
--cc=jianguo.zhang@mediatek.com \
--cc=joabreu@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=yt.shen@mediatek.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