[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160818133935.GA3737@gmail.com>
Date: Thu, 18 Aug 2016 15:39:35 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Josh Poimboeuf <jpoimboe@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kernel@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Brian Gerst <brgerst@...il.com>,
Kees Cook <keescook@...omium.org>,
Peter Zijlstra <peterz@...radead.org>,
Byungchul Park <byungchul.park@....com>,
Nilay Vaish <nilayvaish@...il.com>
Subject: Re: [PATCH v4 00/57] x86/dumpstack: rewrite x86 stack dump code
* Frederic Weisbecker <fweisbec@...il.com> wrote:
> > Josh Poimboeuf (57):
>
> I am personally unable to review a 57 patches series.
>
> Any chance you could split it into self-contained steps? In general doing so
> increase the chances for reviews, accelerate merging, improve maintainance...
Yes, please!
Series of no more than 4-6 patches, ordered in a logical fasion from lowest risk /
simplest towards highest risk / most complex.
Thanks,
Ingo
Powered by blists - more mailing lists