From: biao huang <biao.huang@mediatek.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jose Abreu <joabreu@synopsys.com>,
davem@davemloft.net, jianguo.zhang@mediatek.com,
Alexandre Torgue <alexandre.torgue@st.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
yt.shen@mediatek.com, linux-mediatek@lists.infradead.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [v2, PATCH 0/4] fix some bugs in stmmac
Date: Tue, 14 May 2019 11:38:51 +0800 [thread overview]
Message-ID: <1557805131.24897.41.camel@mhfsdcap03> (raw)
In-Reply-To: <20190514030016.GA19642@lunn.ch>
Hi Andrew,
Add a Fixes:tag in series v3, please review.
On Tue, 2019-05-14 at 05:00 +0200, Andrew Lunn wrote:
> On Tue, May 14, 2019 at 10:28:49AM +0800, Biao Huang wrote:
> > 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.
>
> Hi Biao
>
> Since these are fixes, could you provide a Fixes: tag for each one?
>
> Thanks
> Andrew
WARNING: multiple messages have this Message-ID (diff)
From: biao huang <biao.huang@mediatek.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com, yt.shen@mediatek.com,
Jose Abreu <joabreu@synopsys.com>,
linux-mediatek@lists.infradead.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
jianguo.zhang@mediatek.com,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
davem@davemloft.net, linux-arm-kernel@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [v2, PATCH 0/4] fix some bugs in stmmac
Date: Tue, 14 May 2019 11:38:51 +0800 [thread overview]
Message-ID: <1557805131.24897.41.camel@mhfsdcap03> (raw)
In-Reply-To: <20190514030016.GA19642@lunn.ch>
Hi Andrew,
Add a Fixes:tag in series v3, please review.
On Tue, 2019-05-14 at 05:00 +0200, Andrew Lunn wrote:
> On Tue, May 14, 2019 at 10:28:49AM +0800, Biao Huang wrote:
> > 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.
>
> Hi Biao
>
> Since these are fixes, could you provide a Fixes: tag for each one?
>
> Thanks
> Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: biao huang <biao.huang@mediatek.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jose Abreu <joabreu@synopsys.com>, <davem@davemloft.net>,
<jianguo.zhang@mediatek.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yt.shen@mediatek.com>, <linux-mediatek@lists.infradead.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [v2, PATCH 0/4] fix some bugs in stmmac
Date: Tue, 14 May 2019 11:38:51 +0800 [thread overview]
Message-ID: <1557805131.24897.41.camel@mhfsdcap03> (raw)
In-Reply-To: <20190514030016.GA19642@lunn.ch>
Hi Andrew,
Add a Fixes:tag in series v3, please review.
On Tue, 2019-05-14 at 05:00 +0200, Andrew Lunn wrote:
> On Tue, May 14, 2019 at 10:28:49AM +0800, Biao Huang wrote:
> > 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.
>
> Hi Biao
>
> Since these are fixes, could you provide a Fixes: tag for each one?
>
> Thanks
> Andrew
next prev parent reply other threads:[~2019-05-14 3:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 2:28 [v2, PATCH 0/4] fix some bugs in stmmac Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` [v2, PATCH 1/4] net: stmmac: update rx tail pointer register to fix rx dma hang issue Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` [v2, PATCH 2/4] net: stmmac: fix csr_clk can't be zero issue Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` [v2, PATCH 3/4] net: stmmac: write the modified value back to MTL_OPERATION_MODE Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` [v2, PATCH 4/4] net: stmmac: dwmac-mediatek: modify csr_clk value to fix mdio read/write fail Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 2:28 ` Biao Huang
2019-05-14 3:00 ` [v2, PATCH 0/4] fix some bugs in stmmac Andrew Lunn
2019-05-14 3:00 ` Andrew Lunn
2019-05-14 3:38 ` biao huang [this message]
2019-05-14 3:38 ` biao huang
2019-05-14 3:38 ` biao huang
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=1557805131.24897.41.camel@mhfsdcap03 \
--to=biao.huang@mediatek.com \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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 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.