From: Rob Herring <robh+dt@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH net-next v2 1/2] of: Export of_remove_property() to modules
Date: Fri, 4 Sep 2020 16:16:59 -0600 [thread overview]
Message-ID: <CAL_Jsq+EXvKkFoKgFA4gh7e-PPt0wLHHm3nR1RCqtubBTaj+dw@mail.gmail.com> (raw)
In-Reply-To: <20200904213730.3467899-2-f.fainelli@gmail.com>
On Fri, Sep 4, 2020 at 3:37 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>
> We will need to remove some OF properties in drivers/net/dsa/bcm_sf2.c
> with a subsequent commit. Export of_remove_property() to modules so we
> can keep bcm_sf2 modular and provide an empty stub for when CONFIG_OF is
> disabled to maintain the ability to compile test.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> drivers/of/base.c | 1 +
> include/linux/of.h | 5 +++++
> 2 files changed, 6 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-09-04 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 21:37 [PATCH net-next v2 0/2] net: dsa: bcm_sf2: Ensure MDIO diversion is used Florian Fainelli
2020-09-04 21:37 ` [PATCH net-next v2 1/2] of: Export of_remove_property() to modules Florian Fainelli
2020-09-04 22:16 ` Rob Herring [this message]
2020-09-04 21:37 ` [PATCH net-next v2 2/2] net: dsa: bcm_sf2: Ensure that MDIO diversion is used Florian Fainelli
2020-09-05 15:37 ` Andrew Lunn
2020-09-05 21:29 ` [PATCH net-next v2 0/2] net: dsa: bcm_sf2: Ensure " Jakub Kicinski
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=CAL_Jsq+EXvKkFoKgFA4gh7e-PPt0wLHHm3nR1RCqtubBTaj+dw@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
/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).