public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Gao Xiang <xiang@kernel.org>
Cc: Jingbo Xu <jefflexu@linux.alibaba.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the erofs-fixes tree
Date: Thu, 7 Mar 2024 17:17:43 +0800	[thread overview]
Message-ID: <a7d470b9-091e-4642-badd-a2b19eb3d02d@linux.alibaba.com> (raw)
In-Reply-To: <20240307081628.6a9e9b65@canb.auug.org.au>

Hi,

On 2024/3/7 05:16, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    f531a3c17e7a ("erofs: apply proper VMA alignment for memory mapped files on THP")
> 
> Fixes tag
> 
>    Fixes: be62c5198861 ("erofs: enable large folios for fscache mode")
> 
> has these problem(s):
> 
>    - Subject does not match target commit subject
>      Just use
>          git log -1 --format='Fixes: %h ("%s")'
> 
> So:
> 
> Fixes: be62c5198861 ("erofs: support large folios for fscache mode")

Thanks for the reminder!
It seems that I quoted the wrong commit id and it should be

Fixes: e6687b89225e ("erofs: enable large folios for fscache mode")

I've fixed in the erofs-fixes tree.

Thanks,
Gao Xiang

  reply	other threads:[~2024-03-07  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 21:16 linux-next: Fixes tag needs some work in the erofs-fixes tree Stephen Rothwell
2024-03-07  9:17 ` Gao Xiang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-07 20:34 Stephen Rothwell
2022-11-08  1:03 ` Gao Xiang

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=a7d470b9-091e-4642-badd-a2b19eb3d02d@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xiang@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