From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 2/2] nvme: Make indentation consistent
Date: Mon, 20 Jun 2016 09:40:18 +0300 [thread overview]
Message-ID: <57678FD2.7010109@grimberg.me> (raw)
In-Reply-To: <1ddfff0b-7047-9710-1779-80721d990b45@sandisk.com>
Looks good,
Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
next prev parent reply other threads:[~2016-06-20 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 6:11 [PATCH 0/2] Address issues reported by static checkers Bart Van Assche
2016-06-20 6:12 ` [PATCH 1/2] nvme: Remove set-but-not-used variables Bart Van Assche
2016-06-20 6:39 ` Sagi Grimberg
2016-06-20 6:13 ` [PATCH 2/2] nvme: Make indentation consistent Bart Van Assche
2016-06-20 6:40 ` Sagi Grimberg [this message]
2016-06-20 15:06 ` [PATCH 0/2] Address issues reported by static checkers Keith Busch
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=57678FD2.7010109@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;
as well as URLs for NNTP newsgroup(s).