tpmdd-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 2/3] tpm xen: Remove bogus tpm_chip_unregister
Date: Wed, 2 Nov 2016 04:30:30 -0600	[thread overview]
Message-ID: <20161102103030.llb45xwnnlwokotm@intel.com> (raw)
In-Reply-To: <1477520926-32594-2-git-send-email-jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>

On Wed, Oct 26, 2016 at 04:28:45PM -0600, Jason Gunthorpe wrote:
> tpm_chip_unregister can only be called after tpm_chip_register.
> devm manages the allocation so no unwind is needed here.
> 
> Fixes: afb5abc262e96 ("tpm: two-phase chip management functions")

Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>

/Jarkko

> ---
>  drivers/char/tpm/xen-tpmfront.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/char/tpm/xen-tpmfront.c b/drivers/char/tpm/xen-tpmfront.c
> index 62028f483bba..a2ab00831df1 100644
> --- a/drivers/char/tpm/xen-tpmfront.c
> +++ b/drivers/char/tpm/xen-tpmfront.c
> @@ -307,7 +307,6 @@ static int tpmfront_probe(struct xenbus_device *dev,
>  	rv = setup_ring(dev, priv);
>  	if (rv) {
>  		chip = dev_get_drvdata(&dev->dev);
> -		tpm_chip_unregister(chip);
>  		ring_free(priv);
>  		return rv;
>  	}
> -- 
> 2.1.4
> 

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi

  parent reply	other threads:[~2016-11-02 10:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 22:28 [PATCH 1/3] tpm tis: Do not print timeout messages twice Jason Gunthorpe
     [not found] ` <1477520926-32594-1-git-send-email-jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-26 22:28   ` [PATCH 2/3] tpm xen: Remove bogus tpm_chip_unregister Jason Gunthorpe
     [not found]     ` <1477520926-32594-2-git-send-email-jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-11-02 10:30       ` Jarkko Sakkinen [this message]
     [not found]         ` <20161102103030.llb45xwnnlwokotm-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-11-04  7:23           ` Jarkko Sakkinen
2016-10-26 22:28   ` [PATCH 3/3] tpm: Get rid of TPM_CHIP_FLAG_REGISTERED Jason Gunthorpe
     [not found]     ` <1477520926-32594-3-git-send-email-jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-27 20:35       ` Winkler, Tomas
2016-11-02 10:33       ` Jarkko Sakkinen
2016-11-04  7:22         ` [tpmdd-devel] " Jarkko Sakkinen
2016-11-02 10:26   ` [PATCH 1/3] tpm tis: Do not print timeout messages twice Jarkko Sakkinen
2016-11-04  7:21     ` [tpmdd-devel] " Jarkko Sakkinen

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=20161102103030.llb45xwnnlwokotm@intel.com \
    --to=jarkko.sakkinen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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).