Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Alistair Francis <alistair@alistair23.me>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/xen: fix selinux module
Date: Mon, 6 Nov 2023 22:06:06 +0100	[thread overview]
Message-ID: <20231106220606.3394d0dc@windsurf> (raw)
In-Reply-To: <20231106201309.7280-1-fontaine.fabrice@gmail.com>

On Mon,  6 Nov 2023 21:13:09 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Fix the following refpolicy build failure raised since commit
> 64ce823223fece5c106994d9654a126fc6161d6a:
> 
> policy/modules/system/xen.te:559:ERROR 'type udev_runtime_t is not within scope' at token ';' on line 628879:
> 	allow xm_t udev_runtime_t:dir { open read getattr lock search ioctl add_name remove_name write };
> 
> [...]
> 
> policy/modules/system/udev.te:205:ERROR 'unknown type systemd_hwdb_t' at token ';' on line 582304:
>         allow udev_t systemd_hwdb_t:file map;
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/849050b00a2ee5983c2324cb955cd533189a0460
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/xen/xen.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 20:13 [Buildroot] [PATCH 1/1] package/xen: fix selinux module Fabrice Fontaine
2023-11-06 21:06 ` Thomas Petazzoni via buildroot [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=20231106220606.3394d0dc@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alistair@alistair23.me \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.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