From: David Miller <davem@davemloft.net>
To: biao.huang@mediatek.com
Cc: joabreu@synopsys.com, 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.comi,
boon.leong.ong@intel.com
Subject: Re: [v4, PATCH 0/3] fix some bugs in stmmac
Date: Sat, 25 May 2019 11:02:52 -0700 (PDT) [thread overview]
Message-ID: <20190525.110252.292904127953775877.davem@davemloft.net> (raw)
In-Reply-To: <1558679169-26752-1-git-send-email-biao.huang@mediatek.com>
From: Biao Huang <biao.huang@mediatek.com>
Date: Fri, 24 May 2019 14:26:06 +0800
> changes in v4:
> since MTL_OPERATION_MODE write back issue has be fixed in the latest driver,
> remove original patch#3
>
> changes in v3:
> add a Fixes:tag for each patch
>
> changes in v2:
> 1. update rx_tail_addr as Jose's comment
> 2. changes clk_csr condition as Alex's proposition
> 3. remove init lines in dwmac-mediatek, get clk_csr from dts instead.
>
> v1:
> This series fix some bugs in stmmac driver
> 3 patches are for common stmmac or dwmac4:
> 1. update rx tail pointer to fix rx dma hang issue.
> 2. change condition for mdc clock to fix csr_clk can't be zero issue.
> 3. write the modified value back to MTL_OPERATION_MODE.
> 1 patch is for dwmac-mediatek:
> modify csr_clk value to fix mdio read/write fail issue for dwmac-mediatek
Series applied, thanks.
prev parent reply other threads:[~2019-05-25 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 6:26 Biao Huang
2019-05-24 6:26 ` [v4, PATCH 1/3] net: stmmac: update rx tail pointer register to fix rx dma hang issue Biao Huang
2019-05-24 6:26 ` [v4, PATCH 2/3] net: stmmac: fix csr_clk can't be zero issue Biao Huang
2019-05-24 7:07 ` Alexandre Torgue
2019-05-24 6:26 ` [v4, PATCH 3/3] net: stmmac: dwmac-mediatek: modify csr_clk value to fix mdio read/write fail Biao Huang
2019-05-25 18:02 ` 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=20190525.110252.292904127953775877.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.torgue@st.com \
--cc=biao.huang@mediatek.com \
--cc=boon.leong.ong@intel.com \
--cc=jianguo.zhang@mediatek.comi \
--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
all inboxes | Powered by JetHome®