From: xiubli@redhat.com
To: ceph-devel@vger.kernel.org
Cc: idryomov@gmail.com, jlayton@kernel.org, vshankar@redhat.com,
mchangir@redhat.com, Xiubo Li <xiubli@redhat.com>
Subject: [PATCH v2 0/2] ceph: update the oldest_client_tid via the renew caps
Date: Fri, 17 Nov 2023 16:15:07 +0800 [thread overview]
Message-ID: <20231117081509.723731-1-xiubli@redhat.com> (raw)
From: Xiubo Li <xiubli@redhat.com>
V2:
- a minor fix about incorrect switching oldest_tid to le64 reported by
kernel test robot <lkp@intel.com>
Xiubo Li (2):
ceph: rename create_session_open_msg() to create_session_full_msg()
ceph: update the oldest_client_tid via the renew caps
fs/ceph/mds_client.c | 32 ++++++++++++++++++++++++--------
1 file changed, 24 insertions(+), 8 deletions(-)
--
2.41.0
next reply other threads:[~2023-11-17 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 8:15 xiubli [this message]
2023-11-17 8:15 ` [PATCH v2 1/2] ceph: rename create_session_open_msg() to create_session_full_msg() xiubli
2023-11-17 8:15 ` [PATCH v2 2/2] ceph: update the oldest_client_tid via the renew caps xiubli
2024-02-06 9:25 ` Venky Shankar
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=20231117081509.723731-1-xiubli@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=mchangir@redhat.com \
--cc=vshankar@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).