From: Catalin Marinas <catalin.marinas@arm.com>
To: Al Stone <ahs3@redhat.com>
Cc: Will Deacon <will.deacon@arm.com>, Al Stone <al.stone@linaro.org>,
linaro-kernel@lists.linaro.org, linaro-acpi@lists.linaro.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, patches@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version
Date: Tue, 14 Jun 2016 15:50:39 +0100 [thread overview]
Message-ID: <20160614145039.GE14654@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <67e97389-c04e-b155-637b-a6bee4e24919@redhat.com>
On Tue, Jun 14, 2016 at 08:46:26AM -0600, Al Stone wrote:
> On 06/14/2016 03:24 AM, Will Deacon wrote:
> > On Tue, Jun 14, 2016 at 10:13:31AM +0100, Will Deacon wrote:
> >> On Mon, Jun 13, 2016 at 03:41:54PM -0600, Al Stone wrote:
> >>> This is a resend only: Ping? Last ping was 26 May; there has been zero
> >>> response since then. Already have one ACK from Lorenzo; another from an
> >>> arm64 maintainer would be really helpful.
> >>
> >> I thought there were outstanding comments on v4 of this?
> >>
> >> http://lkml.kernel.org/r/571E699B.9090906@linaro.org
> >
> > Hmm, that's weird. You sent a v5 on 25 April:
> >
> > http://archive.arm.linux.org.uk/lurker/message/20160425.212126.fe36116c.en.html
> >
> > but I can't find that in either my ARM inbox or my gmail inbox that's
> > subscribed to the lists. I guess Catalin can pick this up for 4.8.
>
> Huh. I have no idea why that would have happened. I used the same
> script to send the emails for all the revisions.
>
> Thanks for checking, Will. If this would get picked up for 4.8, that would be
> most excellent.
I'll queue it for 4.8 (should appear in -next towards the end of this
week).
--
Catalin
next prev parent reply other threads:[~2016-06-14 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 21:41 [RESEND PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version Al Stone
2016-06-13 21:41 ` [RESEND PATCH v5 1/1] " Al Stone
2016-06-14 9:13 ` [RESEND PATCH v5 0/1] " Will Deacon
2016-06-14 9:24 ` Will Deacon
2016-06-14 14:46 ` Al Stone
2016-06-14 14:50 ` Catalin Marinas [this message]
2016-06-14 14:52 ` Al Stone
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=20160614145039.GE14654@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=ahs3@redhat.com \
--cc=al.stone@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=will.deacon@arm.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).