public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <hanjun.guo@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: ACPI and PM material for v3.15-rc1 (current queue)
Date: Fri, 21 Mar 2014 08:39:39 +0800	[thread overview]
Message-ID: <532B8A4B.9000808@linaro.org> (raw)
In-Reply-To: <2611540.GrpzWjVQ7v@vostro.rjw.lan>

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

  reply	other threads:[~2014-03-21  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  0:23 ACPI and PM material for v3.15-rc1 (current queue) Rafael J. Wysocki
2014-03-21  0:39 ` Hanjun Guo [this message]
2014-03-21 16:40   ` Rafael J. Wysocki
2014-03-22  2:08     ` Hanjun Guo

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=532B8A4B.9000808@linaro.org \
    --to=hanjun.guo@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox