[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171220181005.GC22908@ziepe.ca>
Date: Wed, 20 Dec 2017 11:10:05 -0700
From: Jason Gunthorpe <jgg@...pe.ca>
To: "Shaikh, Azhar" <azhar.shaikh@...el.com>
Cc: Javier Martinez Canillas <javierm@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
James Ettle <james@...le.org.uk>,
Hans de Goede <hdegoede@...hat.com>,
Arnd Bergmann <arnd@...db.de>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Peter Huewe <peterhuewe@....de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>
Subject: Re: [PATCH 2/4] tpm: delete the TPM_TIS_CLK_ENABLE flag
On Wed, Dec 20, 2017 at 03:19:19PM +0000, Shaikh, Azhar wrote:
> >This flag is only used to warn if CLKRUN_EN wasn't disabled on Braswell
> >systems, but the only way this can happen is if the code is not correct.
> >
> >So it's an unnecessary check that just makes the code harder to read.
>
> This code was implemented as a suggestion from Jason on the previous patches.
> https://www.spinics.net/lists/linux-integrity/msg00827.html
The concept was to be like ASSERT_RTNL, maybe it just needs a suitably
named static inline to addrress Javier's readability concerns?
Jason
Powered by blists - more mailing lists