linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: ahs3@redhat.com
Cc: Pavel Machek <pavel@ucw.cz>,
	x86@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
	trivial@kernel.org
Subject: Re: [PATCH 0/2] minor x86 PM source file cleanup
Date: Wed, 14 Sep 2016 03:04:38 +0200	[thread overview]
Message-ID: <3231912.dxysaRV8Do@vostro.rjw.lan> (raw)
In-Reply-To: <8bbb6de2-19fa-1ad8-9946-d2ef17091806@redhat.com>

On Saturday, August 20, 2016 06:15:10 PM Al Stone wrote:
> On 08/20/2016 04:55 AM, Pavel Machek wrote:
> > On Fri 2016-08-19 17:24:00, Al Stone wrote:
> >> Really minor patches: one to cleanup whitespace, the second just makes
> >> the code a wee bit more maintainable by correcting some variable names
> >> without changing functionality.
> > 
> > Acked-by: Pavel Machek <pavel@ucw.cz>
> > 
> > (for both)
> > 
> >> Al Stone (2):
> >>   x86: ACPI: remove extraneous white space after semicolon
> >>   x86: ACPI: make variable names clearer in
> >>     acpi_parse_madt_lapic_entries()
> >>
> >>  arch/x86/kernel/acpi/boot.c | 6 +++---
> >>  1 file changed, 3 insertions(+), 3 deletions(-)
> >>
> > 
> 
> Thanks, Pavel.

Both applied.

Thanks,
Rafael

      reply	other threads:[~2016-09-14  0:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 23:24 [PATCH 0/2] minor x86 PM source file cleanup Al Stone
2016-08-19 23:24 ` [PATCH 1/2] x86: ACPI: remove extraneous white space after semicolon Al Stone
2016-08-19 23:24 ` [PATCH 2/2] x86: ACPI: make variable names clearer in acpi_parse_madt_lapic_entries() Al Stone
2016-08-20 10:55 ` [PATCH 0/2] minor x86 PM source file cleanup Pavel Machek
2016-08-21  0:15   ` Al Stone
2016-09-14  1:04     ` Rafael J. Wysocki [this message]

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=3231912.dxysaRV8Do@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=ahs3@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=trivial@kernel.org \
    --cc=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;
as well as URLs for NNTP newsgroup(s).