[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da65b8e2-bbc9-4d9b-9d78-4a32775c465b@socionext.com>
Date: Thu, 16 Jan 2025 19:02:03 +0900
From: Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
To: Furong Xu <0x1207@...il.com>
Cc: Alexandre Torgue <alexandre.torgue@...s.st.com>,
Jose Abreu <joabreu@...opsys.com>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net 1/2] net: stmmac: Limit FIFO size by hardware feature
value
Hi Furong,
Thank you for your comment.
On 2025/01/16 12:04, Furong Xu wrote:
> On Thu, 16 Jan 2025 11:08:52 +0900, Kunihiko Hayashi
> <hayashi.kunihiko@...ionext.com> wrote:
>
>> Tx/Rx FIFO size is specified by the parameter "{tx,rx}-fifo-depth" from
>> the platform layer.
>>
>> However, these values are constrained by upper limits determined by the
>> capabilities of each hardware feature. There is a risk that the upper
>> bits will be truncated due to the calculation, so it's appropriate to
>> limit them to the upper limit values.
>>
>
> Patch is fine, but the Fixes: tag is required here.
I see. I'll find original commit and send the patch with Fixes:
tag next.
> And if you like to group this patch and the another patch into one series,
> it is better to add a cover letter.
Yes, I omitted to add a cover letter.
However, this patch has no dependency on the other one and
needs some consideration, so I'll send it separately.
Thank you,
---
Best Regards
Kunihiko Hayashi
Powered by blists - more mailing lists