From: Petr Vorel <pvorel@suse.cz>
To: Yael Tzur <yaelt@google.com>,
linux-integrity@vger.kernel.org, ltp@lists.linux.it,
Cyril Hrubis <chrubis@suse.cz>
Subject: Re: [LTP] [PATCH v4] syscalls/keyctl09: test encrypted keys with provided decrypted data.
Date: Wed, 23 Mar 2022 20:13:16 +0100 [thread overview]
Message-ID: <YjtxTJX91bwftEne@pevik> (raw)
In-Reply-To: <YjOcRn1qx0LHlO/j@pevik>
Hi all,
> > Hi Petr and Cyril,
> > I wanted to check whether there is pending action left on my end?
> @Yael nothing needed from you.
> @Cyril cd3bc044af48 ("KEYS: encrypted: Instantiate key with user-provided
> decrypted data") is in Mimi Zohar's git tree and in next tree, going to be
> merged in next merge window. Can we merge it now as is?
@Cyril cd3bc044af48 is in the next tree. Are we going to wait till it reaches
Linus' tree (in 5.18-rc1) or can I merge it now?
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220323&id=cd3bc044af483422cc81a93f23c78c20c978b17c
Kind regards,
Petr
> Kind regards,
> Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Yael Tzur <yaelt@google.com>,
linux-integrity@vger.kernel.org, ltp@lists.linux.it,
Cyril Hrubis <chrubis@suse.cz>
Subject: Re: [LTP] [PATCH v4] syscalls/keyctl09: test encrypted keys with provided decrypted data.
Date: Wed, 23 Mar 2022 20:13:16 +0100 [thread overview]
Message-ID: <YjtxTJX91bwftEne@pevik> (raw)
In-Reply-To: <YjOcRn1qx0LHlO/j@pevik>
Hi all,
> > Hi Petr and Cyril,
> > I wanted to check whether there is pending action left on my end?
> @Yael nothing needed from you.
> @Cyril cd3bc044af48 ("KEYS: encrypted: Instantiate key with user-provided
> decrypted data") is in Mimi Zohar's git tree and in next tree, going to be
> merged in next merge window. Can we merge it now as is?
@Cyril cd3bc044af48 is in the next tree. Are we going to wait till it reaches
Linus' tree (in 5.18-rc1) or can I merge it now?
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220323&id=cd3bc044af483422cc81a93f23c78c20c978b17c
Kind regards,
Petr
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-03-23 19:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 20:07 [PATCH v4] syscalls/keyctl09: test encrypted keys with provided decrypted data Yael Tzur
2022-02-23 20:07 ` [LTP] " Yael Tzur via ltp
2022-03-02 15:53 ` Cyril Hrubis
2022-03-02 15:53 ` Cyril Hrubis
2022-03-02 20:16 ` Yael Tzur
2022-03-02 20:16 ` Yael Tzur via ltp
2022-03-03 6:14 ` Petr Vorel
2022-03-03 6:14 ` Petr Vorel
2022-03-03 12:44 ` Cyril Hrubis
2022-03-03 12:44 ` Cyril Hrubis
2022-03-03 13:26 ` Petr Vorel
2022-03-03 13:26 ` Petr Vorel
2022-03-03 13:46 ` Cyril Hrubis
2022-03-03 13:46 ` Cyril Hrubis
2022-03-03 14:07 ` Petr Vorel
2022-03-03 14:07 ` Petr Vorel
2022-03-16 20:10 ` Yael Tzur
2022-03-16 20:10 ` Yael Tzur via ltp
2022-03-17 20:38 ` Petr Vorel
2022-03-17 20:38 ` Petr Vorel
2022-03-23 19:13 ` Petr Vorel [this message]
2022-03-23 19:13 ` Petr Vorel
2022-03-24 13:35 ` Cyril Hrubis
2022-03-24 13:35 ` Cyril Hrubis
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=YjtxTJX91bwftEne@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=yaelt@google.com \
/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.