From: Anand Jain <anand.jain@oracle.com>
To: fdmanana@kernel.org, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs: add missing commit ids for a few tests using _fixed_by_kernel_commit
Date: Sat, 16 Sep 2023 07:05:31 +0800 [thread overview]
Message-ID: <a0bcfebd-b5ca-c868-8ed8-49baec5862bc@oracle.com> (raw)
In-Reply-To: <be0250a9232aa614dd07b40e8cbbebb591fc3e0b.1694769988.git.fdmanana@suse.com>
On 15/09/2023 17:26, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> The tests btrfs/288, btrfs/289 and btrfs/300 are using the "xxxx..." stub
> for commit ids, as when they were submitted/merged the corresponding
> btrfs patches were not yet in Linus' tree. So replace the stubs with the
> commit ids.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
prev parent reply other threads:[~2023-09-15 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 9:26 [PATCH] btrfs: add missing commit ids for a few tests using _fixed_by_kernel_commit fdmanana
2023-09-15 23:05 ` Anand Jain [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=a0bcfebd-b5ca-c868-8ed8-49baec5862bc@oracle.com \
--to=anand.jain@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).