From: Vladis Dronov <vdronov@redhat.com>
To: ap420073@gmail.com
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] debugfs: Check module state before warning in {full/open}_proxy_open()
Date: Tue, 11 Aug 2020 17:34:28 +0200 [thread overview]
Message-ID: <20200811153428.58901-1-vdronov@redhat.com> (raw)
In-Reply-To: <20200218043150.29447-1-ap420073@gmail.com>
This fix does not work as intended, please see:
https://lore.kernel.org/linux-fsdevel/20200811150129.53343-1-vdronov@redhat.com/T/#u
Regards,
Vladis
prev parent reply other threads:[~2020-08-11 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 4:31 [PATCH v2 RESEND] debugfs: Check module state before warning in {full/open}_proxy_open() Taehee Yoo
2020-08-11 15:34 ` Vladis Dronov [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=20200811153428.58901-1-vdronov@redhat.com \
--to=vdronov@redhat.com \
--cc=ap420073@gmail.com \
--cc=linux-fsdevel@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).