[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hPYkF0CkhN7aWmvmhVcnq5SbwjQFgbJwK_9gbW-Ci2hw@mail.gmail.com>
Date: Fri, 23 Dec 2016 13:10:56 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Nick Desaulniers <nick.desaulniers@...il.com>
Cc: Pavel Machek <pavel@....cz>, Joe Perches <joe@...ches.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <len.brown@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"the arch/x86 maintainers" <x86@...nel.org>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ACPI: small formatting fixes
On Fri, Dec 23, 2016 at 4:19 AM, Nick Desaulniers
<nick.desaulniers@...il.com> wrote:
> On Tue, Dec 13, 2016 at 08:00:01PM +0100, Pavel Machek wrote:
>> Actually.. the ACPI cleanup is fine. You did well :-).
>> Pavel
>
> Cool, so (forgive the naive question) what happens next? Maybe I'm too
> used to the immediate gratification from Github of having a Pull Request
> get merged. Is this something that you have cherry picked into your
> tree, then will ask Linus to pull from at the end of the merge window?
>
> Do you have a tree that public that I am able to view? On
> git.kernel.org, there seems to be one tree with your name on it but it
> seems to be related to the (Nokia?) n900 and it's latest updated branch
> is from 9 weeks ago.
>
> Or is there more approvals I have to get to get the patch merged?
Somebody has to decide that your patch is worth merging and take it.
For ACPI-related patches that usually is me, but I haven't looked at
it yet. I'll do that next week and let you know if all goes well.
Thanks,
Rafael
Powered by blists - more mailing lists