From: Will Deacon <will.deacon@arm.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: catalin.marinas@arm.com, hanjun.guo@linaro.org,
dan.carpenter@oracle.com, okaya@codeaurora.org,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org
Subject: Re: [GIT PULL] ACPI IORT fixes for v4.10-rc8
Date: Mon, 6 Feb 2017 13:47:36 +0000 [thread overview]
Message-ID: <20170206134735.GJ19939@arm.com> (raw)
In-Reply-To: <20170206133856.GA14139@red-moon>
On Mon, Feb 06, 2017 at 01:38:56PM +0000, Lorenzo Pieralisi wrote:
> Hi Will, Catalin,
Hi Lorenzo,
> please consider pulling a couple of minor ACPI IORT fixes that were
> missed in the last few -rc* cycles but should be considered for
> merging as soon as possible, hopefully before v4.10 is released.
Both of these fixes look like they fix theoretical issues, as opposed to
fixing problems actually seen on existing platforms. Given that I don't
think there's going to be an -rc8, I'll take these for 4.11 instead.
Hopefully it'll be smooth sailing now that we've got the merge path
sorted out for arm64 acpi changes.
Let me know if that's a problem.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ACPI IORT fixes for v4.10-rc8
Date: Mon, 6 Feb 2017 13:47:36 +0000 [thread overview]
Message-ID: <20170206134735.GJ19939@arm.com> (raw)
In-Reply-To: <20170206133856.GA14139@red-moon>
On Mon, Feb 06, 2017 at 01:38:56PM +0000, Lorenzo Pieralisi wrote:
> Hi Will, Catalin,
Hi Lorenzo,
> please consider pulling a couple of minor ACPI IORT fixes that were
> missed in the last few -rc* cycles but should be considered for
> merging as soon as possible, hopefully before v4.10 is released.
Both of these fixes look like they fix theoretical issues, as opposed to
fixing problems actually seen on existing platforms. Given that I don't
think there's going to be an -rc8, I'll take these for 4.11 instead.
Hopefully it'll be smooth sailing now that we've got the merge path
sorted out for arm64 acpi changes.
Let me know if that's a problem.
Will
next prev parent reply other threads:[~2017-02-06 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 13:38 [GIT PULL] ACPI IORT fixes for v4.10-rc8 Lorenzo Pieralisi
2017-02-06 13:38 ` Lorenzo Pieralisi
2017-02-06 13:47 ` Will Deacon [this message]
2017-02-06 13:47 ` Will Deacon
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=20170206134735.GJ19939@arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=okaya@codeaurora.org \
/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.