[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180624101503.GA26953@zn.tnic>
Date: Sun, 24 Jun 2018 12:15:03 +0200
From: Borislav Petkov <bp@...en8.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...nel.org>, linux-crypto@...r.kernel.org,
Mike Galbraith <efault@....de>,
Alexey Dobriyan <adobriyan@...il.com>,
torvalds@...ux-foundation.org, jpoimboe@...hat.com,
luto@...nel.org, peterz@...radead.org, brgerst@...il.com,
hpa@...or.com, linux-kernel@...r.kernel.org, dvlasenk@...hat.com,
h.peter.anvin@...el.com,
linux-tip-commits <linux-tip-commits@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH] x86/crypto: Add missing RETs
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.
Powered by blists - more mailing lists