linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	"Martin Wilck" <Martin.Wilck@ts.fujitsu.com>,
	"Peter Huewe" <peterhuewe@gmx.de>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v2 0/3] tpm_tis: Clean up force module parameter
Date: Wed, 2 Dec 2015 10:11:14 +0200	[thread overview]
Message-ID: <20151202081114.GA3458@intel.com> (raw)
In-Reply-To: <20151201222223.GA27480@obsidianresearch.com>

On Tue, Dec 01, 2015 at 03:22:23PM -0700, Jason Gunthorpe wrote:
> On Tue, Dec 01, 2015 at 11:33:51PM +0200, Jarkko Sakkinen wrote:
> 
> > I went through the patches and didn't see anything that would shock me
> > enough not to apply the patches in the current if they also work when
> > tested *but* are these release critical for Linux v4.4?
> > 
> > I got a bit confused about the discussion that was going on about "where
> > to fix the probe" crash whether or not both it should be fixed in both
> > places.
> 
> I'm also confused by that..
> 
> It sounds like force=1 is broken in 4.4 right now - do we care? Should
> we fix this by using Martin's patch?
> 
> These changes are complex enough they really shouldn't go into 4.4
> unless absolutely necessary.

The reasons I'm asking this are:

* I'm planning to do v4.5 pull request soon.
* If this need to be get this into v4.4, we should act fast. Given the
  complexity of the changes I'd not recommend that unless it is a life
  and death question.

> > Could you possibly make these apply on top of security/next and
> > re-submit if needed?
> 
> It isn't trivial to reorder all 10 patches to do this, I'd like to
> know we need to do this for sure first. Uwe?

Agreed. First we have to know whether these changes have go to v4.4.

> Jason

/Jarkko

  parent reply	other threads:[~2015-12-02  8:11 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 18:58 [PATCH v2 0/3] tpm_tis: Clean up force module parameter Jason Gunthorpe
2015-12-01 18:58 ` [PATCH v2 1/3] tpm_tis: Disable interrupt auto probing on a per-device basis Jason Gunthorpe
2015-12-01 19:19   ` Uwe Kleine-König
2015-12-01 19:36     ` Jason Gunthorpe
2015-12-01 18:58 ` [PATCH v2 2/3] tpm_tis: Use devm_ioremap_resource Jason Gunthorpe
2015-12-01 19:22   ` Uwe Kleine-König
2015-12-01 19:44     ` Jason Gunthorpe
2015-12-01 19:52       ` Uwe Kleine-König
2015-12-01 20:46         ` Jason Gunthorpe
2015-12-01 18:58 ` [PATCH v2 3/3] tpm_tis: Clean up the force=1 module parameter Jason Gunthorpe
2015-12-01 19:33   ` Uwe Kleine-König
2015-12-01 19:51     ` Jason Gunthorpe
2015-12-01 21:14 ` [PATCH v2 0/3] tpm_tis: Clean up force " Jarkko Sakkinen
2015-12-01 21:33 ` Jarkko Sakkinen
2015-12-01 22:22   ` Jason Gunthorpe
2015-12-02  1:15     ` Peter Huewe
2015-12-02  8:14       ` Jarkko Sakkinen
2015-12-02  9:02         ` Peter Huewe
2015-12-02  8:11     ` Jarkko Sakkinen [this message]
2015-12-02  8:21       ` Uwe Kleine-König
2015-12-02 16:53         ` Greg Kroah-Hartman
2015-12-02 16:59           ` Uwe Kleine-König
2015-12-03  8:51           ` [PATCH v3] base/platform: fix binding for drivers without probe callback martin.wilck
2015-12-03  9:00             ` Uwe Kleine-König
2015-12-03  9:34             ` [tpmdd-devel] " Jarkko Sakkinen
2015-12-02 18:27   ` [PATCH v2 0/3] tpm_tis: Clean up force module parameter Jason Gunthorpe
2015-12-02 19:11     ` [tpmdd-devel] " Jason Gunthorpe
2015-12-03  6:00       ` Jarkko Sakkinen
2015-12-03 18:19         ` Jason Gunthorpe
2015-12-06  4:02           ` Jarkko Sakkinen
2015-12-06  4:15             ` Jarkko Sakkinen
2015-12-06  4:20               ` Jarkko Sakkinen
2015-12-07  6:15               ` Jason Gunthorpe
2015-12-07  8:06               ` Wilck, Martin
2015-12-07  8:56                 ` Jarkko Sakkinen
2015-12-07  9:52                   ` Wilck, Martin
2015-12-07 10:16                     ` Jarkko Sakkinen
2015-12-03  8:30       ` Wilck, Martin
2015-12-03 17:00         ` Jason Gunthorpe
2015-12-04  8:39           ` Wilck, Martin
2015-12-04  9:10           ` Wilck, Martin
2015-12-04 18:09             ` Jason Gunthorpe
2015-12-07  9:59               ` Wilck, Martin
2015-12-07 17:35                 ` Jason Gunthorpe
2015-12-03  5:58     ` Jarkko Sakkinen
2015-12-02 12:34 ` Wilck, Martin
2015-12-02 18:11   ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151202081114.GA3458@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=Martin.Wilck@ts.fujitsu.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).