netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Lixue Liang <lianglixuehao@126.com>
Cc: anthony.l.nguyen@intel.com, intel-wired-lan@lists.osuosl.org,
	jesse.brandeburg@intel.com, kuba@kernel.org,
	lianglixue@greatwall.com.cn, netdev@vger.kernel.org
Subject: Re: [PATCH v3 3/3] igb_main: Assign random MAC address instead of fail in case of invalid one
Date: Mon, 30 May 2022 09:47:17 +0200	[thread overview]
Message-ID: <ade6c030-b1c5-e359-7321-fa21310a10f3@molgen.mpg.de> (raw)
In-Reply-To: <20220530031941.44006-1-lianglixuehao@126.com>

Dear Lixue,

Am 30.05.22 um 05:19 schrieb Lixue Liang:
> From: Lixue Liang <lianglixue@greatwall.com.cn>
> 
> In some cases, when the user uses igb_set_eeprom to modify the MAC
> address to be invalid, the igb driver will fail to load. If there is no
> network card device, the user must modify it to a valid MAC address by
> other means.
> 
> Since the MAC address can be modified, then add a random valid MAC address
> to replace the invalid MAC address in the driver can be workable, it can
> continue to finish the loading, and output the relevant log reminder.
> 
> Signed-off-by: Lixue Liang <lianglixue@greatwall.com.cn>
> ---
>   drivers/net/ethernet/intel/igb/igb_main.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c b/drivers/net/ethernet/intel/igb/igb_main.c
> index 746233befade..40f43534a3af 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -3362,7 +3362,7 @@ static int igb_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>   		eth_hw_addr_random(netdev);
>   		ether_addr_copy(hw->mac.addr, netdev->dev_addr);
>   		dev_err(&pdev->dev,
> -			"Invalid MAC Address, already assigned random MAC Address\n");
> +			"Invalid MAC address, already assigned random MAC address\n");
>   	}
>   
>   	igb_set_default_mac_filter(adapter);

The diff does not do what is described in the commit message. I also 
just noticed, that it was spelled “MAC Address” before, so it would be 
fine for me if you send in this commit separately (but with the correct 
commit message).


Kind regards,

Paul

  reply	other threads:[~2022-05-30  7:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  9:39 [PATCH v2 2/2] igb_main: Assign random MAC address instead of fail in case of invalid one lixue liang
2022-05-12 13:55 ` [Intel-wired-lan] " Paul Menzel
2022-05-13  3:25   ` 梁礼学
2022-05-13  3:47   ` 梁礼学
2022-05-13  5:00   ` lixue liang
2022-05-30  3:19   ` [PATCH v3 3/3] " Lixue Liang
2022-05-30  7:47     ` Paul Menzel [this message]
2022-05-30 10:58   ` [PATCH v3] " Lixue Liang
2022-05-31 20:36     ` Tony Nguyen
2022-05-13 21:25 [PATCH v3 3/3] " lixue liang
2022-05-17  2:25 lixue liang

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=ade6c030-b1c5-e359-7321-fa21310a10f3@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=lianglixue@greatwall.com.cn \
    --cc=lianglixuehao@126.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).