public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Dr. Greg" <greg@enjellic.com>, paul@paul-moore.com
Cc: linux-security-module@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: TSEM feedback.
Date: Mon, 31 Jul 2023 18:20:53 +0700	[thread overview]
Message-ID: <ZMeZFRz/lH8Uz2mX@debian.me> (raw)
In-Reply-To: <20230731103822.GA4093@wind.enjellic.com>

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

On Mon, Jul 31, 2023 at 05:38:22AM -0500, Dr. Greg wrote:
> 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.

OK, please reroll with all reviews addressed.

As for the documentation, it seems that you missed Cc'ing
linux-doc@vger.kernel.org list, hence I didn't see your series. In any case,
run ``scripts/get_maintainer.pl`` to find maintainers, potential reviewers,
and lists that should have received your patch (series).

Last but not least, it'd been great if you can also link to public Git
repo containing your series (you already have the repo locally when
developing the series, right?), so I can simply ``git pull`` when about
to review yours.

See you in v2!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

           reply	other threads:[~2023-07-31 11:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230731103822.GA4093@wind.enjellic.com>]

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=ZMeZFRz/lH8Uz2mX@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=greg@enjellic.com \
    --cc=linux-kernel@vger.kernel.org \
    --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