mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [PATCH v2 next 0/5] dm: lvm: Initial Logical Volume Management support
Date: Fri, 02 Oct 2026 07:57:14 +0200	[thread overview]
Message-ID: <179092063433.3100211.18305048568604878122.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260925105510.1431927-1-tobias@waldekranz.com>


On Fri, 25 Sep 2026 10:54:22 +0000, Tobias Waldekranz wrote:
> This series adds basic support for accessing LVM logical volumes.
> 
> Example session:
> 
>     wkz@spa:~/src/github.com/barebox/barebox$ ./barebox -i disk0=infix-x86_64.disk,blkdev
>     [...]
>     barebox@Sandbox:/ lvm info
>     VG "internal":
>       UUID:    sN8htx-oD18-wHWH-SuCU-1EWy-th1l-5WPU6j
>       SeqNum:  1
>       Size:    132 MiB (1 MiB extents)
>       #PV:     1
>       #LV:     1
>       PV disk0.2:
>         UUID:  6VHjVF-WVt7-Gk4Y-oTrK-lsgY-ve7N-GJ0CUn
>         Size:  134 MiB
>       LV "infix-x86_64.raw":
>         UUID:  Xp76Ig-9XXj-aBfK-Xv2U-rbsY-nEWX-omt4Bo
>         Type:  linear
>         Size:  132 MiB
>     barebox@Sandbox:/ lvm activate internal infix-x86_64.raw
>     [GPT warnings...]
>     Created internal-infix-x86_64.raw
>     barebox@Sandbox:/ ls /mnt/internal-infix-x86_64.raw.0/
>     mounted /dev/internal-infix-x86_64.raw.0 on /mnt/internal-infix-x86_64.raw.0
>     bin       boot      cfg       config    dev       etc       home
>     lib       lib64     loader    log       media     mnt       opt
>     proc      root      run       sbin      srv       sys       tmp
>     usr       var
>     barebox@Sandbox:/
> 
> [...]

Applied, thanks!

[1/5] dm: lvm: Initial Logical Volume Management support
      https://git.pengutronix.de/cgit/barebox/commit/?id=22c2baac6396 (link may not be stable)
[2/5] dm: lvm: Add fuzz testers for metadata parser and binary headers
      https://git.pengutronix.de/cgit/barebox/commit/?id=fad8dbd73014 (link may not be stable)
[3/5] test: self: lvm: Add tests for metadata parser and binary headers
      https://git.pengutronix.de/cgit/barebox/commit/?id=1a7b015fd6b4 (link may not be stable)
[4/5] commands: lvm: inspect VGs, activate LVs
      https://git.pengutronix.de/cgit/barebox/commit/?id=0aebdf94bcfc (link may not be stable)
[5/5] test: py: lvm: Add basic LV activation test
      https://git.pengutronix.de/cgit/barebox/commit/?id=cf82822866f5 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2026-10-02  5:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 10:54 Tobias Waldekranz
2026-09-25 10:54 ` [PATCH v2 next 1/5] " Tobias Waldekranz
2026-09-25 10:54 ` [PATCH v2 next 2/5] dm: lvm: Add fuzz testers for metadata parser and binary headers Tobias Waldekranz
2026-09-25 10:54 ` [PATCH v2 next 3/5] test: self: lvm: Add tests " Tobias Waldekranz
2026-09-25 10:54 ` [PATCH v2 next 4/5] commands: lvm: inspect VGs, activate LVs Tobias Waldekranz
2026-09-25 10:54 ` [PATCH v2 next 5/5] test: py: lvm: Add basic LV activation test Tobias Waldekranz
2026-10-02  5:57 ` Sascha Hauer [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=179092063433.3100211.18305048568604878122.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=tobias@waldekranz.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