FS/XFS testing framework
 help / color / mirror / Atom feed
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] generic/708: fix commit subject and add its git hash
Date: Fri, 19 May 2023 13:23:09 +0800	[thread overview]
Message-ID: <9f1c6ecb-3cab-c3ba-8a43-15b73e5f2ec3@oracle.com> (raw)
In-Reply-To: <5f0b10c063fd6297c470dcc26cf2f3eaf412a943.1684407930.git.fdmanana@suse.com>

On 18/5/23 19:05, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> The test refers to a patch that ended up not committed to Linus' tree, as
> the fix evolved through several patchset versions. The up to date fix
> landed on kernel 6.4-rc1 and is the following:
> 
>      b73a6fd1b1ef "btrfs: split partial dio bios before submit"
> 
> So updated the test to point to that.
> 
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
>   tests/generic/708 | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/generic/708 b/tests/generic/708
> index 1f0843c7..6809a50c 100755
> --- a/tests/generic/708
> +++ b/tests/generic/708
> @@ -14,7 +14,8 @@
>   . ./common/preamble
>   _begin_fstest quick auto
>   [ $FSTYP == "btrfs" ] && \
> -	_fixed_by_kernel_commit XXXX 'btrfs: fix dio continue after short write due to buffer page fault'
> +	_fixed_by_kernel_commit b73a6fd1b1ef \
> +		"btrfs: split partial dio bios before submit"


Reviewed-by: Anand Jain <anand.jain@oracle.com>


>   
>   # real QA test starts here
>   _supported_fs generic


      reply	other threads:[~2023-05-19  5:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 11:05 [PATCH] generic/708: fix commit subject and add its git hash fdmanana
2023-05-19  5:23 ` 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=9f1c6ecb-3cab-c3ba-8a43-15b73e5f2ec3@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