From: Mark Brown <broonie@kernel•org>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software•com>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Subject: Fixes tags need work in the ntfs3 tree
Date: Fri, 29 May 2026 12:49:22 +0100 [thread overview]
Message-ID: <ahl9QtsR38b4FuXO@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
In commit
6b6fbad790ef1 ("ntfs3: Allocate iomap inline_data using alloc_page")
Fixes tag
Fixes: 099ef9a ("fs/ntfs3: implement iomap-based file operations")
has these problem(s):
- SHA1 should be at least 12 digits long
This can be fixed for the future by setting core.abbrev to 12 (or
more) or (for git v2.11 or later) just making sure it is not set
(or set to "auto").
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-05-29 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 11:49 Mark Brown [this message]
2026-06-02 15:08 ` Fixes tags need work in the ntfs3 tree Konstantin Komarov
-- strict thread matches above, loose matches on Subject: below --
2026-06-03 7:17 Mark Brown
2026-06-03 14:41 ` Konstantin Komarov
2026-06-03 7:16 Mark Brown
2026-06-03 14:41 ` Konstantin Komarov
2026-05-18 8:11 Mark Brown
2026-06-02 15:08 ` Konstantin Komarov
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=ahl9QtsR38b4FuXO@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=almaz.alexandrovich@paragon-software$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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