From: Pavel Reichl <preichl@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v12 4/4] xfs: replace mrlock_t with rw_semaphores
Date: Mon, 2 Nov 2020 20:45:47 +0100 [thread overview]
Message-ID: <fa33cd29-9b84-552e-b5f6-d4df723c879a@redhat.com> (raw)
In-Reply-To: <20201029223534.GP1061252@magnolia>
> Looks ok to me. Would you mind rebasing this against 5.10-rc1 so I can
> start testing a work branch with all the accumulated 5.11 stuff?
Hi,
version #13 is on the list - it's rebased against 5.10-rc1 and also contains the changes Brian proposed.
Bye.
prev parent reply other threads:[~2020-11-02 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 2:10 [PATCH v12 0/4] xfs: Remove wrappers for some semaphores Pavel Reichl
2020-10-16 2:10 ` [PATCH v12 1/4] xfs: Refactor xfs_isilocked() Pavel Reichl
2020-10-20 10:28 ` Brian Foster
2020-10-16 2:10 ` [PATCH v12 2/4] xfs: clean up whitespace in xfs_isilocked() calls Pavel Reichl
2020-10-16 2:10 ` [PATCH v12 3/4] xfs: xfs_isilocked() can only check a single lock type Pavel Reichl
2020-10-16 2:10 ` [PATCH v12 4/4] xfs: replace mrlock_t with rw_semaphores Pavel Reichl
2020-10-20 10:28 ` Brian Foster
2020-10-29 22:35 ` Darrick J. Wong
2020-11-02 19:45 ` Pavel Reichl [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=fa33cd29-9b84-552e-b5f6-d4df723c879a@redhat.com \
--to=preichl@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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).