linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filipe Manana <fdmanana@kernel.org>
To: Naohiro Aota <naohiro.aota@wdc.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 2/2] btrfs/076: use _fixed_by_kernel_commit to tell the fixing kernel commit
Date: Fri, 15 Sep 2023 10:17:54 +0100	[thread overview]
Message-ID: <CAL3q7H7HbiMGMO7=iYkAzdP+OTYyFmaHtUJS=nwhKsnOE-tZig@mail.gmail.com> (raw)
In-Reply-To: <d975ad16c184649e89c57dedcb85064cb385ca47.1694762532.git.naohiro.aota@wdc.com>

On Fri, Sep 15, 2023 at 8:28 AM Naohiro Aota <naohiro.aota@wdc.com> wrote:
>
> The fix commit is written in the comment without a commit hash. Use
> _fixed_by_kernel_commit command to describe it.
>
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>

Looks good,

Reviewed-by: Filipe Manana <fdmanana@suse.com>

> ---
>  tests/btrfs/076 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/btrfs/076 b/tests/btrfs/076
> index a5cc3eb96b2f..dbb67bd1c241 100755
> --- a/tests/btrfs/076
> +++ b/tests/btrfs/076
> @@ -5,10 +5,8 @@
>  # FS QA Test No. btrfs/076
>  #
>  # Regression test for btrfs incorrect inode ratio detection.
> -# This was fixed in the following linux kernel patch:
> -#
> -#     Btrfs: fix incorrect compression ratio detection
>  #
> +
>  . ./common/preamble
>  _begin_fstest auto quick compress
>
> @@ -27,6 +25,8 @@ _cleanup()
>  _supported_fs btrfs
>  _require_test
>  _require_scratch
> +_fixed_by_kernel_commit 4bcbb3325513 \
> +       "Btrfs: fix incorrect compression ratio detection"
>
>  # An extent size can be up to BTRFS_MAX_UNCOMPRESSED
>  max_extent_size=$(( 128 << 10 ))
> --
> 2.42.0
>

      reply	other threads:[~2023-09-15  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  7:25 [PATCH v2 0/2] btrfs/076: fix failure on device with small zone_append_max_bytes Naohiro Aota
2023-09-15  7:25 ` [PATCH v2 1/2] btrfs/076: support smaller extent size limit Naohiro Aota
2023-09-15  9:16   ` Filipe Manana
2023-09-21  7:41     ` Naohiro Aota
2023-09-21 17:09       ` Zorro Lang
2023-09-22  0:04         ` Naohiro Aota
2023-09-15  7:25 ` [PATCH v2 2/2] btrfs/076: use _fixed_by_kernel_commit to tell the fixing kernel commit Naohiro Aota
2023-09-15  9:17   ` Filipe Manana [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='CAL3q7H7HbiMGMO7=iYkAzdP+OTYyFmaHtUJS=nwhKsnOE-tZig@mail.gmail.com' \
    --to=fdmanana@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    /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).