From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@infradead.org>,
Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v2] freevxfs: don't BUG() on unknown typed-extent type
Date: Tue, 23 Jun 2026 12:04:40 +0200 [thread overview]
Message-ID: <20260623-anbot-kanon-imitieren-fea40d9418fd@brauner> (raw)
In-Reply-To: <CA+0ovChveuAwv=t15dr2m09E32bM48hHJxvfeEYZOhdNiEc9Tw@mail.gmail.com>
On Mon, 01 Jun 2026 20:10:08 -0700, Farhad Alemi wrote:
> freevxfs: don't BUG() on unknown typed-extent type
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/1] freevxfs: don't BUG() on unknown typed-extent type
https://git.kernel.org/vfs/vfs/c/f2f1b6ebe857
prev parent reply other threads:[~2026-06-23 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 3:35 [PATCH] " Farhad Alemi
2026-06-01 7:09 ` Christoph Hellwig
2026-06-02 3:10 ` [PATCH v2] " Farhad Alemi
2026-06-02 6:18 ` Christoph Hellwig
2026-06-23 10:04 ` 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=20260623-anbot-kanon-imitieren-fea40d9418fd@brauner \
--to=brauner@kernel.org \
--cc=farhad.alemi@berkeley.edu \
--cc=hch@infradead.org \
--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®