From: Christian Brauner <brauner@kernel.org>
To: I Hsin Cheng <richard120310@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] file: Wrap locking mechanism for f_pos_lock
Date: Wed, 4 Dec 2024 17:07:29 +0100 [thread overview]
Message-ID: <20241204-entrollt-nestbau-e45aada983e1@brauner> (raw)
In-Reply-To: <Z1B2Lxxenie3SA6d@vaxr-BM6660-BM6360>
> Is it just for the inline function speed up?
Yes, very likely.
next prev parent reply other threads:[~2024-12-04 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 9:23 [RFC PATCH] file: Wrap locking mechanism for f_pos_lock I Hsin Cheng
2024-12-04 10:26 ` Jan Kara
2024-12-04 11:11 ` Christian Brauner
2024-12-04 12:48 ` Jan Kara
2024-12-04 15:33 ` I Hsin Cheng
2024-12-04 16:07 ` Christian Brauner [this message]
2024-12-04 16:34 ` Al Viro
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=20241204-entrollt-nestbau-e45aada983e1@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard120310@gmail.com \
--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 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.