From: Darren Hart <dvhart@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Andy Lutomirski" <luto@kernel.org>,
"Pali Rohár" <pali.rohar@gmail.com>,
platform-driver-x86@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: never 'select DMI' from a driver
Date: Mon, 29 Feb 2016 15:19:22 -0800 [thread overview]
Message-ID: <20160229231922.GL7499@dvhart-mobl5.amr.corp.intel.com> (raw)
In-Reply-To: <CALCETrXCvX_btgePvpW7=BU+u3qg+rkZEfM5pbREcF-VJ-2-ow@mail.gmail.com>
On Mon, Feb 29, 2016 at 03:13:54PM -0800, Andy Lutomirski wrote:
> On Mon, Feb 29, 2016 at 3:07 PM, Darren Hart <dvhart@infradead.org> wrote:
> > On Mon, Feb 29, 2016 at 07:46:58AM -0800, Andy Lutomirski wrote:
> >> On Mon, Feb 29, 2016 at 4:13 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> > CONFIG_DMI is a user-selectable Kconfig symbol that some drivers
> >> > depend on. As part of a recent patch, other drivers started
> >> > adding a 'select' for the same symbol, which now causes
> >> > a recursive dependency:
> >>
> >> Darren, it may make sense for you to fold the DELL_LAPTOP change in.
> >
> > Andy, I didn't quite follow you. Are you referring to this patch from Arnd, or
> > from the dell-smbios series from Michał?
> >
> > I'm planning on merging both (Michał's is pending a v5).
> >
>
> I meant to fold the "select DMI" -> "depends on DMI" for DELL_WMI into my patch.
Of course. Obvious in retrospect. :-)
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-02-29 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 12:13 Arnd Bergmann
2016-02-29 15:46 ` Andy Lutomirski
2016-02-29 23:07 ` Darren Hart
2016-02-29 23:13 ` Andy Lutomirski
2016-02-29 23:19 ` Darren Hart [this message]
2016-02-29 23:10 ` Darren Hart
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=20160229231922.GL7499@dvhart-mobl5.amr.corp.intel.com \
--to=dvhart@infradead.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@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 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®