Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/network-manager: bump to 1.52.2
Date: Mon, 27 Apr 2026 22:08:37 +0200	[thread overview]
Message-ID: <06064ec2e3c5cd488ca381bfeeeb4bb6@free.fr> (raw)
In-Reply-To: <20260216103714.802444-1-buildroot@bubu1.eu>

On 16/02/2026 11:37, Marcus Hoffmann via buildroot wrote:
> Overview of changes since NetworkManager-1.52.1[1]
> 
> * Support reapplying the "sriov.vfs" property as long as
>   "sriov.total-vfs" is not changed.
> * For private connections (the ones that specify a user in the
>   "connection.permissions" property), verify that the user can access
>   the 802.1X certificates and keys set in the connection.
> * Introduce a libnm function that can be used by VPN plugins to check
>   user permissions on certificate and keys.
> 
> [1] 
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/1.52.2/NEWS
> 
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>

Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-04-27 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 10:37 [Buildroot] [PATCH v2 1/2] package/network-manager: bump to 1.52.2 Marcus Hoffmann via buildroot
2026-02-16 10:37 ` [Buildroot] [PATCH v2 2/2] package/network-manager: bump to 1.56.0 Marcus Hoffmann via buildroot
2026-02-17 22:58   ` Fiona Klute via buildroot
2026-04-27 20:08 ` Julien Olivain 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=06064ec2e3c5cd488ca381bfeeeb4bb6@free.fr \
    --to=buildroot@buildroot.org \
    --cc=buildroot@bubu1.eu \
    --cc=ju.o@free.fr \
    /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