From: Andrew Lunn <andrew@lunn.ch>
To: Michael Walle <michael@walle.cc>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/2] of: net: fix of_get_mac_addr_nvmem() for PCI and DSA nodes
Date: Tue, 6 Apr 2021 14:40:34 +0200 [thread overview]
Message-ID: <YGxWwhUYutuN8QJT@lunn.ch> (raw)
In-Reply-To: <1b7e58ba2ec798ddda77a9a3ab72338c@walle.cc>
> But then pdev will be NULL and nvmem_get_mac_address() won't be called
> at all, no?
Forget it, it can be added later if there is a real use case.
Andrew
next prev parent reply other threads:[~2021-04-06 12:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 16:46 [PATCH 0/2] of: net: support non-platform devices in of_get_mac_address() Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 16:46 ` [PATCH 1/2] of: net: pass the dst buffer to of_get_mac_address() Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 19:19 ` kernel test robot
2021-04-05 19:19 ` kernel test robot
2021-04-05 19:19 ` kernel test robot
2021-04-05 19:19 ` kernel test robot
2021-04-05 19:19 ` kernel test robot
2021-04-05 21:25 ` Andrew Lunn
2021-04-05 21:25 ` Andrew Lunn
2021-04-05 21:25 ` Andrew Lunn
2021-04-05 21:25 ` Andrew Lunn
2021-04-05 21:25 ` Andrew Lunn
2021-04-05 21:25 ` Andrew Lunn
2021-04-05 16:46 ` [PATCH 2/2] of: net: fix of_get_mac_addr_nvmem() for PCI and DSA nodes Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 16:46 ` Michael Walle
2021-04-05 21:34 ` Andrew Lunn
2021-04-05 21:46 ` Michael Walle
2021-04-05 22:13 ` Andrew Lunn
2021-04-06 8:59 ` Michael Walle
2021-04-06 12:40 ` Andrew Lunn [this message]
2021-04-07 1:13 ` Rob Herring
2021-04-07 1:13 ` Rob Herring
2021-04-07 1:13 ` Rob Herring
2021-04-07 1:13 ` Rob Herring
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=YGxWwhUYutuN8QJT@lunn.ch \
--to=andrew@lunn.ch \
--cc=michael@walle.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.