From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 0/2] Prepare for PTXdist 2020.04.0
Date: Thu, 9 Apr 2020 09:36:40 +0200 [thread overview]
Message-ID: <20200409073640.GM7599@pengutronix.de> (raw)
In-Reply-To: <20200409073533.30522-1-m.olbrich@pengutronix.de>
Hi,
Sorry, this was supposed to go to the Distrokit mailing list.
Michael
On Thu, Apr 09, 2020 at 09:35:31AM +0200, Michael Olbrich wrote:
> Here are some changes that are needed/useful for PTXdist 2020.04.0.
> The ptxd_make_nfsd_exec function has changed upstream so this first commit
> ensures that they are in sync again.
> The second patch makes use of the new features and enables
> security_model=mapped-file for the 9p rootfs when possible.
>
> Note, that both changes are backwards compatible. This can be merged before
> the update to 2020.04.0.
>
> Michael
>
> Michael Olbrich (2):
> ptxd_make_nfsd_exec: sync with upstream
> platform-v7a: run: use security_model=mapped-file when possible
>
> configs/platform-v7a/run | 12 +++++++++---
> configs/platform-v7a/scripts/lib/ptxd_make_nfsd.sh | 10 ++++++++--
> 2 files changed, 17 insertions(+), 5 deletions(-)
>
> --
> 2.20.1
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2020-04-09 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 7:35 Michael Olbrich
2020-04-09 7:35 ` [ptxdist] [PATCH 1/2] ptxd_make_nfsd_exec: sync with upstream Michael Olbrich
2020-04-09 7:35 ` [ptxdist] [PATCH 2/2] platform-v7a: run: use security_model=mapped-file when possible Michael Olbrich
2020-04-09 7:36 ` Michael Olbrich [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=20200409073640.GM7599@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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