From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jarkko Sakkinen <jarkko.sakkinen@linux•intel.com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Roberto Sassu <roberto.sassu@huawei•com>
Subject: linux-next: build warning after merge of the tpmdd tree
Date: Thu, 7 Feb 2019 13:47:33 +1100 [thread overview]
Message-ID: <20190207134733.05a8e55a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]
Hi Jarkko,
After merging the tpmdd tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/char/tpm/tpm_i2c_nuvoton.c:45: warning: "TPM_RETRY" redefined
#define TPM_RETRY 5
In file included from drivers/char/tpm/tpm_i2c_nuvoton.c:35:
drivers/char/tpm/tpm.h:43: note: this is the location of the previous definition
#define TPM_RETRY 50
drivers/char/tpm/tpm_i2c_infineon.c:30: warning: "TPM_BUFSIZE" redefined
#define TPM_BUFSIZE 1260
In file included from drivers/char/tpm/tpm_i2c_infineon.c:27:
drivers/char/tpm/tpm.h:41: note: this is the location of the previous definition
#define TPM_BUFSIZE 4096
In file included from drivers/char/tpm/st33zp24/i2c.c:30:
drivers/char/tpm/st33zp24/st33zp24.h:22: warning: "TPM_BUFSIZE" redefined
#define TPM_BUFSIZE 2048
In file included from drivers/char/tpm/st33zp24/i2c.c:29:
drivers/char/tpm/st33zp24/../tpm.h:41: note: this is the location of the previous definition
#define TPM_BUFSIZE 4096
In file included from drivers/char/tpm/st33zp24/spi.c:30:
drivers/char/tpm/st33zp24/st33zp24.h:22: warning: "TPM_BUFSIZE" redefined
#define TPM_BUFSIZE 2048
In file included from drivers/char/tpm/st33zp24/spi.c:29:
drivers/char/tpm/st33zp24/../tpm.h:41: note: this is the location of the previous definition
#define TPM_BUFSIZE 4096
In file included from drivers/char/tpm/st33zp24/st33zp24.c:34:
drivers/char/tpm/st33zp24/st33zp24.h:22: warning: "TPM_BUFSIZE" redefined
#define TPM_BUFSIZE 2048
In file included from drivers/char/tpm/st33zp24/st33zp24.c:33:
drivers/char/tpm/st33zp24/../tpm.h:41: note: this is the location of the previous definition
#define TPM_BUFSIZE 4096
In file included from drivers/char/tpm/st33zp24/st33zp24.c:34:
drivers/char/tpm/st33zp24/st33zp24.h:22: warning: "TPM_BUFSIZE" redefined
#define TPM_BUFSIZE 2048
In file included from drivers/char/tpm/st33zp24/st33zp24.c:33:
drivers/char/tpm/st33zp24/../tpm.h:41: note: this is the location of the previous definition
#define TPM_BUFSIZE 4096
Introduced by commit
569c1057f9ac ("tpm: move tpm_chip definition to include/linux/tpm.h")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-02-07 2:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 2:47 Stephen Rothwell [this message]
2019-02-07 21:16 ` linux-next: build warning after merge of the tpmdd tree Jarkko Sakkinen
-- 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-06-11 4:52 Stephen Rothwell
2019-06-13 15:13 ` 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=20190207134733.05a8e55a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jarkko.sakkinen@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=roberto.sassu@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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