From: Arnd Bergmann <arnd@arndb.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: arm@kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [Urgent PATCH] arm64: dts: uniphier: fix IRQ trigger type of ARMv8 timer
Date: Thu, 11 Aug 2016 08:44:48 +0200 [thread overview]
Message-ID: <4943063.JrVaCOJD4r@wuerfel> (raw)
In-Reply-To: <CAK7LNAT5D0HmvpVPnX1oFw=KJSOavVjXT6ECHBuTOhNaKpdQLg@mail.gmail.com>
On Thursday, August 11, 2016 11:25:30 AM CEST Masahiro Yamada wrote:
> 2016-08-01 17:26 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> >>> I could do this after -rc1 is out because it is apparently a
> >>> bug fix, but in that case the for-next branch in ASOC will be
> >>> broken for me, which would make bisect-ability difficult for me.
> >>
> >> I have a patch that addresses all platforms in one go (there is really
> >> no point in fixing one at a time for a bug that is so widespread).
> >>
> >> I'll repost it later today.
> >>
> >
> > That'll be fine.
> > Thank you!
> >
> >
> > Arnd, Olof:
> > Please disregard this one.
> >
>
> Oh Dear.
> Did you apply this one?
>
> This was replaced with Marc'one:
> https://patchwork.kernel.org/patch/9254183/
Thanks for letting me know so quickly of my mistake, I was able
to back out the commit from the fixes branch as it was right at
the top.
Arnd
next prev parent reply other threads:[~2016-08-11 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 8:12 [Urgent PATCH] arm64: dts: uniphier: fix IRQ trigger type of ARMv8 timer Masahiro Yamada
2016-08-01 8:18 ` Marc Zyngier
2016-08-01 8:26 ` Masahiro Yamada
2016-08-11 2:25 ` Masahiro Yamada
2016-08-11 6:44 ` Arnd Bergmann [this message]
2016-08-10 20:52 ` Arnd Bergmann
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=4943063.JrVaCOJD4r@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.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