[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200222014038.180923-1-saravanak@google.com>
Date: Fri, 21 Feb 2020 17:40:33 -0800
From: Saravana Kannan <saravanak@...gle.com>
To: Jonathan Corbet <corbet@....net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Ard Biesheuvel <ardb@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Len Brown <lenb@...nel.org>
Cc: Saravana Kannan <saravanak@...gle.com>, kernel-team@...roid.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-efi@...r.kernel.org, devicetree@...r.kernel.org,
linux-acpi@...r.kernel.org
Subject: [PATCH v1 0/5] Add fw_devlink kernel commandline option
1/5 isn't really related to adding fw_devlink, but I'm just rolling it
into this series.
The rest of the series is about adding fw_devlink kernel commandline
that can be set to off|permissive|on|rpm which are in increasing order
of enforcement by device links.
2/5 is the most "interesting" part.
The hope is that once this series merges, we'll consider enabling
fw_devlink=permissive by default and at a later point in time ideally
"on".
Thanks,
Saravana
Saravana Kannan (5):
driver core: Reevaluate dev->links.need_for_probe as suppliers are
added
driver core: Add fw_devlink kernel commandline option
efi/arm: Start using fw_devlink_get_flags()
of: property: Start using fw_devlink_get_flags()
of: property: Delete of_devlink kernel commandline option
.../admin-guide/kernel-parameters.txt | 24 +++++++++----
drivers/base/core.c | 35 +++++++++++++++++--
drivers/firmware/efi/arm-init.c | 2 +-
drivers/of/property.c | 8 +----
include/linux/fwnode.h | 2 ++
5 files changed, 54 insertions(+), 17 deletions(-)
--
2.25.0.265.gbab2e86ba0-goog
Powered by blists - more mailing lists