From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH v2 0/2] align to generic ib_event logging helper
Date: Tue, 22 Nov 2016 08:23:16 -0800 [thread overview]
Message-ID: <1479831796.18270.3.camel@linux.intel.com> (raw)
In-Reply-To: <1479825391-10389-1-git-send-email-maxg@mellanox.com>
On Tue, 2016-11-22@16:36 +0200, Max Gurtovoy wrote:
> Changes since V1:
> ? - updated debug level to pr_debug
>
> Max Gurtovoy (2):
> ? nvmet-rdma: align to generic ib_event logging helper
> ? nvme-rdma: align to generic ib_event logging helper
>
> ?drivers/nvme/host/rdma.c???|????4 +++-
> ?drivers/nvme/target/rdma.c |????4 +++-
> ?2 files changed, 6 insertions(+), 2 deletions(-)
Seems fine but I'm curious why the extra debugging is needed to the
point it warrants a change to the Linux kernel? ?Why does the default
print case need to be moved such that there will be a debug message
printed for each event instead of the unmatched default event?
>
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2016-11-22 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 14:36 [PATCH v2 0/2] align to generic ib_event logging helper Max Gurtovoy
2016-11-22 14:36 ` [PATCH v2 1/2] nvmet-rdma: " Max Gurtovoy
2016-11-25 7:47 ` Christoph Hellwig
2016-11-22 14:36 ` [PATCH v2 2/2] nvme-rdma: " Max Gurtovoy
2016-11-22 14:43 ` Max Gurtovoy
2016-11-25 7:47 ` Christoph Hellwig
2016-11-22 16:23 ` J Freyensee [this message]
2016-11-23 9:28 ` [PATCH v2 0/2] " Max Gurtovoy
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=1479831796.18270.3.camel@linux.intel.com \
--to=james_p_freyensee@linux.intel.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 NNTP newsgroup(s).