From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>, Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>,
linux-next@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: Missing signoffs in the ext3 tree
Date: Fri, 6 Dec 2024 15:46:06 +0100 [thread overview]
Message-ID: <20241206144606.eltwdm6srrhlplss@quack3> (raw)
In-Reply-To: <1175596d-fdaf-4c99-9bf3-4a5f517ef09e@sirena.org.uk>
Hi!
On Fri 06-12-24 10:22:31, Mark Brown wrote:
> Commits
>
> 74094f677916e ("fanotify: don't skip extra event info if no info_mode is set")
> 8adc64d022177 ("fs: get rid of __FMODE_NONOTIFY kludge")
Thanks for noticing Mark.
Al, care to provide your signed-off-by for the
"fs: get rid of __FMODE_NONOTIFY kludge"? Amir then massaged the details
but you were indeed the original author of big part of the patch. Thanks!
Amir, I'm not sure about the authorship of "fanotify: don't skip extra
event info if no info_mode is set". Was it you or actually Josef?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-12-06 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 10:22 Missing signoffs in the ext3 tree Mark Brown
2024-12-06 14:46 ` Jan Kara [this message]
2024-12-06 14:52 ` Amir Goldstein
2024-12-06 15:06 ` Jan Kara
2024-12-06 17:28 ` Al Viro
2024-12-09 10:36 ` Jan Kara
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=20241206144606.eltwdm6srrhlplss@quack3 \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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