All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Sergiy Kibrik <Sergiy_Kibrik@epam.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Daniel P. Smith" <dpsmith@apertussolutions.com>
Subject: Re: [PATCH v1 1/2] flask: add const qualifier to security_context_to_sid()
Date: Tue, 1 Sep 2026 08:34:11 +0200	[thread overview]
Message-ID: <cdc3f09f-0472-4660-8c08-b68d16c2b079@suse.com> (raw)
In-Reply-To: <5564a32f-31fa-4629-beb4-d87d19c2944d@epam.com>

On 31.08.2026 12:01, Sergiy Kibrik wrote:
> On 8/28/26 09:40, Jan Beulich wrote:
>> - While touching code anyway, it would be nice if u<N> was converted to
>>    uint<N>_t (or else we'll never complete that conversion).
>> I think I'll take the liberty of addressing all of these while committing.
> 
> thank you, Jan. BTW, what's up with u<N>? Are they expected to be 
> dropped/converted in Xen?

Yes. If you go look, s<N> were already dropped, as were __[su]<N>. The use
of u<N> sadly is far more widespread.

Jan


      reply	other threads:[~2026-09-01  6:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  9:38 [PATCH v1 0/2] XSM labels support in dom0less Sergiy Kibrik
2026-08-27  9:38 ` [PATCH v1 2/2] common: dom0less-bindings: introduce XSM labels Sergiy Kibrik
2026-08-27 18:09   ` Daniel P. Smith
2026-08-31 10:19   ` Andrew Cooper
2026-09-04 10:01     ` Sergiy Kibrik
2026-08-27  9:38 ` [PATCH v1 1/2] flask: add const qualifier to security_context_to_sid() Sergiy Kibrik
2026-08-27 18:08   ` Daniel P. Smith
2026-08-28  6:40   ` Jan Beulich
2026-08-31 10:01     ` Sergiy Kibrik
2026-09-01  6:34       ` Jan Beulich [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=cdc3f09f-0472-4660-8c08-b68d16c2b079@suse.com \
    --to=jbeulich@suse.com \
    --cc=Sergiy_Kibrik@epam.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=xen-devel@lists.xenproject.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.