From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Schmauss, Erik" <erik.schmauss@intel.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v2 00/12] ACPICA version 20191018v2
Date: Tue, 29 Oct 2019 11:56:20 +0200 [thread overview]
Message-ID: <20191029095620.GS32742@smile.fi.intel.com> (raw)
In-Reply-To: <2812725.QSNE5ueIqz@kreacher>
On Mon, Oct 28, 2019 at 10:16:58PM +0100, Rafael J. Wysocki wrote:
> On Monday, October 28, 2019 6:49:10 PM CET Schmauss, Erik wrote:
> > > -----Original Message-----
> > > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > Sent: Monday, October 28, 2019 8:59 AM
> > > To: Schmauss, Erik <erik.schmauss@intel.com>
> > > Cc: Rafael J . Wysocki <rafael@kernel.org>; linux-acpi@vger.kernel.org
> > > Subject: Re: [PATCH v2 00/12] ACPICA version 20191018v2
> > > On Fri, Oct 25, 2019 at 02:36:48PM -0700, Erik Schmauss wrote:
> > I agree. It makes sense to use the interface in the same commit for linux
>
> OK, done.
>
> Please check the result in the bleeding-edge branch of my tree.
I have checked the contents of the patch 5 and it's fine, thanks!
(Since for the rest I have no changes, I think they are fine as well)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-10-29 9:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 21:36 [PATCH v2 00/12] ACPICA version 20191018v2 Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 01/12] ACPICA: Results from Clang changes/fixes From Clang V5.0.1. Mostly "set but never read" warnings Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 02/12] ACPICA: Win OSL: Replace get_tick_count with get_tick_count64 Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 03/12] ACPICA: More Clang changes - V8.0.1 Fixed all "dead assignment" warnings Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 04/12] ACPICA: Add new external interface, acpi_unload_table Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 05/12] ACPICA: make acpi_load_table() return table index Erik Schmauss
2019-10-26 14:44 ` Andy Shevchenko
2019-10-28 17:15 ` Schmauss, Erik
2019-10-28 15:52 ` Andy Shevchenko
2019-10-25 21:36 ` [PATCH v2 06/12] ACPICA: utilities: add flag to only display data when dumping buffers Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 07/12] ACPICA: debugger: add command to dump all fields of a particular subtype Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 08/12] ACPICA: debugger: surround field unit output with braces '{' Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 09/12] ACPICA: debugger: add field unit support for acpi_db_get_next_token Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 10/12] ACPICA: acpiexec: initialize all simple types and field units from user input Erik Schmauss
2019-10-25 21:36 ` [PATCH v2 11/12] ACPICA: debugger: remove leading whitespaces when converting a string to a buffer Erik Schmauss
2019-10-25 21:37 ` [PATCH v2 12/12] ACPICA: Update version to 20191018 Erik Schmauss
2019-10-26 14:42 ` [PATCH v2 00/12] ACPICA version 20191018v2 Andy Shevchenko
2019-10-28 15:58 ` Andy Shevchenko
2019-10-28 17:49 ` Schmauss, Erik
2019-10-28 21:16 ` Rafael J. Wysocki
2019-10-29 9:56 ` Andy Shevchenko [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=20191029095620.GS32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=erik.schmauss@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.