From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the tpmdd tree
Date: Wed, 29 May 2024 01:41:04 +0300 [thread overview]
Message-ID: <D1LN1FCKDWHR.2VZQY8BBBCSIJ@kernel.org> (raw)
In-Reply-To: <20240529081930.487f7290@canb.auug.org.au>
On Wed May 29, 2024 at 1:19 AM EEST, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different
> commit (but the same patch):
>
> 7df9ef4f7b1e ("tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer")
Sorry it was my fault forgot to update 'next'.
Now it should be fixed.
I verified this also by rebasing Linus' tree, which went cleanly
and git push origin next did not require '-f', so hopefully now
all is good...
BR, Jarkko
next prev parent reply other threads:[~2024-05-28 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 22:19 linux-next: duplicate patch in the tpmdd tree Stephen Rothwell
2024-05-28 22:41 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 4:59 Stephen Rothwell
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=D1LN1FCKDWHR.2VZQY8BBBCSIJ@kernel.org \
--to=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox