From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>
Cc: 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 vfs-fixes tree
Date: Wed, 7 May 2025 17:43:02 +1000 [thread overview]
Message-ID: <20250507174302.57e3eb62@canb.auug.org.au> (raw)
In-Reply-To: <20250429191520.5aa5f923@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
Hi all,
On Tue, 29 Apr 2025 19:15:20 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> In commit
>
> 72dbec48ca3c ("do_umount(): add missing barrier before refcount checks in sync case")
This is now commit
b2478f9bd75a ("do_umount(): add missing barrier before refcount checks in sync case")
> Fixes tag
>
> Fixes: 48a066e72d97 ("RCU'd vsfmounts")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> So:
>
> Fixes: 48a066e72d97 ("RCU'd vfsmounts")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-07 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 9:15 linux-next: Fixes tag needs some work in the vfs-fixes tree Stephen Rothwell
2025-05-07 7:43 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-29 9:13 Stephen Rothwell
2024-05-31 6:08 Stephen Rothwell
2021-03-25 20:51 Stephen Rothwell
2020-11-12 21:02 Stephen Rothwell
2020-11-12 21:14 ` Al Viro
2019-11-10 22:09 Stephen Rothwell
2019-10-21 20:44 Stephen Rothwell
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=20250507174302.57e3eb62@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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