Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alex Kiernan <alex.kiernan@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alex Kiernan <alex.kiernan@gmail.com>
Subject: [PATCH v2 0/2] eudev: upgrade 3.2.14 -> 3.2.15
Date: Sat, 17 Oct 2026 17:01:48 +0100	[thread overview]
Message-ID: <20261017-eudev-3-2-15-v2-0-489cff4613f3@gmail.com> (raw)

eudev 3.2.15 adds a render group for DRM render nodes, so we add that to
base-passwd first, then upgrade eudev.

Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
---
Changes in v2:
- add a fix, submitted upstream, for a use-after-free new in 3.2.15
- eudev: link the upstream release notes instead of the shortlog
- Link to v1: https://patch.msgid.link/20261015-eudev-3-2-15-v1-0-407ba1a93edb@gmail.com

---
Alex Kiernan (2):
      base-passwd: add the render group for eudev-3.2.15
      eudev: upgrade 3.2.14 -> 3.2.15

 .../0001-base-passwd-add-the-render-group.patch    |  29 +++++
 meta/recipes-core/base-passwd/base-passwd_3.6.8.bb |  16 +++
 ....c-sync-dev_urandom-implementation-to-sys.patch | 138 ---------------------
 ...01-udevd-keep-a-copy-of-the-event-devnode.patch | 101 +++++++++++++++
 meta/recipes-core/udev/eudev/netifnames.patch      |  17 ---
 .../udev/{eudev_3.2.14.bb => eudev_3.2.15.bb}      |   5 +-
 6 files changed, 148 insertions(+), 158 deletions(-)
---
base-commit: 7803450fd5ecc1bb714abadfbe3ec340e930139a
change-id: 20261015-eudev-3-2-15-e406a27a8c72

Best regards,
--  
Alex Kiernan <alex.kiernan@gmail.com>



             reply	other threads:[~2026-10-17 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 16:01 Alex Kiernan [this message]
2026-10-17 16:01 ` [PATCH v2 1/2] base-passwd: add the render group for eudev-3.2.15 Alex Kiernan
2026-10-17 16:01 ` [PATCH v2 2/2] eudev: upgrade 3.2.14 -> 3.2.15 Alex Kiernan

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=20261017-eudev-3-2-15-v2-0-489cff4613f3@gmail.com \
    --to=alex.kiernan@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox