From: Thomas Gleixner <tglx@linutronix.de>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: linux@rasmusvillemoes.dk, catalin.marinas@arm.com,
will.deacon@arm.com, LKML <linux-kernel@vger.kernel.org>,
linux-kselftest@vger.kernel.org, vincenzo.frascino@arm.com,
shuah@kernel.org, linux-arch@vger.kernel.org,
Will Deacon <will@kernel.org>,
daniel.lezcano@linaro.org, arnd@arndb.de, andre.przywara@arm.com,
Chris Clayton <chris2553@googlemail.com>,
0x7f454c46@gmail.com, pcc@google.com,
linux-arm-kernel@lists.infradead.org, huw@codeweavers.com,
linux-mips@vger.kernel.org, ralf@linux-mips.org,
salyzyn@android.com, paul.burton@mips.com, sthotton@marvell.com
Subject: Re: Regression in 5.3-rc1 and later
Date: Fri, 23 Aug 2019 14:25:58 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908231424230.1896@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190823111712.GB13294@shell.armlinux.org.uk>
On Fri, 23 Aug 2019, Russell King - ARM Linux admin wrote:
> On Fri, Aug 23, 2019 at 11:40:50AM +0100, Will Deacon wrote:
> > On Fri, Aug 23, 2019 at 11:36:54AM +0100, Russell King - ARM Linux admin wrote:
> > > To everyone on the long Cc list...
> > >
> > > What's happening with this? I was about to merge the patches for 32-bit
> > > ARM, which I don't want to do if doing so will cause this regression on
> > > 32-bit ARM as well.
> >
> > tglx fixed it:
> >
> > https://lkml.kernel.org/r/alpine.DEB.2.21.1908221257580.1983@nanos.tec.linutronix.de
> >
> > which I assume is getting routed as a fix via -tip.
>
> Right, so Chris reported the issue to everyone involved. Tglx's
> reply severely trimmed the Cc list so folk like me had no idea what
> was going on, removing even the mailing lists. On the face of it,
> it looks like an intentional attempt to cut people out of the loop
> who really should've been kept in the loop. Yea, that's just great.
Sorry that was no intentional attempt to cut anyone out of the
loop. Trimmed it too agressively without applying much brain.
Thanks,
tglx
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-23 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 6:57 Regression in 5.3-rc1 and later Chris Clayton
2019-08-23 10:36 ` Russell King - ARM Linux admin
2019-08-23 10:40 ` Will Deacon
2019-08-23 11:17 ` Russell King - ARM Linux admin
2019-08-23 12:25 ` Thomas Gleixner [this message]
2019-08-23 10:43 ` Vincenzo Frascino
2019-08-23 10:51 ` Russell King - ARM Linux admin
2019-08-23 12:27 ` Thomas Gleixner
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=alpine.DEB.2.21.1908231424230.1896@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=0x7f454c46@gmail.com \
--cc=andre.przywara@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=chris2553@googlemail.com \
--cc=daniel.lezcano@linaro.org \
--cc=huw@codeweavers.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=paul.burton@mips.com \
--cc=pcc@google.com \
--cc=ralf@linux-mips.org \
--cc=salyzyn@android.com \
--cc=shuah@kernel.org \
--cc=sthotton@marvell.com \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@arm.com \
--cc=will@kernel.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 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).