From: David Disseldorp <ddiss@suse.de>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs/299: update kernel commit hash and subject
Date: Wed, 25 Jan 2023 13:15:54 +0100 [thread overview]
Message-ID: <20230125131554.1fef6a07@echidna.fritz.box> (raw)
In-Reply-To: <3ccaa4e5f43538891d312ba7e9e4b38d61434d35.1674644818.git.fdmanana@suse.com>
On Wed, 25 Jan 2023 11:07:39 +0000, fdmanana@kernel.org wrote:
> 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>
Reviewed-by: David Disseldorp <ddiss@suse.de>
next prev parent reply other threads:[~2023-01-25 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 11:07 [PATCH] btrfs/299: update kernel commit hash and subject fdmanana
2023-01-25 12:15 ` David Disseldorp [this message]
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=20230125131554.1fef6a07@echidna.fritz.box \
--to=ddiss@suse.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox