[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171009154746.xb2mjjik2smuuenu@sirena.co.uk>
Date: Mon, 9 Oct 2017 16:47:46 +0100
From: Mark Brown <broonie@...nel.org>
To: "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Will Deacon <will.deacon@....com>,
Mark Rutland <mark.rutland@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Laura Abbott <labbott@...hat.com>
Subject: Re: [PATCH 4.9 086/104] arm64: kasan: avoid bad virt_to_pfn()
On Mon, Oct 09, 2017 at 02:00:53PM +0000, Levin, Alexander (Sasha Levin) wrote:
> In this case, for example, this patch had a "review cycle" of 18 days
> where 4 different emails regarding this patch were sent out as it was
> making it's way through review and queues, so we already try to be
> as "loud" as we can with it.
As someone on the reviewing side what I'm seeing is a bunch of stable
maintainers sending fairly large patch serieses that look like normal
stable review things. That's not very loud. I usually don't spend that
much time on stable reviews as up until this started happening anything
that went in was either something I'd pushed in directly or something
where I had spent more time on already after someone had sent a "hey, we
should backport this" mail. Mails that look like the ones that have
been sent are just confirming prior review.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists