public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: jarkko@kernel.org
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	Rikard Falkeborn <rikard.falkeborn@gmail.com>,
	Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] tpm: Remove unintentional dump_stack() call
Date: Mon, 1 Mar 2021 22:08:55 +0100	[thread overview]
Message-ID: <YD1X553fpbyl7Kbw@rikard> (raw)
In-Reply-To: <20210301094409.14380-1-jarkko@kernel.org>

On Mon, Mar 01, 2021 at 11:44:09AM +0200, jarkko@kernel.org wrote:
> From: Jarkko Sakkinen <jarkko@kernel.org>
> 
> Somewhere along the line, probably during a rebase, an unintentional
> dump_stack() got included. Revert this change.
> 
> Reported-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>
> Fixes: 90cba8d20f8b ("tpm/ppi: Constify static struct attribute_group")
> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
> ---
>  drivers/char/tpm/tpm-chip.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/char/tpm/tpm-chip.c b/drivers/char/tpm/tpm-chip.c
> index 19e23fcc6bc8..ddaeceb7e109 100644
> --- a/drivers/char/tpm/tpm-chip.c
> +++ b/drivers/char/tpm/tpm-chip.c
> @@ -278,8 +278,6 @@ static void tpm_devs_release(struct device *dev)
>  {
>  	struct tpm_chip *chip = container_of(dev, struct tpm_chip, devs);
>  
> -	dump_stack();
> -
>  	/* release the master device reference */
>  	put_device(&chip->dev);
>  }
> -- 
> 2.30.1
> 

Acked-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>

  reply	other threads:[~2021-03-01 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  9:44 [PATCH] tpm: Remove unintentional dump_stack() call jarkko
2021-03-01 21:08 ` Rikard Falkeborn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-01 21:24 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=YD1X553fpbyl7Kbw@rikard \
    --to=rikard.falkeborn@gmail.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.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