From: Randy Dunlap <rdunlap@infradead.org>
To: Divya Bharathi <divya27392@gmail.com>, dvhart@infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Divya Bharathi <divya.bharathi@dell.com>,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
mark gross <mgross@linux.intel.com>,
Mario Limonciello <mario.limonciello@dell.com>,
Prasanth KSR <prasanth.ksr@dell.com>
Subject: Re: [PATCH v4] Introduce support for Systems Management Driver over WMI for Dell Systems
Date: Wed, 23 Sep 2020 10:11:32 -0700 [thread overview]
Message-ID: <9b015765-de6f-3b2a-8804-e23864eb8806@infradead.org> (raw)
In-Reply-To: <20200923113015.110980-1-divya.bharathi@dell.com>
Hi,
On 9/23/20 4:30 AM, Divya Bharathi wrote:
> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> index 40219bba6801..4fd7a3f0a904 100644
> --- a/drivers/platform/x86/Kconfig
> +++ b/drivers/platform/x86/Kconfig
> @@ -430,6 +430,18 @@ config DELL_WMI
> To compile this driver as a module, choose M here: the module will
> be called dell-wmi.
>
> +config DELL_WMI_SYSMAN
> + tristate "Dell WMI Systems management WMI driver"
Could you drop one of those "WMI" strings or are both of them needed?
> + depends on ACPI_WMI
> + depends on DMI
> + select NLS
> + help
> + This driver allows changing BIOS settings on many Dell machines from
> + 2018 and newer without the use of any additional software.
> +
> + To compile this driver as a module, choose M here: the module will
> + be called dell-wmi-sysman.
thanks.
--
~Randy
next prev parent reply other threads:[~2020-09-23 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:30 Divya Bharathi
2020-09-23 17:11 ` Randy Dunlap [this message]
2020-09-23 18:39 ` Limonciello, Mario
2020-09-23 18:41 ` Randy Dunlap
2020-09-25 13:26 ` Hans de Goede
2020-09-25 15:32 ` Limonciello, Mario
2020-09-25 18:16 ` Hans de Goede
2020-09-25 18:37 ` Limonciello, Mario
2020-09-25 19:40 ` Hans de Goede
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=9b015765-de6f-3b2a-8804-e23864eb8806@infradead.org \
--to=rdunlap@infradead.org \
--cc=andy.shevchenko@gmail.com \
--cc=divya.bharathi@dell.com \
--cc=divya27392@gmail.com \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prasanth.ksr@dell.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®