From: Ronnie Sahlberg <lsahlber@redhat.com>
To: linux-cifs <linux-cifs@vger.kernel.org>
Subject: [PATCH 0/1] cifs: move cifsFileInfo_put logic into a work-queue
Date: Wed, 30 Oct 2019 12:59:05 +1000 [thread overview]
Message-ID: <20191030025906.14395-1-lsahlber@redhat.com> (raw)
Pavel,
version 3 of the patch with your suggestions.
I left the full commit message of the deadlocked threads as is though.
next reply other threads:[~2019-10-30 2:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 2:59 Ronnie Sahlberg [this message]
2019-10-30 2:59 ` [PATCH] cifs: move cifsFileInfo_put logic into a work-queue Ronnie Sahlberg
2019-10-30 15:46 ` Pavel Shilovsky
2019-10-30 16:56 ` Pavel Shilovsky
2019-10-31 1:04 ` Ronnie Sahlberg
2019-10-31 20:47 ` Pavel Shilovsky
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 3:13 [PATCH 0/1] " Ronnie Sahlberg
2019-10-26 21:04 Ronnie Sahlberg
2019-10-27 23:52 ` Frank Sorenson
2019-10-28 22:51 ` Pavel Shilovsky
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=20191030025906.14395-1-lsahlber@redhat.com \
--to=lsahlber@redhat.com \
--cc=linux-cifs@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).