From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: <alok.a.tiwarilinux@gmail.com>, <aleksander.lobakin@intel.com>,
<anthony.l.nguyen@intel.com>, <andrew+netdev@lunn.ch>,
<kuba@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>,
<pabeni@redhat.com>, <horms@kernel.org>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next] iavf: clarify VLAN add/delete log messages and lower log level
Date: Mon, 3 Nov 2025 10:27:15 +0100 [thread overview]
Message-ID: <05a823d2-231d-47de-89fa-9648e47cbfa5@intel.com> (raw)
In-Reply-To: <20251103090344.452909-2-alok.a.tiwari@oracle.com>
On 11/3/25 10:03, Alok Tiwari wrote:
> The current dev_warn messages for too many VLAN changes are confusing
> and one place incorrectly reference "add" instead of "delete" VLANs
> due to copy-paste errors.
>
> - Use dev_info instead of dev_warn to lower the log level.
> - Rephrase the message to: "Too many VLAN [add|delete] changes requested,
> splitting into multiple messages to PF".
>
> Suggested-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
thank you!
just two minor nits, but the messages are good already, so:
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> ---
> https://lore.kernel.org/all/47f8c95c-bac4-471f-8e58-9155c6e58cb5@intel.com/
> ---
> drivers/net/ethernet/intel/iavf/iavf_virtchnl.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c b/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> index 34a422a4a29c..3593c0b45cf7 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> @@ -793,7 +793,8 @@ void iavf_add_vlans(struct iavf_adapter *adapter)
>
> len = virtchnl_struct_size(vvfl, vlan_id, count);
> if (len > IAVF_MAX_AQ_BUF_SIZE) {
> - dev_warn(&adapter->pdev->dev, "Too many add VLAN changes in one request\n");
> + dev_info(&adapter->pdev->dev, "Too many VLAN add changes requested,\n"
> + "splitting into multiple messages to PF\n");
perhaps it is too much bikeshedding for such a change, sorry, but
I would rather remove the newline in the middle
nit: another thing that I would consider is to differentiate the
messages (v1/v2 or A/B, or whatever) for different protocol versions
> while (len > IAVF_MAX_AQ_BUF_SIZE)
> len = virtchnl_struct_size(vvfl, vlan_id,
> --count);
> @@ -838,7 +839,8 @@ void iavf_add_vlans(struct iavf_adapter *adapter)
>
> len = virtchnl_struct_size(vvfl_v2, filters, count);
> if (len > IAVF_MAX_AQ_BUF_SIZE) {
> - dev_warn(&adapter->pdev->dev, "Too many add VLAN changes in one request\n");
> + dev_info(&adapter->pdev->dev, "Too many VLAN add changes requested,\n"
> + "splitting into multiple messages to PF\n");
> while (len > IAVF_MAX_AQ_BUF_SIZE)
> len = virtchnl_struct_size(vvfl_v2, filters,
> --count);
> @@ -941,7 +943,8 @@ void iavf_del_vlans(struct iavf_adapter *adapter)
>
> len = virtchnl_struct_size(vvfl, vlan_id, count);
> if (len > IAVF_MAX_AQ_BUF_SIZE) {
> - dev_warn(&adapter->pdev->dev, "Too many delete VLAN changes in one request\n");
> + dev_info(&adapter->pdev->dev, "Too many VLAN delete changes requested,\n"
> + "splitting into multiple messages to PF\n");
> while (len > IAVF_MAX_AQ_BUF_SIZE)
> len = virtchnl_struct_size(vvfl, vlan_id,
> --count);
> @@ -987,7 +990,8 @@ void iavf_del_vlans(struct iavf_adapter *adapter)
>
> len = virtchnl_struct_size(vvfl_v2, filters, count);
> if (len > IAVF_MAX_AQ_BUF_SIZE) {
> - dev_warn(&adapter->pdev->dev, "Too many add VLAN changes in one request\n");
> + dev_info(&adapter->pdev->dev, "Too many VLAN delete changes requested,\n"
> + "splitting into multiple messages to PF\n");
> while (len > IAVF_MAX_AQ_BUF_SIZE)
> len = virtchnl_struct_size(vvfl_v2, filters,
> --count);
next prev parent reply other threads:[~2025-11-03 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 9:03 [Intel-wired-lan] [PATCH net-next] iavf: clarify VLAN add/delete log messages and lower log level Alok Tiwari
2025-11-03 9:27 ` Przemek Kitszel [this message]
2025-11-03 10:17 ` [Intel-wired-lan] [External] : " ALOK TIWARI
2025-11-03 10:30 ` Loktionov, Aleksandr
2025-11-03 11:24 ` Przemek Kitszel
2025-11-03 10:27 ` [Intel-wired-lan] " Loktionov, Aleksandr
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=05a823d2-231d-47de-89fa-9648e47cbfa5@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=alok.a.tiwarilinux@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox