From: Jens Axboe <axboe@kernel.dk>
To: Kitone Elvis Peter <elviskitone@gmail.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: REMOVE CODING STYLE WARNING
Date: Tue, 19 Jun 2018 13:34:00 -0600 [thread overview]
Message-ID: <0b851687-0663-69b0-6c37-305cabc0b543@kernel.dk> (raw)
In-Reply-To: <20180619142738.GA12449@kitone-HP-ProBook-4530s>
On 6/19/18 8:27 AM, Kitone Elvis Peter wrote:
> Added a license identifier for this file to remove the malformed
> license warning. This will specify which license the file is
> using.
This is the third (and last) time I'll explain this. Go read
Documentation/process/submitting-patches.rst
and format your patches properly.
--
Jens Axboe
prev parent reply other threads:[~2018-06-19 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 14:27 REMOVE CODING STYLE WARNING Kitone Elvis Peter
2018-06-19 19:34 ` Jens Axboe [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=0b851687-0663-69b0-6c37-305cabc0b543@kernel.dk \
--to=axboe@kernel.dk \
--cc=elviskitone@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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