From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrzej Pietrasiewicz <andrzej.p@collabora.com>
Subject: Re: [PATCH V3 2/2] usb: gadget: u_ether: Don't warn in gether_setup_name_default()
Date: Thu, 19 Jan 2023 11:46:14 +0100 [thread overview]
Message-ID: <Y8kfdm9juBi58bnj@kroah.com> (raw)
In-Reply-To: <20230119102547.26698-2-jonathanh@nvidia.com>
On Thu, Jan 19, 2023 at 10:25:47AM +0000, Jon Hunter wrote:
> The function gether_setup_name_default() is called by various USB
> ethernet gadget drivers. Calling this function will select a random
> host and device MAC addresses. A properly working driver should be
> silent, so don't warn the user about default MAC addresses selection
> happening and convert the warnings into debug messages.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> V2 -> V3: Updated commit message.
> V1 -> V2: Changed print to debug instead of info.
>
> drivers/usb/gadget/function/u_ether.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/gadget/function/u_ether.c b/drivers/usb/gadget/function/u_ether.c
> index be8e7b448933..8feb40e38137 100644
> --- a/drivers/usb/gadget/function/u_ether.c
> +++ b/drivers/usb/gadget/function/u_ether.c
> @@ -845,13 +845,13 @@ struct net_device *gether_setup_name_default(const char *netname)
> snprintf(net->name, sizeof(net->name), "%s%%d", netname);
>
> eth_random_addr(dev->dev_mac);
> - pr_warn("using random self ethernet address %pM\n", dev->dev_mac);
> + pr_debug("using random self ethernet address %pM\n", dev->dev_mac);
>
> /* by default we always have a random MAC address */
> net->addr_assign_type = NET_ADDR_RANDOM;
>
> eth_random_addr(dev->host_mac);
> - pr_warn("using random host ethernet address %pM\n", dev->host_mac);
> + pr_debug("using random host ethernet address %pM\n", dev->host_mac);
In looking at this further, you are right, the structures are not
initialized properly yet.
So move these to a different function entirely, they should be in
gether_register_netdev() instead, after the device is registered with
the system.
thanks,
greg k-h
next prev parent reply other threads:[~2023-01-19 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 10:25 [PATCH V3 1/2] usb: gadget: u_ether: Improve print in gether_setup_name_default() Jon Hunter
2023-01-19 10:25 ` [PATCH V3 2/2] usb: gadget: u_ether: Don't warn " Jon Hunter
2023-01-19 10:46 ` Greg Kroah-Hartman [this message]
2023-01-19 13:38 ` Jon Hunter
2023-01-19 15:26 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2023-02-09 12:53 [PATCH V3 1/2] usb: gadget: u_ether: Convert prints to device prints Jon Hunter
2023-02-09 12:53 ` [PATCH V3 2/2] usb: gadget: u_ether: Don't warn in gether_setup_name_default() Jon Hunter
2023-02-13 13:16 ` Andrzej Pietrasiewicz
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=Y8kfdm9juBi58bnj@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrzej.p@collabora.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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