All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Matthew Garrett <mjg59@google.com>
Subject: Re: linux-next: build warning after merge of the tpmdd tree
Date: Thu, 13 Jun 2019 18:13:52 +0300	[thread overview]
Message-ID: <20190613151352.GB18488@linux.intel.com> (raw)
In-Reply-To: <20190611145255.68682629@canb.auug.org.au>

Matthew, can you provide a fixup for this?

/Jarkko

On Tue, Jun 11, 2019 at 02:52:55PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the tpmdd tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/firmware/efi/tpm.c: In function 'efi_tpm_eventlog_init':
> drivers/firmware/efi/tpm.c:80:10: warning: passing argument 1 of 'tpm2_calc_event_log_size' makes pointer from integer without a cast [-Wint-conversion]
>   tbl_size = tpm2_calc_event_log_size(efi.tpm_final_log
>                                       ~~~~~~~~~~~~~~~~~
>           + sizeof(final_tbl->version)
>           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>           + sizeof(final_tbl->nr_events),
>           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/firmware/efi/tpm.c:19:43: note: expected 'void *' but argument is of type 'long unsigned int'
>  static int tpm2_calc_event_log_size(void *data, int count, void *size_info)
>                                      ~~~~~~^~~~
> 
> Introduced by commit
> 
>   a537b15c54a3 ("tpm: Reserve the TPM final events table")
> 
> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2019-06-13 15:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  4:52 linux-next: build warning after merge of the tpmdd tree Stephen Rothwell
2019-06-13 15:13 ` Jarkko Sakkinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-11 10:00 Stephen Rothwell
2025-03-11 10:10 ` Jarkko Sakkinen
2025-03-11 14:21   ` Stuart Yoder
2025-03-12  6:16     ` Jarkko Sakkinen
2024-05-06  6:21 Stephen Rothwell
2024-05-06 10:48 ` Bagas Sanjaya
2024-05-06 10:55   ` Bagas Sanjaya
2019-02-07  2:47 Stephen Rothwell
2019-02-07 21:16 ` Jarkko Sakkinen
2018-01-02  2:50 Stephen Rothwell
2018-01-02  4:05 ` Shaikh, Azhar
2017-09-07  2:31 Stephen Rothwell
2017-09-07  8:43 ` Colin Ian King
2017-09-07 16:21   ` Jarkko Sakkinen
2016-11-15  1:01 Stephen Rothwell
2016-11-15  2:13 ` 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=20190613151352.GB18488@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mjg59@google.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.