public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/zfs/files/
Date: Fri, 23 Sep 2022 20:15:51 +0000 (UTC)	[thread overview]
Message-ID: <1663964136.09a38ed7d7243ffebcb5ce419ec06e7991da96df.gyakovlev@gentoo> (raw)

commit:     09a38ed7d7243ffebcb5ce419ec06e7991da96df
Author:     Michael Mair-Keimberger <mmk <AT> levelnine <DOT> at>
AuthorDate: Mon Sep 19 06:54:38 2022 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Fri Sep 23 20:15:36 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=09a38ed7

sys-fs/zfs: remove unused patch

Signed-off-by: Michael Mair-Keimberger <mmk <AT> levelnine.at>
Portage 3.0.35 / pkgdev 0.2.1 / pkgcheck 0.10.14
Closes: https://github.com/gentoo/gentoo/pull/27350
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

 sys-fs/zfs/files/2.1.5-dracut-non-root.patch | 33 ----------------------------
 1 file changed, 33 deletions(-)

diff --git a/sys-fs/zfs/files/2.1.5-dracut-non-root.patch b/sys-fs/zfs/files/2.1.5-dracut-non-root.patch
deleted file mode 100644
index 6d1caf92cd2d..000000000000
--- a/sys-fs/zfs/files/2.1.5-dracut-non-root.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-https://github.com/openzfs/zfs/pull/13589
-https://bugs.gentoo.org/854333
-
-From ef9d996669cc2ec596d4e90753b89b32a3f0ce59 Mon Sep 17 00:00:00 2001
-From: "Andrew J. Hesford" <ajh@sideband.org>
-Date: Fri, 24 Jun 2022 11:05:53 -0400
-Subject: [PATCH] Dracut module: fix parsing of root= kernel command-line
- argument
-
-Some Dracut modules may read the `root=` kernel command-line argument
-and rewrite it; in particular, `rootfs-block` installs a command-line
-hook that to canonicalize arguments that specify block devices. If the
-`zfs` module is added to an initramfs (which it is, by default, as long
-as the core ZFS utilities are available) on a system that does not use a
-ZFS root filesystem, the `zfs` module will overwrite the `root` shell
-variable with the contents of the kernel command-line in the process of
-determining if it should control mounting the root. This breaks the
-initramfs. To solve this problem, only parse the kernel command-line
-directly if the `root` shell variable is empty; otherwise, rely on the
-parsing (and possible rewriting) done by other modules.
-
-Signed-off-by: Andrew J. Hesford <ajh@sideband.org>
---- a/contrib/dracut/90zfs/zfs-lib.sh.in
-+++ b/contrib/dracut/90zfs/zfs-lib.sh.in
-@@ -88,7 +88,7 @@ decode_root_args() {
-         return
-     fi
- 
--    root=$(getarg root=)
-+    [ -n  "$root" ] || root=$(getarg root=)
-     rootfstype=$(getarg rootfstype=)
- 
-     # shellcheck disable=SC2249


             reply	other threads:[~2022-09-23 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 20:15 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23  6:42 [gentoo-commits] repo/gentoo:master commit in: sys-fs/zfs/files/ Sam James
2023-07-04 22:17 Conrad Kostecki
2022-09-16 23:21 Georgy Yakovlev
2021-12-16  2:55 Georgy Yakovlev
2020-09-21 23:04 Georgy Yakovlev
2020-06-10 23:49 Georgy Yakovlev
2019-11-26 21:25 Georgy Yakovlev
2015-10-01 23:02 Richard Yao

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=1663964136.09a38ed7d7243ffebcb5ce419ec06e7991da96df.gyakovlev@gentoo \
    --to=gyakovlev@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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