From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: saravanak@google.com, linux-kernel@vger.kernel.org
Cc: frowand.list@gmail.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: [PATCH v2 0/2] of: property: fw_devlink misc fixes
Date: Fri, 17 Apr 2020 18:54:40 +0200 [thread overview]
Message-ID: <20200417165442.1856-1-nsaenzjulienne@suse.de> (raw)
As I'm interested in using this feature to fine-tune Raspberry Pi 4's
device probe dependencies, I tried to get the board to boot with
fw_devlink=on. As of today's linux-next the board won't boot with that
option. I tried to address the underlying issues.
---
Changes since v1:
- Address Saravana's comments
- Drop patch #3 & #4
Nicolas Saenz Julienne (2):
of: property: Fix create device links for all child-supplier
dependencies
of: property: Do not link to disabled devices
drivers/of/property.c | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
--
2.26.0
next reply other threads:[~2020-04-17 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 16:54 Nicolas Saenz Julienne [this message]
2020-04-17 16:54 ` [PATCH v2 1/2] of: property: Fix create device links for all child-supplier dependencies Nicolas Saenz Julienne
2020-04-17 20:56 ` Saravana Kannan
2020-04-17 16:54 ` [PATCH v2 2/2] of: property: Do not link to disabled devices Nicolas Saenz Julienne
2020-04-17 21:08 ` Saravana Kannan
2020-04-18 9:20 ` Nicolas Saenz Julienne
2020-04-17 18:06 ` [PATCH v2 0/2] of: property: fw_devlink misc fixes Nicolas Saenz Julienne
2020-04-17 20:55 ` Saravana Kannan
2020-04-20 11:29 ` Nicolas Saenz Julienne
2020-04-20 22:37 ` Saravana Kannan
2020-04-21 8:54 ` Nicolas Saenz Julienne
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=20200417165442.1856-1-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.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
all inboxes | Powered by JetHome®