netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Dave Hill <davidchill@hotmail.com>, netdev@vger.kernel.org
Subject: Re: PATCH: i40e Improve trusted VF MAC addresses logging when limit is reached
Date: Thu, 31 Jul 2025 16:48:29 +0200	[thread overview]
Message-ID: <62e55634-d36d-49e5-9d2f-d5cb00a0f099@linux.intel.com> (raw)
In-Reply-To: <CH3P221MB1462BC768A36BFE9E37E2CB6D327A@CH3P221MB1462.NAMP221.PROD.OUTLOOK.COM>

Hey David,

On 2025-07-31 4:06 PM, Dave Hill wrote:
> From: David Hill<dhill@redhat.com>

s/David Hill<dhill@redhat.com>/David Hill <dhill@redhat.com>/g

The patch formatting is really mangled and not possible to be applied 
with standard tooling.

It is advised to create patches using `git format-patch` and use `git 
send-email` tool for patch submissions, as it ensures proper formatting.

It is also advised to add the maintainers for a given piece of code to 
To: or Cc:, you can find them using ./scripts/get_maintainer.pl

Please take a look at 
https://docs.kernel.org/process/submitting-patches.html on information 
how to submit patches properly.

> When a VF reaches the limit introduced in this commit [1], the host 
> reports an error in the syslog but doesn't mention which VF reached its 
> limit and what the limit is actually is which makes troubleshooting of 
> networking issue a bit tedious.   This commit simply improves this error 
> reporting by adding which VF number has reached a limit and what that 
> limit is.
> 
> Signed-off-by: David Hill<dhill@redhat.com>
> 
> diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c b/ 
> drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c
> 
> index 9b8efdeafbcf..dc0e7a80d83a 100644
> --- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c
> +++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c
> @@ -2953,7 +2953,8 @@ static inline int i40e_check_vf_permission(struct 
> i40e_vf *vf,
> I40E_VC_MAX_MACVLAN_PER_TRUSTED_VF(pf->num_alloc_vfs,
> hw->num_ports)) {
>                          dev_err(&pf->pdev->dev,
> -                               "Cannot add more MAC addresses, trusted 
> VF exhausted it's resources\n");
> +                               "Cannot add more MAC addresses, trusted 
> VF %d uses %d out of %d MAC addresses\n", vf->vf_id, 
> i40e_count_filters(vsi) +
> +          mac2add_cnt, I40E_VC_MAX_MACVLAN_PER_TRUSTED_VF(pf- 
>  >num_alloc_vfs,num_ports)));
>                          return -EPERM;
>                  }
>          }
> 
> [1] commit cfb1d572c986a39fd288f48a6305d81e6f8d04a3
> Author: Karen Sornek <karen.sornek@intel.com>
> Date:   Thu Jun 17 09:19:26 2021 +0200

The above should be just below your signoff tag as follows:

Signed-off-by: David Hill <dhill@redhat.com>
---
[1] commit cfb1d572c986a39fd288f48a6305d81e6f8d04a3
Author: Karen Sornek <karen.sornek@intel.com>
Date:   Thu Jun 17 09:19:26 2021 +0200
---

Best regards,
Dawid

      reply	other threads:[~2025-07-31 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 14:06 PATCH: i40e Improve trusted VF MAC addresses logging when limit is reached Dave Hill
2025-07-31 14:48 ` Dawid Osuchowski [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=62e55634-d36d-49e5-9d2f-d5cb00a0f099@linux.intel.com \
    --to=dawid.osuchowski@linux.intel.com \
    --cc=davidchill@hotmail.com \
    --cc=netdev@vger.kernel.org \
    /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).