From: Lee Jones <lee@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Qunqin Zhao <zhaoqunqin@loongson.cn>,
herbert@gondor.apana.org.au, jarkko@kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
davem@davemloft.net, linux-crypto@vger.kernel.org,
peterhuewe@gmx.de, jgg@ziepe.ca, linux-integrity@vger.kernel.org,
sgarzare@redhat.com
Subject: Re: [GIT PULL] Immutable branch between MFD, Char and Crypto due for the v6.18 merge window
Date: Wed, 17 Sep 2025 10:38:23 +0100 [thread overview]
Message-ID: <20250917093823.GG3893363@google.com> (raw)
In-Reply-To: <20250916191658.GA1249009@ax162>
On Tue, 16 Sep 2025, Nathan Chancellor wrote:
> On Tue, Sep 16, 2025 at 08:58:35AM +0100, Lee Jones wrote:
> > On Fri, 12 Sep 2025, Nathan Chancellor wrote:
> > > > The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
> > > >
> > > > Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
> ...
> > > > Qunqin Zhao (4):
> > > ...
> > > > tpm: Add a driver for Loongson TPM device
> > >
> > > This one needs a fix up due to commit 07d8004d6fb9 ("tpm: add bufsiz
> > > parameter in the .send callback") in 6.17-rc1, as I am seeing the
> > > following error in next-20250912.
> > >
> > > drivers/char/tpm/tpm_loongson.c:48:17: error: initialization of 'int (*)(struct tpm_chip *, u8 *, size_t, size_t)' {aka 'int (*)(struct tpm_chip *, unsigned char *, long unsigned int, long unsigned int)'} from incompatible pointer type 'int (*)(struct tpm_chip *, u8 *, size_t)' {aka 'int (*)(struct tpm_chip *, unsigned char *, long unsigned int)'} [-Wincompatible-pointer-types]
> > > 48 | .send = tpm_loongson_send,
> > > | ^~~~~~~~~~~~~~~~~
> > > drivers/char/tpm/tpm_loongson.c:48:17: note: (near initialization for 'tpm_loongson_ops.send')
> > > drivers/char/tpm/tpm_loongson.c:31:12: note: 'tpm_loongson_send' declared here
> > > 31 | static int tpm_loongson_send(struct tpm_chip *chip, u8 *buf, size_t count)
> > > | ^~~~~~~~~~~~~~~~~
> > >
> > > Can you squash it or do you want a separate patch?
> > >
> > > Cheers,
> > > Nathan
> > >
> > > diff --git a/drivers/char/tpm/tpm_loongson.c b/drivers/char/tpm/tpm_loongson.c
> > > index a4ec23639911..9e50250763d1 100644
> > > --- a/drivers/char/tpm/tpm_loongson.c
> > > +++ b/drivers/char/tpm/tpm_loongson.c
> > > @@ -28,7 +28,7 @@ static int tpm_loongson_recv(struct tpm_chip *chip, u8 *buf, size_t count)
> > > return cmd_ret->data_len;
> > > }
> > >
> > > -static int tpm_loongson_send(struct tpm_chip *chip, u8 *buf, size_t count)
> > > +static int tpm_loongson_send(struct tpm_chip *chip, u8 *buf, size_t bufsiz, size_t count)
> > > {
> > > struct loongson_se_engine *tpm_engine = dev_get_drvdata(&chip->dev);
> > > struct tpm_loongson_cmd *cmd = tpm_engine->command;
> >
> > This will break my local branch.
> >
> > Any chance of an immutable pull-request for:
> >
> > 07d8004d6fb9 ("tpm: add bufsiz parameter in the .send callback")
>
> I might be missing something but this commit is in Linux 6.17-rc1, which
> this tree is based on according to both 'git log' and the lead in to
> your pull request at the top, so your local branch is already broken.
> That error message was taken from the tip of your tree and the fix was
> tested against it as well.
>
> "tpm: Add a driver for Loongson TPM device" was sent back in early July,
> so it was never updated for this conflict.
Ah, gotcha. I thought you were saying that 07d8004d6fb9 ("tpm: add
bufsiz parameter in the .send callback") was applied somewhere else. In
which case, I need to figure out why my build testing didn't catch it.
I'd be happy with a formal patch from you or I can create the patch and
add your {Reported,Suggested}-by. How would you like to proceed?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-09-17 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 7:20 [PATCH v12 0/4] Add Loongson Security Engine chip driver Qunqin Zhao
2025-07-05 7:20 ` [PATCH v12 1/4] mfd: Add support for Loongson Security Engine chip controller Qunqin Zhao
2025-07-05 7:20 ` [PATCH v12 2/4] crypto: loongson - add Loongson RNG driver support Qunqin Zhao
2025-08-19 12:55 ` Lee Jones
2025-08-20 2:33 ` Herbert Xu
2025-07-05 7:20 ` [PATCH v12 3/4] tpm: Add a driver for Loongson TPM device Qunqin Zhao
2025-07-07 9:48 ` Stefano Garzarella
2025-07-26 7:05 ` Qunqin Zhao
2025-07-19 12:09 ` Jarkko Sakkinen
2025-07-20 1:05 ` Huacai Chen
2025-07-05 7:20 ` [PATCH v12 4/4] MAINTAINERS: Add entry for Loongson Security Engine drivers Qunqin Zhao
2025-09-02 11:32 ` [PATCH v12 0/4] Add Loongson Security Engine chip driver Lee Jones
2025-09-02 11:33 ` Lee Jones
2025-09-02 12:42 ` [GIT PULL] Immutable branch between MFD, Char and Crypto due for the v6.18 merge window Lee Jones
2025-09-12 21:32 ` Nathan Chancellor
2025-09-16 7:58 ` Lee Jones
2025-09-16 8:00 ` Lee Jones
2025-09-16 19:16 ` Nathan Chancellor
2025-09-17 9:38 ` Lee Jones [this message]
2025-09-17 17:12 ` Nathan Chancellor
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=20250917093823.GG3893363@google.com \
--to=lee@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=peterhuewe@gmx.de \
--cc=sgarzare@redhat.com \
--cc=zhaoqunqin@loongson.cn \
/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