From: patchwork-bot+netdevbpf@kernel.org
To: Jiasheng Jiang <jiashengjiangcool@gmail.com>
Cc: przemyslaw.kitszel@intel.com, arkadiusz.kubalewski@intel.com,
davem@davemloft.net, jan.glaza@intel.com, jiri@resnulli.us,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
stable@vger.kernel.org, vadim.fedorenko@linux.dev
Subject: Re: [PATCH v4 net-next] dpll: Add an assertion to check freq_supported_num
Date: Wed, 05 Mar 2025 01:20:44 +0000 [thread overview]
Message-ID: <174113764499.356990.5931495827775849774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250228150210.34404-1-jiashengjiangcool@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Feb 2025 15:02:10 +0000 you wrote:
> Since the driver is broken in the case that src->freq_supported is not
> NULL but src->freq_supported_num is 0, add an assertion for it.
>
> Signed-off-by: Jiasheng Jiang <jiashengjiangcool@gmail.com>
> ---
> Changelog:
>
> [...]
Here is the summary with links:
- [v4,net-next] dpll: Add an assertion to check freq_supported_num
https://git.kernel.org/netdev/net-next/c/39e912a959c1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-05 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 15:02 [PATCH v4 net-next] dpll: Add an assertion to check freq_supported_num Jiasheng Jiang
2025-02-28 15:22 ` Jiri Pirko
2025-02-28 16:37 ` Vadim Fedorenko
2025-02-28 16:42 ` Kubalewski, Arkadiusz
2025-03-05 1:20 ` patchwork-bot+netdevbpf [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=174113764499.356990.5931495827775849774.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=jan.glaza@intel.com \
--cc=jiashengjiangcool@gmail.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).