From: Pavel Machek <pavel@ucw.cz>
To: Nick Desaulniers <nick.desaulniers@gmail.com>
Cc: Joe Perches <joe@perches.com>,
rjw@rjwysocki.net, len.brown@intel.com, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: small formatting fixes
Date: Wed, 11 Jan 2017 21:03:45 +0100 [thread overview]
Message-ID: <20170111200345.GB29366@amd> (raw)
In-Reply-To: <20161223031942.jrgjt567m6bdeke3@lostoracle.net>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
On Thu 2016-12-22 19:19:43, Nick Desaulniers 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.
I don't maintain a tree for power management stuff. Rafael does.
There are tricks that can be done for easy but not trivial fixes.
Ouch and if you want code that needs clean ups / fixes... just let me
know :-).
> Or is there more approvals I have to get to get the patch merged?
No, you did well, just wait.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-01-11 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 7:25 [PATCH] ACPI: small formatting fixes Nick Desaulniers
2016-12-12 8:56 ` Pavel Machek
2016-12-12 17:56 ` Nick Desaulniers
2016-12-12 18:39 ` Joe Perches
2016-12-12 22:22 ` Pavel Machek
2016-12-12 22:32 ` Joe Perches
2016-12-12 23:08 ` Pavel Machek
2016-12-12 23:13 ` Joe Perches
2016-12-13 10:00 ` Bjørn Mork
2016-12-12 23:20 ` Nick Desaulniers
2016-12-12 23:22 ` Joe Perches
2016-12-13 19:00 ` Pavel Machek
2016-12-23 3:19 ` Nick Desaulniers
2016-12-23 12:10 ` Rafael J. Wysocki
2017-01-11 20:03 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-21 6:51 Nick Desaulniers
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=20170111200345.GB29366@amd \
--to=pavel@ucw.cz \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nick.desaulniers@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).