From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/2] nvme-pci: remove whitespace
Date: Mon, 2 Jul 2018 15:07:28 +0200 [thread overview]
Message-ID: <20180702130728.GA4624@lst.de> (raw)
In-Reply-To: <aaa460e43cb43efbfb902d0aa844a1da9ed270dc.1530457943.git.zhangweiping@didichuxing.com>
Please, no whitespace cleanups before critical patches.
Also both styles in this case are acceptable in the kernel. I
personally prefer to not have space, but we really shouldn't spuriously
change it.
next prev parent reply other threads:[~2018-07-02 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 15:20 [PATCH 0/2] release /dev/nvmeX if nvme_probe failed Weiping Zhang
2018-07-01 15:20 ` [PATCH 1/2] nvme-pci: remove whitespace Weiping Zhang
2018-07-02 9:49 ` Sagi Grimberg
2018-07-02 13:07 ` Christoph Hellwig [this message]
2018-07-02 15:45 ` Keith Busch
2018-07-02 16:10 ` Weiping Zhang
2018-07-01 15:20 ` [PATCH 2/2] nvme-pci: release nvme_ctrl if failed to alloc memory in nvme_probe Weiping Zhang
2018-07-02 9:53 ` Sagi Grimberg
2018-07-02 16:13 ` Weiping Zhang
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=20180702130728.GA4624@lst.de \
--to=hch@lst.de \
/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