[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240627123932.4c7e964a@kernel.org>
Date: Thu, 27 Jun 2024 12:39:32 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Heng Qi <hengqi@...ux.alibaba.com>
Cc: netdev@...r.kernel.org, Eric Dumazet <edumazet@...gle.com>, "David S.
Miller" <davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>, Vladimir
Oltean <vladimir.oltean@....com>, Jiri Pirko <jiri@...nulli.us>, Simon
Horman <horms@...nel.org>,
syzbot+e77327e34cdc8c36b7d3@...kaller.appspotmail.com
Subject: Re: [PATCH net] net: ethtool: Fix the panic caused by dev being
null when dumping coalesce
On Wed, 26 Jun 2024 23:34:21 +0800 Heng Qi wrote:
> The problematic commit targeted by this fix may still be in the next branch.
Could you resend with [PATCH net-next] in the subject instead, in this
case? Our build bot trusts the designation in the subject so since this
was submitted as "PATCH net" and patch doesn't apply to net - it
rejected the patch.
--
pw-bot: cr
Powered by blists - more mailing lists