On Tue, May 09, 2017 at 02:45:02AM +0300, Jarkko Sakkinen wrote:
> On Thu, May 04, 2017 at 09:53:23AM -0600, Jason Gunthorpe wrote:
> > The test was backwards, triggering IRQ autoprobing if the firmware
> > did not specify an IRQ, instead of triggering it only when the
> > module force parameter was specified.
> > 
> > Since autoprobing is not enabled on !x86 and the platform device is
> > currently only used on !x86, or with force, this has gone unnoticed.
> > 
> > Fixes: 00194826e6be ("tpm_tis: Clean up the force=1 module parameter")
> > Tested-by: Jerry Snitselaar <jsnit...@redhat.com>
> > Signed-off-by: Jason Gunthorpe <jguntho...@obsidianresearch.com>
> 
> Reviewed-by: Jarkko Sakkinen <jarkko.sakki...@linux.intel.com>

Tested-by: Jarkko Sakkinen <jarkko.sakki...@linux.intel.com>

/Jarkko

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
tpmdd-devel mailing list
tpmdd-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tpmdd-devel

Reply via email to