Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: [PATCH v5 1/4] ACPI / scan: Initialize status to ACPI_STA_DEFAULT | From | Hans de Goede <> | Date | Thu, 9 Aug 2018 13:36:50 +0200 |
| |
Hi,
On 09-08-18 11:59, Rafael J. Wysocki wrote: > On Thu, Aug 9, 2018 at 11:58 AM, Hans de Goede <hdegoede@redhat.com> wrote: >> Hi, >> >> On 09-08-18 11:51, Andy Shevchenko wrote: >>> >>> On Thu, Aug 9, 2018 at 12:39 PM, Hans de Goede <hdegoede@redhat.com> >>> wrote: >>>> >>>> On 09-08-18 11:35, Rafael J. Wysocki wrote: >>>>> >>>>> On Thu, Aug 9, 2018 at 11:15 AM, Hans de Goede <hdegoede@redhat.com> >>>>> wrote: >>> >>> >>>>> I've applied the v4 of this patch and I don't think there are any >>>>> changes from it here. >>>> >>>> >>>> >>>> Correct, there were only changes to the 4th patch in the series. >>>> >>>>> As for the rest of the series I'll wait from comments from Wolfram and >>>>> the other reviewers. >>>> >>>> >>>> >>>> Ok, note if you've taken patch 1 you may also want to take patch 3 which >>>> is an ACPI code cleanup made possible by patch 1 and otherwise is >>>> unrelated. >>> >>> >>> I'm under impression Rafael is going to take entire series (at least >>> for patch 4 I'm expecting to give an Ack). >> >> >> As I mentioned in the coverletter, my idea was to have Rafael take >> patches 1-3 and then merge the 4th patch through the platform/x86 >> tree. There are only runtime dependencies between the 2 parts and >> merging them independently should not cause any issues. > > I can apply the 4th one too if it is ACKed by everyone with a vested interest.
That works for me, note I'm about to send out a v6 (with only changes to the 4th patch), so hold of a bit with merging this please.
Andy does your ack for the 4th patch mean you're ok with Rafael merging this?
Regards,
Hans
| ![\](/images/icornerr.gif) |