All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: [PATCH] btrfs/299: update kernel commit hash and subject
Date: Wed, 25 Jan 2023 11:07:39 +0000	[thread overview]
Message-ID: <3ccaa4e5f43538891d312ba7e9e4b38d61434d35.1674644818.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

Test case btrfs/299 refers to a kernel patch with a subject of:

   "btrfs: fix logical_ino ioctl panic"

However when the patch was merged, the subject was renamed to:

   "btrfs: fix resolving backrefs for inline extent followed by prealloc"

So update the test with the correct subject and also add the commit's
hash from Linus' tree.

Signed-off-by: Filipe Manana <fdmanana@suse.com>
---
 tests/btrfs/299 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tests/btrfs/299 b/tests/btrfs/299
index 42a08317..8ed23ac5 100755
--- a/tests/btrfs/299
+++ b/tests/btrfs/299
@@ -24,7 +24,8 @@ _require_scratch
 _require_xfs_io_command "falloc" "-k"
 _require_btrfs_command inspect-internal dump-tree
 _require_btrfs_command inspect-internal logical-resolve
-_fixed_by_kernel_commit xxxxxxxx "btrfs: fix logical_ino ioctl panic"
+_fixed_by_kernel_commit 560840afc3e6 \
+	"btrfs: fix resolving backrefs for inline extent followed by prealloc"
 
 dump_tree() {
 	$BTRFS_UTIL_PROG inspect-internal dump-tree $SCRATCH_DEV
-- 
2.35.1


             reply	other threads:[~2023-01-25 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 11:07 fdmanana [this message]
2023-01-25 12:15 ` [PATCH] btrfs/299: update kernel commit hash and subject David Disseldorp
2023-01-26  3:32 ` Anand Jain

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=3ccaa4e5f43538891d312ba7e9e4b38d61434d35.1674644818.git.fdmanana@suse.com \
    --to=fdmanana@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.