From: Johannes Segitz <jsegitz@suse.de>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: "Cathy Hu" <cahu@suse.de>,
selinux@vger.kernel.org, jwcart2@gmail.com, plautrba@redhat.com,
omosnace@redhat.com, jason@perfinion.com, paul@paul-moore.com,
"Russell Coker" <russell@coker.com.au>,
"Laurent Bigonville" <bigon@debian.org>,
"Thiébaud Weksteen" <tweek@google.com>,
selinux@suse.de
Subject: Re: [PATCH v5] libsepol: drop support for policy versions before xperms_ioctl/xen_devicetree
Date: Mon, 7 Sep 2026 17:27:39 +0200 [thread overview]
Message-ID: <ap7X66Suk6ui4j7u@suse.com> (raw)
In-Reply-To: <CAEjxPJ5203DeJ_38pT9Kw86FFACh00z3YegMDzedvv9OcpG1qQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
Hi Stephen,
On Fri, Sep 04, 2026 at 11:13:32AM -0400, Stephen Smalley wrote:
> On Fri, Sep 4, 2026 at 8:50 AM Stephen Smalley <stephen.smalley.work@gmail.com> wrote:
> > Having heard no objections, I plan to re-base and merge this today.
>
> This is now merged but can be reverted if distros report problems.
I was on a (long) holiday, so delayed feedback for me. At least for SUSE
this is not a problem since we will never update very old products like SLE
12 to this, so breaking changing of this nature are no problem for us.
Johannes
--
GPG Key EE16 6BCE AD56 E034 BFB3 3ADD 7BF7 29D5 E7C8 1FA0
Subkey fingerprint: 250F 43F5 F7CE 6F1E 9C59 4F95 BC27 DD9D 2CC4 FD66
SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg, Germany
www.suse.com, Geschäftsführer: Jochen Jaser, Andrew McDonald, Abhinav Puri, (HRB 36809, AG Nürnberg)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
prev parent reply other threads:[~2026-09-07 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 12:55 [PATCH v5] libsepol: drop support for policy versions before xperms_ioctl/xen_devicetree Stephen Smalley
2026-08-31 18:01 ` Stephen Smalley
2026-08-31 19:51 ` Russell Coker
2026-08-31 19:56 ` Stephen Smalley
2026-09-01 8:40 ` Cathy Hu
2026-09-04 12:50 ` Stephen Smalley
2026-09-04 15:13 ` Stephen Smalley
2026-09-07 15:27 ` Johannes Segitz [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=ap7X66Suk6ui4j7u@suse.com \
--to=jsegitz@suse.de \
--cc=bigon@debian.org \
--cc=cahu@suse.de \
--cc=jason@perfinion.com \
--cc=jwcart2@gmail.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=plautrba@redhat.com \
--cc=russell@coker.com.au \
--cc=selinux@suse.de \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tweek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox