From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox 0/2] fix #7541: zfs status: account for msg directly after status in vdev parser
Date: Wed, 3 Jun 2026 18:01:34 +0200 [thread overview]
Message-ID: <6e92044d-dd66-4227-8a91-bc1042aca2fa@proxmox.com> (raw)
In-Reply-To: <20260603155822.370223-1-n.frey@proxmox.com>
this was meant to go to pbs-devel, sorry
prev parent reply other threads:[~2026-06-03 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 15:58 [PATCH proxmox 0/2] fix #7541: zfs status: account for msg directly after status in vdev parser Nicolas Frey
2026-06-03 15:58 ` [PATCH proxmox 1/2] disks: zpool: add `VDevStats` struct instead of 3 optional u64s Nicolas Frey
2026-06-03 15:58 ` [PATCH proxmox 2/2] fix #7541: zfs status: account for msg directly after status in vdev parser Nicolas Frey
2026-06-03 16:01 ` Nicolas Frey [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=6e92044d-dd66-4227-8a91-bc1042aca2fa@proxmox.com \
--to=n.frey@proxmox.com \
--cc=pve-devel@lists.proxmox.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