From: Christian Brauner <brauner@kernel.org>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>,
gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] further lockref cleanups
Date: Thu, 30 Jan 2025 16:05:18 +0100 [thread overview]
Message-ID: <20250130-breitengrad-bergregion-ab2caff08b56@brauner> (raw)
In-Reply-To: <20250130135624.1899988-1-agruenba@redhat.com>
On Thu, 30 Jan 2025 14:56:20 +0100, Andreas Gruenbacher wrote:
> Here's an updated version with:
>
> * An additional comment saying that lockref_init() initializes
> count to 1.
>
> * Reviewed-by tags from Christoph.
>
> [...]
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/3] gfs2: use lockref_init for gl_lockref
https://git.kernel.org/vfs/vfs/c/6c789b8e0913
[2/3] gfs2: switch to lockref_init(..., 1)
https://git.kernel.org/vfs/vfs/c/69469b7ad4a4
[3/3] lockref: remove count argument of lockref_init
https://git.kernel.org/vfs/vfs/c/24239add174c
prev parent reply other threads:[~2025-01-30 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 13:56 Andreas Gruenbacher
2025-01-30 13:56 ` [PATCH v2 1/3] gfs2: use lockref_init for gl_lockref Andreas Gruenbacher
2025-01-30 13:56 ` [PATCH v2 2/3] gfs2: switch to lockref_init(..., 1) Andreas Gruenbacher
2025-01-30 13:56 ` [PATCH v2 3/3] lockref: remove count argument of lockref_init Andreas Gruenbacher
2025-01-30 15:05 ` Christian Brauner [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=20250130-breitengrad-bergregion-ab2caff08b56@brauner \
--to=brauner@kernel.org \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®