All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Joshua Brindle <joshua.brindle@crunchydata.com>
Cc: Ondrej Mosnacek <omosnace@redhat.com>,
	SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH testsuite] tests: add test for default_range glblub support
Date: Wed, 4 Mar 2020 15:33:29 -0500	[thread overview]
Message-ID: <CAEjxPJ6_X=ceyf+Hy0qtY8L1ZgcJhwxnMBRQ1rwKZV9eFYJ8Yw@mail.gmail.com> (raw)
In-Reply-To: <CAGB+Vh4RVwSraAGn1caEXOvHySkmgzgAfV7aZ-pwWKeUVyV_ag@mail.gmail.com>

On Wed, Mar 4, 2020 at 12:11 PM Joshua Brindle
<joshua.brindle@crunchydata.com> wrote:
>
> On Wed, Mar 4, 2020 at 11:54 AM Stephen Smalley
> <stephen.smalley.work@gmail.com> wrote:
> >
> > On Tue, Mar 3, 2020 at 3:54 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > >
> > > Adds a basic test for the "glblub" default_range mode introduced in
> > > kernel commit [1] and userspace commit [2]. The test vectors are taken
> > > from the original commit messages.
>
> I'm confused, I submitted tests at Paul's request. The patch is here
> but says superceded:
> https://patchwork.kernel.org/patch/11119909/

Hmm...not sure whose fault that was; could be mine. Probably got
marked as superseded by accident
along with the earlier versions of the kernel and userspace patches.

      parent reply	other threads:[~2020-03-04 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03  8:52 [PATCH testsuite] tests: add test for default_range glblub support Ondrej Mosnacek
2020-03-03 20:01 ` Stephen Smalley
2020-03-04 16:55 ` Stephen Smalley
2020-03-04 17:11   ` Joshua Brindle
2020-03-04 17:18     ` Joshua Brindle
2020-03-04 20:57       ` Stephen Smalley
2020-03-04 21:42         ` Joshua Brindle
2020-03-05 13:10           ` Stephen Smalley
2020-03-05  8:16       ` Ondrej Mosnacek
2020-03-04 20:33     ` Stephen Smalley [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='CAEjxPJ6_X=ceyf+Hy0qtY8L1ZgcJhwxnMBRQ1rwKZV9eFYJ8Yw@mail.gmail.com' \
    --to=stephen.smalley.work@gmail.com \
    --cc=joshua.brindle@crunchydata.com \
    --cc=omosnace@redhat.com \
    --cc=selinux@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 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.