From: Mark Brown <broonie@kernel•org>
To: Jaegeuk Kim <jaegeuk@kernel•org>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Subject: Missing signoff in the f2fs tree
Date: Fri, 22 May 2026 11:23:50 +0100 [thread overview]
Message-ID: <ahAutugqas-sXq8S@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
Commits
6a59aa5442e33 ("f2fs: atomic: fix UAF issue on f2fs_inode_info.atomic_inode")
cf69827e772ca ("f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()")
are missing a Signed-off-by from their authors
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-05-22 10:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ahAutugqas-sXq8S@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=jaegeuk@kernel$(echo .)org \
--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