[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <532B8A4B.9000808@linaro.org>
Date: Fri, 21 Mar 2014 08:39:39 +0800
From: Hanjun Guo <hanjun.guo@...aro.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
CC: ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux PM list <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux PCI <linux-pci@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: ACPI and PM material for v3.15-rc1 (current queue)
Hi Rafael,
On 2014年03月21日 08:23, Rafael J. Wysocki wrote:
> Hi All,
>
> My queue for the first pull request during the upcoming 3.15 merge window
> contains the material below. Following the rule that everything I send
> pull requests for should spend at least one day in linux-next, I'm not
> going to add any more new commits to it at this point.
>
> Most likely, there will be more ACPI+PM pull request during the 3.15 cycle,
> so if I missed something, it still may be possible to get that into that
> kernel, but there has to be a good reason for it.
>
> Kind regards,
> Rafael
>
>
> ---------------
>
> Hanjun Guo (2):
> ACPI / tables: Replace printk with pr_*
> ACPI: Remove duplicate definitions of PREFIX
It seems that you missed some of my patches:
ACPI: Move BAD_MADT_ENTRY() to linux/acpi.h
ACPI / idle: Make idle_boot_override depend on x86 and ia64
ACPI / trivial: Fix the return value type of acpi_processor_eval_pdc()
ACPI / processor: Replace hard-coded "ACPI0007" with
ACPI_PROCESSOR_DEVICE_HID
I think those 4 patches can be merged in 3.15 and you already accepted them.
and this patch still need more acks and then you will accept it:
ACPI / processor_core: Rework _PDC related stuff to make it more
arch-independent
and this patch was reverted from your tree suggested by Catalin and Sudeep,
ACPI / processor: Introduce map_gic_id() to get apic id from MADT or
_MAT method
Sorry for the confusion if I missed something.
Thanks
Hanjun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists