From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH] x86/crypto: Add missing RETs Date: Sun, 24 Jun 2018 12:15:03 +0200 Message-ID: <20180624101503.GA26953@zn.tnic> References: <1529235613.4572.7.camel@gmx.de> <20180617120012.GB16877@zn.tnic> <1529242717.4472.3.camel@gmx.de> <1529244178.4674.1.camel@gmx.de> <20180617194747.GA21160@zn.tnic> <1529289279.31745.3.camel@gmx.de> <20180623103622.GA2760@zn.tnic> <20180624071105.GA29407@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Ingo Molnar , linux-crypto@vger.kernel.org, Mike Galbraith , Alexey Dobriyan , torvalds@linux-foundation.org, jpoimboe@redhat.com, luto@kernel.org, peterz@infradead.org, brgerst@gmail.com, hpa@zytor.com, linux-kernel@vger.kernel.org, dvlasenk@redhat.com, h.peter.anvin@intel.com, linux-tip-commits , Herbert Xu To: Thomas Gleixner Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Sun, Jun 24, 2018 at 09:12:35AM +0200, Thomas Gleixner wrote: > We should really have something like that exactly to catch cases like this. Sounds like a good use case for the snake language. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.