From: Paul Moore <paul@paul-moore.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Stephen Smalley <stephen.smalley.work@gmail.com>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] selinux: fix variable scope issue in live sidtab conversion
Date: Thu, 18 Mar 2021 10:49:36 -0400 [thread overview]
Message-ID: <CAHC9VhQK8=RbJJv3ADRmajNzmpHcK53mkN3vnmMjrwKVMn2jVA@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNs9U30ydS76Gw7A2m9v6F6XdPgc2F8HmOyHfOhFt+w1JA@mail.gmail.com>
On Thu, Mar 18, 2021 at 7:45 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> No, I've been waiting for a reply regarding pr_warn() vs. pr_err(),
> etc. on patch 1/2 (and then it slipped off my mind, so I didn't follow
> up...)
Sorry about that, it looks like it was a casualty of my inbox. I just
replied back on that thread.
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2021-03-18 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 18:59 [PATCH v2 0/2] selinux: policy load fixes Ondrej Mosnacek
2021-02-12 18:59 ` [PATCH v2 1/2] selinux: don't log MAC_POLICY_LOAD record on failed policy load Ondrej Mosnacek
2021-02-25 18:14 ` Paul Moore
2021-02-26 14:46 ` Ondrej Mosnacek
2021-02-28 18:52 ` Paul Moore
2021-03-03 2:55 ` Tyler Hicks
2021-03-03 8:54 ` Ondrej Mosnacek
2021-03-18 14:48 ` Paul Moore
2021-03-18 15:12 ` Stephen Smalley
2021-02-12 18:59 ` [PATCH v2 2/2] selinux: fix variable scope issue in live sidtab conversion Ondrej Mosnacek
2021-02-25 19:20 ` Paul Moore
2021-02-26 14:47 ` Ondrej Mosnacek
2021-03-03 2:57 ` Tyler Hicks
2021-03-03 9:01 ` Ondrej Mosnacek
2021-03-18 11:22 ` Stephen Smalley
2021-03-18 11:45 ` Ondrej Mosnacek
2021-03-18 14:49 ` Paul Moore [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='CAHC9VhQK8=RbJJv3ADRmajNzmpHcK53mkN3vnmMjrwKVMn2jVA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tyhicks@linux.microsoft.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.