All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-block@vger.kernel.org
Cc: osandov@osandov.com, bvanassche@acm.org,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Subject: [PATCH 0/8] nvme: misc cleanups
Date: Tue, 19 Feb 2019 15:28:17 -0800	[thread overview]
Message-ID: <1550618905-4112-1-git-send-email-chaitanya.kulkarni@wdc.com> (raw)

Hi Omar,
   
   This is a small patch series which follows the blktests codingi
   style format as pointed out by Bart. Also minimizes the overall
   code for the review.

-Regards,
Chaitanya


Chaitanya Kulkarni (8):
  nvme/021: use consistent coding style
  nvme/022: use consistent coding style
  nvme/023: use consistent coding style
  nvme/024: use consistent coding style
  nvme/025: use consistent coding style
  nvme/026: use consistent coding style
  nvme/027: use consistent coding style
  nvme/028: use consistent coding style

 tests/nvme/021     | 15 ++++++---------
 tests/nvme/021.out |  1 -
 tests/nvme/022     | 16 ++++++----------
 tests/nvme/022.out |  1 -
 tests/nvme/023     | 16 ++++++----------
 tests/nvme/023.out |  1 -
 tests/nvme/024     | 16 ++++++----------
 tests/nvme/024.out |  1 -
 tests/nvme/025     | 16 ++++++----------
 tests/nvme/025.out |  1 -
 tests/nvme/026     | 16 ++++++----------
 tests/nvme/026.out |  1 -
 tests/nvme/027     | 16 ++++++----------
 tests/nvme/027.out |  1 -
 tests/nvme/028     | 17 ++++++-----------
 tests/nvme/028.out |  1 -
 16 files changed, 48 insertions(+), 88 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-02-19 23:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 23:28 Chaitanya Kulkarni [this message]
2019-02-19 23:28 ` [PATCH 1/8] nvme/021: use consistent coding style Chaitanya Kulkarni
2019-02-20 18:10   ` Omar Sandoval
2019-02-20 18:19     ` Chaitanya Kulkarni
2019-02-20 18:23       ` Omar Sandoval
2019-02-19 23:28 ` [PATCH 2/8] nvme/022: " Chaitanya Kulkarni
2019-02-19 23:28 ` [PATCH 3/8] nvme/023: " Chaitanya Kulkarni
2019-02-19 23:28 ` [PATCH 4/8] nvme/024: " Chaitanya Kulkarni
2019-02-19 23:28 ` [PATCH 5/8] nvme/025: " Chaitanya Kulkarni
2019-02-19 23:28 ` [PATCH 6/8] nvme/026: " Chaitanya Kulkarni
2019-02-19 23:28 ` [PATCH 7/8] nvme/027: " Chaitanya Kulkarni
2019-02-19 23:28 ` [PATCH 8/8] nvme/028: " Chaitanya Kulkarni

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=1550618905-4112-1-git-send-email-chaitanya.kulkarni@wdc.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@osandov.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.