From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Andy Lutomirski <luto@amacapital.net>,
Bjorn Helgaas <helgaas@kernel.org>,
Linux API <linux-api@vger.kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Yijing Wang <wangyijing@huawei.com>
Subject: Re: [PATCH 0/2] Minor _OSC error handling improvements
Date: Tue, 15 Dec 2015 17:10:06 +0100 [thread overview]
Message-ID: <56703B5E.7040601@intel.com> (raw)
In-Reply-To: <CALCETrV53ZR6Yy0m4xWzNTZJaQWrk9X7cMf3__32H+fN1ya0=g@mail.gmail.com>
On 12/15/2015 4:15 AM, Andy Lutomirski wrote:
> [cc: linux-acpi and Rafael -- whoops]
>
> Rafael, do you want me to resend these?
Yes, please.
Thanks,
Rafael
> On Thu, Dec 3, 2015 at 9:29 AM, Bjorn Helgaas <helgaas@kernel.org> wrote:
>> On Thu, Nov 19, 2015 at 08:08:18AM -0800, Andy Lutomirski wrote:
>>> This doesn't fix any bugs, but it makes the debugging output a
>>> little more useful.
>>>
>>> Andy Lutomirski (2):
>>> acpi: Tidy up _OSC error spacing
>>> acpi: Show _OSC UUID when _OSC fails
>>>
>>> drivers/acpi/bus.c | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>> These both look fine to me. If you want it:
>>
>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>
>
prev parent reply other threads:[~2015-12-15 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 16:08 [PATCH 0/2] Minor _OSC error handling improvements Andy Lutomirski
2015-11-19 16:08 ` [PATCH 1/2] acpi: Tidy up _OSC error spacing Andy Lutomirski
2015-11-19 21:59 ` Andy Lutomirski
2015-11-20 1:01 ` Rafael J. Wysocki
2015-11-19 16:08 ` [PATCH 2/2] acpi: Show _OSC UUID when _OSC fails Andy Lutomirski
2015-11-19 22:00 ` Andy Lutomirski
2015-11-19 22:23 ` [PATCH 0/2] Minor _OSC error handling improvements Rafael J. Wysocki
2015-12-03 17:29 ` Bjorn Helgaas
2015-12-15 3:15 ` Andy Lutomirski
2015-12-15 16:10 ` 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=56703B5E.7040601@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=wangyijing@huawei.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;
as well as URLs for NNTP newsgroup(s).