From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH] nvme/lightnvm: Log using the ctrl named device
Date: Mon, 2 May 2016 12:30:37 +0300 [thread overview]
Message-ID: <57271E3D.5060106@grimberg.me> (raw)
In-Reply-To: <57270A98.70209@bjorling.me>
> Thanks Sagi. I have a couple of patches on top of lightnvm.c that
> conflicts. Will it be okay with you if I carry it through my for-next
> branch that I send to Jens?
Sure, go ahead.
prev parent reply other threads:[~2016-05-02 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 3:25 [PATCH] nvme/lightnvm: Log using the ctrl named device Sagi Grimberg
2016-05-02 8:06 ` Matias Bjørling
2016-05-02 9:30 ` Sagi Grimberg [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=57271E3D.5060106@grimberg.me \
--to=sagi@grimberg.me \
/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