From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: sedat.dilek@gmail.com, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Corentin Chary <corentin.chary@gmail.com>,
Matthew Garrett <mjg@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] platform/x86: Fix recursive Kconfig dependency
Date: Sun, 19 Dec 2010 20:00:14 +0100 [thread overview]
Message-ID: <201012192000.14969.PeterHuewe@gmx.de> (raw)
In-Reply-To: <AANLkTikPVqaZE8KBOCKWuwkqRpn3mHKQn+V3bUU5cW7=@mail.gmail.com>
Am Freitag 17 Dezember 2010, 12:30:15 schrieb Sedat Dilek:
> On Wed, Dec 15, 2010 at 10:14 PM, Peter Hüwe <PeterHuewe@gmx.de> wrote:
> > Am Mittwoch 15 Dezember 2010, 21:51:04 schrieb Randy Dunlap:
> >> > Hi, another patch was posted before:
> >> >
> >> > http://article.gmane.org/gmane.linux.drivers.platform.x86.devel/970/ma
> >> > tch =acpi_wmi
> >> >Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
> >
> > Yeah, you're right - but as Sedat's patch is perfect (and fixes both) -
> > so for Sedats's patch:
> > Acked-by: Peter Huewe <peterhuewe@gmx.de>
> >
> > Thanks,
> > Peter
>
> [ CC John Linville ]
>
> It's a bit disappointing to see my fix is still not in
> platform-drivers-x86/linux-next [1] (even it's only fixing "warnings",
> 9 days past).
> linux-next tree is for me a very high dynamic SCM tree, I am doing
> mostly daily builds, at weekend I am testing/pulling other trees
> before they go into Monday's linux-next.
> As far as I have fun with "my process"... I will continue.
Added Stephen Rothwell on CC, maybe he can apply it directly to linux-next ;)
Peter
next prev parent reply other threads:[~2010-12-19 19:00 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
2010-12-15 21:14 ` Peter Hüwe
2010-12-17 11:30 ` Sedat Dilek
2010-12-19 19:00 ` Peter Hüwe [this message]
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=201012192000.14969.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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