From: Dennis Semakin <insane79@yandex.ru>
To: jbrassow@redhat.com, agk@redhat.com, asi@seznam.cz,
j-nomura@ce.jp.nec.com, andmike@linux.vnet.ibm.com,
christophe.varoqui@free.fr, bmarzins@redhat.com,
k-ueda@ct.jp.nec.com, snitzer@redhat.com, dm-devel@redhat.com
Subject: Forward SECDISCARD request within device mapper layer
Date: Fri, 16 Feb 2018 14:38:00 +0300 [thread overview]
Message-ID: <4411521518781080@web43j.yandex.ru> (raw)
Hello.
Recently I've submitted the patch https://patchwork.kernel.org/patch/10182691/
about forwarding SECDISCARD request.
May I know your thoughts about it? Is it so bad and ugly? Is it so unneeded to provide this request?
I just want to know your opinion.
If it's not applicable then I could re-write it.
I've successfully tested it for 3.10 and 3.18 kernels.
Best regards,
Denis Semakin
next reply other threads:[~2018-02-16 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 11:38 Dennis Semakin [this message]
2018-02-16 21:58 ` Forward SECDISCARD request within device mapper layer Mike Snitzer
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=4411521518781080@web43j.yandex.ru \
--to=insane79@yandex.ru \
--cc=agk@redhat.com \
--cc=andmike@linux.vnet.ibm.com \
--cc=asi@seznam.cz \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jbrassow@redhat.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=snitzer@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