devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Loc Ho <lho@apm.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Doug Thompson <dougthompson@xmission.com>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Tomasz Nowicki <tomasz.nowicki@linaro.org>,
	Fu Wei <fu.wei@linaro.org>, Len Brown <lenb@kernel.org>,
	linux-edac <linux-edac@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-acpi@vger.kernel.org, "patches@apm.com" <patches@apm.com>,
	Tuan Phan <tphan@apm.com>
Subject: Re: [PATCH v4 2/2] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ
Date: Mon, 25 Jan 2016 22:54:34 +0100	[thread overview]
Message-ID: <20160125215433.GE4322@pd.tnic> (raw)
In-Reply-To: <CAPw-ZTmmK1RvKQVpNLtP=X+cxMVj3wYqq78x1eZ+2w5+5Q1dYg@mail.gmail.com>

On Mon, Jan 25, 2016 at 01:25:00PM -0800, Loc Ho wrote:
> Can this be pull into 4.5-rcX given that it was already ack'ed week back?

It is still Rafael's decision, as I've already stated.

Rafael?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

      reply	other threads:[~2016-01-25 21:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  0:17 [PATCH v4 0/2] acpi: apei: Bug fix to enable APEI support for ARMv8 Loc Ho
2016-01-21  0:17 ` [PATCH v4 1/2] acpi: Fix proper return code for function acpi_gsi_to_irq Loc Ho
2016-01-25 21:23   ` Loc Ho
     [not found]     ` <CAPw-ZTnm5F3Kt+_J6HoNCYbx8R7JVkME5yA9V-hAwRtr8ge9ZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-26  8:31       ` Marc Zyngier
2016-01-26 17:54         ` Loc Ho
2016-01-21  0:17 ` [PATCH v4 2/2] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ Loc Ho
     [not found]   ` <1453335459-3617-3-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
2016-01-25 21:25     ` Loc Ho
2016-01-25 21:54       ` Borislav Petkov [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=20160125215433.GE4322@pd.tnic \
    --to=bp@alien8.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dougthompson@xmission.com \
    --cc=fu.wei@linaro.org \
    --cc=lenb@kernel.org \
    --cc=lho@apm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=patches@apm.com \
    --cc=rjw@rjwysocki.net \
    --cc=tomasz.nowicki@linaro.org \
    --cc=tphan@apm.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).