From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
	by lore.proxmox.com (Postfix) with ESMTPS id 2CC0B1FF13A
	for <inbox@lore.proxmox.com>; Wed, 13 May 2026 04:08:13 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 01A5B315BB;
	Wed, 13 May 2026 04:08:11 +0200 (CEST)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH storage] lvm plugin: encode locking requirement into
 the name of two helper functions
Date: Wed, 13 May 2026 04:05:24 +0200
Message-ID: <177863755628.3889845.17681281226081542276.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260213102816.17672-1-f.ebner@proxmox.com>
References: <20260213102816.17672-1-f.ebner@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1778637972948
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.003 Adjusted score from AWL reputation of From:
 address
	BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record
Message-ID-Hash: 4WZBOYMK6ZJDHLBGDFYZKBXJKQKTWAUW
X-Message-ID-Hash: 4WZBOYMK6ZJDHLBGDFYZKBXJKQKTWAUW
X-MailFrom: t.lamprecht@proxmox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; emergency; member-moderation; nonmember-moderation;
 administrivia; implicit-dest; max-recipients; max-size; news-moderation;
 no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Fri, 13 Feb 2026 11:27:03 +0100, Fiona Ebner wrote:
> Makes it easier to verify and keep track of the locking, and to not
> forget taking the lock for future callers.

Applied, thanks!

[1/1] lvm plugin: encode locking requirement into the name of two helper functions
      commit: 936bf28ee81124c6367d7a6ad4c7178c28f484ca