From: Herbert Xu <herbert@gondor.apana.org.au>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
David Howells <dhowells@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] KEYS: asymmetric: Fix error codes
Date: Wed, 12 Jul 2023 09:27:42 +1000 [thread overview]
Message-ID: <ZK3lbns1A/kEOrcM@gondor.apana.org.au> (raw)
In-Reply-To: <93959358dc48d45b98aa598feae7307fa32c00d0.camel@kernel.org>
On Wed, Jul 12, 2023 at 12:51:45AM +0300, Jarkko Sakkinen wrote:
> On Tue, 2023-07-11 at 11:40 +0300, Dan Carpenter wrote:
> > On Tue, Jul 11, 2023 at 02:12:22AM +0300, Jarkko Sakkinen wrote:
> > > > > Fixes: 63ba4d67594a ("KEYS: asymmetric: Use new crypto interface without scatterlists")
> >
> > [ snip ]
> >
> > > >
> > > > I'll pick this as I'm late with 6.5 PR.
> > > >
> > > > Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> > >
> > > Causes merge conflicts with my tree:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/
> >
> > Your master branch doesn't include the "Use new crypto interface" commit
> > so it doesn't have the bug.
> >
> > (I'm just testing against linux-next and I don't know how the crypto
> > trees work).
> >
> > regards,
> > dan carpenter
>
> It is unfortunately based on Linus' tree :-/
Both this fix and the pathces it depends on have gone through
the crypto tree and is now merged upstream.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2023-07-11 23:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 14:18 [PATCH] KEYS: asymmetric: Fix error codes Dan Carpenter
2023-07-07 4:20 ` Herbert Xu
2023-07-07 6:01 ` David Howells
2023-07-10 23:10 ` Jarkko Sakkinen
2023-07-10 23:12 ` Jarkko Sakkinen
2023-07-11 8:40 ` Dan Carpenter
2023-07-11 21:51 ` Jarkko Sakkinen
2023-07-11 23:27 ` Herbert Xu [this message]
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=ZK3lbns1A/kEOrcM@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).