From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 5 Apr 2019 18:01:36 +0200 From: Borislav Petkov Subject: Re: [PATCH RFC 1/5] cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options Message-ID: <20190405160136.GI23348@zn.tnic> References: <20190405131211.GE23348@zn.tnic> <20190405142048.burthk2jnpcvi2om@treble> <20190405152059.GG23348@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190405152059.GG23348@zn.tnic> Sender: linux-arch-owner@vger.kernel.org Message-ID: <20190405160136.4tt7RfRZIEc9AAQ_k2zJ0AX2Oh1p-cAAYSJuQZnqAA0@z> List-Archive: List-Post: To: Josh Poimboeuf Cc: linux-kernel@vger.kernel.org, x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Andy Lutomirski , Peter Zijlstra , Jiri Kosina , Waiman Long , Andrea Arcangeli , Jon Masters , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , linuxppc-dev@lists.ozlabs.org, Martin Schwidefsky , Heiko Carstens , linux-s390@vger.kernel.org, Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, Greg Kroah-Hartman , Tyler Hicks , Linus Torvalds List-ID: Thinking about this more, we can shave off the first 4 chars and have it be: spec_mitigations= I think it is painfully clear which speculation mitigations we mean. And the other switches don't have "cpu_" prefixes too so... -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.