From: Mateusz Guzik <mjguzik@gmail.com>
To: brauner@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH 0/2] 2 cosmetic changes
Date: Wed, 4 Oct 2023 13:19:14 +0200 [thread overview]
Message-ID: <20231004111916.728135-1-mjguzik@gmail.com> (raw)
both were annoying me for some time, so I'm pushing them out
These patches don't warrant arguing nor pinging in case of no response,
so if you don't like them that's it for the patchset. :)
cheers
Mateusz Guzik (2):
vfs: predict the error in retry_estale as unlikely
vfs: stop counting on gcc not messing with mnt_expiry_mark if not
asked
fs/namespace.c | 4 ++--
include/linux/namei.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.39.2
next reply other threads:[~2023-10-04 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 11:19 Mateusz Guzik [this message]
2023-10-04 11:19 ` [PATCH 1/2] vfs: predict the error in retry_estale as unlikely Mateusz Guzik
2023-10-04 11:19 ` [PATCH 2/2] vfs: stop counting on gcc not messing with mnt_expiry_mark if not asked Mateusz Guzik
2023-10-09 16:14 ` [PATCH 0/2] 2 cosmetic changes Christian Brauner
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=20231004111916.728135-1-mjguzik@gmail.com \
--to=mjguzik@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).