[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231017082618.4558ad06@kernel.org>
Date: Tue, 17 Oct 2023 08:26:18 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Johannes Zink <j.zink@...gutronix.de>
Cc: Simon Horman <horms@...nel.org>, Alexandre Torgue
<alexandre.torgue@...s.st.com>, Jose Abreu <joabreu@...opsys.com>, "David
S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Maxime Coquelin <mcoquelin.stm32@...il.com>,
Richard Cochran <richardcochran@...il.com>, Kurt Kanzenbach
<kurt@...utronix.de>, patchwork-jzi@...gutronix.de, netdev@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel@...gutronix.de
Subject: Re: [PATCH net-next 2/5] net: stmmac: fix PPS capture input index
On Tue, 17 Oct 2023 11:12:53 +0200 Johannes Zink wrote:
> > If it is a bug fix then it should probably be targeted at 'net',
> > creating a dependency for the remainder of this series.
> >
> > On the other hand, if it is not a bug fix then perhaps it is best to
> > update the subject and drop the Fixes tag.
>
> I added the fixes-Tag in order to make code archeology easier, but as it may
> trigger picks to stable branches (which is not required imho), I have no
> objections to dropping it for a v2.
Would be good to clarify what impact on device operation the problem
has. How would end user notice the problem?
Does it mean snapshots were always or never enabled, previously?
Note that if you submit this fix for net today it will still make it
to -rc7 and net-next by tomorrow, so no major delay. We merge the trees
on Thursday, usually.
Powered by blists - more mailing lists