From: Christoph Hellwig <hch@lst.de>
To: Rohit Chavan <roheetchavan@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmet: Fix warnings given by checkpatch
Date: Wed, 18 Sep 2024 14:03:51 +0200 [thread overview]
Message-ID: <20240918120351.GA20881@lst.de> (raw)
In-Reply-To: <20240918081134.908075-1-roheetchavan@gmail.com>
Please don't waste peoples time by sending checkpatch cleanups.
Good coding style is nice to have, but unless you do actualy substantial
work in the area that has issues it's just churn that creates work.
prev parent reply other threads:[~2024-09-18 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 8:11 [PATCH] nvmet: Fix warnings given by checkpatch Rohit Chavan
2024-09-18 12:03 ` Christoph Hellwig [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=20240918120351.GA20881@lst.de \
--to=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=roheetchavan@gmail.com \
--cc=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