From: Jens Axboe <axboe@kernel.dk>
To: Akhil Bhansali <Akhil.Bhansali@hgst.com>
Cc: OS Engineering <osengineering@stec-inc.com>,
Ramprasad Chinthekindi <Ramprasad.Chinthekindi@hgst.com>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"'linux kernel (linux-kernel@vger.kernel.org)'"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] skd: Fix checkpatch ERRORS and removed unused functions.
Date: Wed, 23 Oct 2013 13:02:32 +0100 [thread overview]
Message-ID: <20131023120232.GB14598@kernel.dk> (raw)
In-Reply-To: <87B0A48E21A1974AB4780BA3191524C210E71E@MYMBX3.stec-inc.ad>
On Wed, Oct 23 2013, Akhil Bhansali wrote:
> From dcd25c7128e14c90abb6a5d61e0a9ae9b26b6904 Mon Sep 17 00:00:00 2001
> From: Akhil Bhansali <bhansaliakhil@gmail.com>
> Date: Wed, 23 Oct 2013 14:45:34 +0530
> Subject: [PATCH] [PATCH] Fix checkpatch ERRORS and removed unused functions.
In the future, please ensure that patches are sanity cleaned. There's a
double [PATCH] in that subject, and you should prefix the first line
with the driver/area being modified.
I committed it as:
skd: Fix checkpatch ERRORS and removed unused functions.
> This patch fixes checkpatch.pl errors for assignment in if condition.
> It also removes unused readq / readl function calls.
>
> As Andrew had disabled the compilation of drivers for 32 bit,
> I have modified format specifiers in few VPRINTKs to avoid warnings
> during 64 bit compilation.
> Signed-off-by: Akhil Bhansali <abhansali@stec-inc.com>
> Reviewed-by: Ramprasad Chinthekindi <rchinthekindi@stec-inc.com>
Leave a line between the commit message and the signed-off/reviewed
lines.
> PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED
>
> This electronic transmission, and any documents attached hereto, may
> contain confidential, proprietary and/or legally privileged
> information. The information is intended only for use by the recipient
> named above. If you received this electronic message in error, please
> notify the sender and delete the electronic message. Any disclosure,
> copying, distribution, or use of the contents of information received
> in error is strictly prohibited, and violators will be pursued
> legally.
And you might want to look into getting rid of this if possible, you are
posting to public lists...
--
Jens Axboe
prev parent reply other threads:[~2013-10-23 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 11:51 Akhil Bhansali
2013-10-23 12:02 ` 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=20131023120232.GB14598@kernel.dk \
--to=axboe@kernel.dk \
--cc=Akhil.Bhansali@hgst.com \
--cc=Ramprasad.Chinthekindi@hgst.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osengineering@stec-inc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome