From: "Dr. Greg" <greg@enjellic.com>
To: paul@paul-moore.com
Cc: linux-security-module@vger.kernel.org
Subject: TSEM feedback.
Date: Mon, 31 Jul 2023 05:38:22 -0500 [thread overview]
Message-ID: <20230731103822.GA4093@wind.enjellic.com> (raw)
Good morning Paul, I hope this note finds your week starting well.
We submitted the patches for the V2 release of TSEM three weeks ago.
We received some feedback from Randy Dunlap on some documentations
issues that we went on to address.
Haven't heard any reflections from you. Was just wondering if you
were swamped or had possibly missed the submission? We didn't include
you as a copy on the notion that you didn't need two sets of patches
landing in your inbox.
You can find the series with the following lore link:
https://lore.kernel.org/linux-security-module/20230710102319.19716-1-greg@enjellic.com/T/#t
Will look forward to any reflections you might have.
Have a good day.
As always,
Dr. Greg
The Quixote Project - Flailing at the Travails of Cybersecurity
next reply other threads:[~2023-07-31 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 10:38 Dr. Greg [this message]
2023-07-31 11:20 ` TSEM feedback Bagas Sanjaya
2023-07-31 14:57 ` Paul Moore
2023-08-01 10:54 ` Dr. Greg
2023-08-01 12:55 ` Serge E. Hallyn
2023-08-01 18:49 ` Paul Moore
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=20230731103822.GA4093@wind.enjellic.com \
--to=greg@enjellic.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox