From: Marius Kittler <mkittler@suse.de>
To: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] fanotify14: Revert broken flag support check
Date: Wed, 15 Nov 2023 14:10:06 +0100 [thread overview]
Message-ID: <6003663.lOV4Wx5bFT@linux-9lzf> (raw)
In-Reply-To: <20231115104148.8287-1-mdoucha@suse.cz>
Hi,
that change was definitely not part of the memcontrol-related patch I sent to
this mailinglist.
I think this change was part of another patchset I sent to the list. However,
this patchset definitely didn't contain out-commented code so someone was
editing it before pushing. When I remember correctly, I only changed the flags
as it was suggested to me as a review comment (and I personally wouldn't have
done this change in the first place).
So I'm fine with reverting the change.
Reviewed-by: Marius Kittler <mkittler@suse.de>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-11-15 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 10:41 [LTP] [PATCH] fanotify14: Revert broken flag support check Martin Doucha
2023-11-15 13:10 ` Marius Kittler [this message]
2023-11-21 11:55 ` Amir Goldstein
2023-11-21 12:08 ` Petr Vorel
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=6003663.lOV4Wx5bFT@linux-9lzf \
--to=mkittler@suse.de \
--cc=ltp@lists.linux.it \
/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