From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 13:38:15 +0000 [thread overview]
Message-ID: <e0e3fb48-1c7a-f012-5308-4897bab01dfc@nvidia.com> (raw)
In-Reply-To: <Y8kfdm9juBi58bnj@kroah.com>
On 19/01/2023 10:46, Greg Kroah-Hartman wrote:
...
> 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.
I wonder if this is even necessary. Looking at gether_register_netdev()
it already has ...
status = register_netdev(net);
if (status < 0) {
dev_dbg(&g->dev, "register_netdev failed, %d\n", status);
return status;
} else {
INFO(dev, "HOST MAC %pM\n", dev->host_mac);
INFO(dev, "MAC %pM\n", dev->dev_mac);
...
}
Any objection to just removing completely from
gether_setup_name_default()? If we move to
gether_register_netdev() then I believe we also have to deal with
gether_register_netdev().
Jon
--
nvpublic
next prev parent reply other threads:[~2023-01-19 13:42 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 " 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
2023-01-19 13:38 ` Jon Hunter [this message]
2023-01-19 15:26 ` Greg Kroah-Hartman
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=e0e3fb48-1c7a-f012-5308-4897bab01dfc@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=andrzej.p@collabora.com \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®