From: Randy Dunlap <randy.dunlap@oracle.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: "Peter Hüwe" <PeterHuewe@gmx.de>,
"Matthew Garrett" <mjg@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Sedat Dilek" <sedat.dilek@googlemail.com>
Subject: Re: [PATCH] platform/x86: Fix recursive Kconfig dependency
Date: Wed, 15 Dec 2010 12:51:04 -0800 [thread overview]
Message-ID: <4D092A38.7020407@oracle.com> (raw)
In-Reply-To: <AANLkTin+vOvpK4geMKdcx4wiOSc_EdPNwXJAcFTaCcnf@mail.gmail.com>
On 12/15/10 12:49, Corentin Chary wrote:
> On Wed, Dec 15, 2010 at 9:35 PM, Peter Hüwe <PeterHuewe@gmx.de> wrote:
>> Am Donnerstag 09 Dezember 2010, 00:29:30 schrieb Peter Huewe:
>>> This patch removes a recursive dependency which causes a build failure
>>> [1-3] by changing the ASUS_WMI from select ACPI_WMI to depend on
>>> ACPI_WMI as most other _WMI config options do.
>>>
>>> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
>
> Hi, another patch was posted before:
>
> http://article.gmane.org/gmane.linux.drivers.platform.x86.devel/970/match=acpi_wmi
>
> Randy Dunlap sort of Acked it ("Ah, that's what Sedat's patch does. Good.")
> http://article.gmane.org/gmane.linux.drivers.platform.x86.devel/971/match=acpi_wmi
For Matthew:
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
>
> Your patch seems to miss TC1100_WMI section.
Yes, it would be better to do both (all) of them the same way.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-12-15 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 23:29 [PATCH] platform/x86: Fix recursive Kconfig dependency Peter Huewe
2010-12-15 20:35 ` Peter Hüwe
2010-12-15 20:49 ` Corentin Chary
2010-12-15 20:51 ` Randy Dunlap [this message]
2010-12-15 21:14 ` Peter Hüwe
2010-12-17 11:30 ` Sedat Dilek
2010-12-19 19:00 ` Peter Hüwe
2010-12-20 14:46 ` Sedat Dilek
2010-12-20 17:09 ` Peter Hüwe
2010-12-20 17:24 ` Randy Dunlap
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=4D092A38.7020407@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=PeterHuewe@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sedat.dilek@googlemail.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