From: Greg KH <gregkh@linuxfoundation.org>
To: cel@kernel.org
Cc: amir73il@gmail.com, krisman@collabora.com, jack@suse.cz,
sashal@kernel.org, stable@vger.kernel.org,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
tytso@mit.edu, alexey.makhalov@broadcom.com,
vasavi.sirnapalli@broadcom.com, florian.fainelli@broadcom.com,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v5.10.y 0/3] Apply fanotify-related documentation changes
Date: Tue, 13 Aug 2024 12:30:22 +0200 [thread overview]
Message-ID: <2024081313-shallot-nursing-6023@gregkh> (raw)
In-Reply-To: <20240725153229.13407-1-cel@kernel.org>
On Thu, Jul 25, 2024 at 11:32:26AM -0400, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> These extra commits were requested by Amir Goldstein
> <amir73il@gmail.com>. Note that c0baf9ac0b05 ("docs: Document the
> FAN_FS_ERROR event") is already applied to v5.10.y.
>
> Gabriel Krisman Bertazi (2):
> samples: Add fs error monitoring example
> samples: Make fs-monitor depend on libc and headers
>
> Linus Torvalds (1):
> Add gitignore file for samples/fanotify/ subdirectory
>
> samples/Kconfig | 8 ++
> samples/Makefile | 1 +
> samples/fanotify/.gitignore | 1 +
> samples/fanotify/Makefile | 5 ++
> samples/fanotify/fs-monitor.c | 142 ++++++++++++++++++++++++++++++++++
> 5 files changed, 157 insertions(+)
> create mode 100644 samples/fanotify/.gitignore
> create mode 100644 samples/fanotify/Makefile
> create mode 100644 samples/fanotify/fs-monitor.c
>
> --
> 2.45.2
>
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-08-13 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 15:32 [PATCH v5.10.y 0/3] Apply fanotify-related documentation changes cel
2024-07-25 15:32 ` [PATCH v5.10.y 1/3] samples: Add fs error monitoring example cel
2024-07-25 15:32 ` [PATCH v5.10.y 2/3] samples: Make fs-monitor depend on libc and headers cel
2024-07-25 15:32 ` [PATCH v5.10.y 3/3] Add gitignore file for samples/fanotify/ subdirectory cel
2024-08-13 10:30 ` Greg KH [this message]
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=2024081313-shallot-nursing-6023@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=alexey.makhalov@broadcom.com \
--cc=amir73il@gmail.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=florian.fainelli@broadcom.com \
--cc=jack@suse.cz \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=vasavi.sirnapalli@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.