From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Benjamin Young <youngcdev@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: goldfish: Coding Style Fix Comparison to NULL could
Date: Fri, 11 Dec 2015 12:14:17 +0530 [thread overview]
Message-ID: <20151211064417.GB4763@sudip-pc> (raw)
In-Reply-To: <20151210233109.GA3532@arc008b.sc.wdc.com>
On Thu, Dec 10, 2015 at 06:31:09PM -0500, Benjamin Young wrote:
> From 4b8ce6b3bd7effdfff2c95fbeb4a20cb93d5e9e5 Mon Sep 17 00:00:00 2001
> From: Benjamin Young <youngcdev@gmail.com>
> Date: Thu, 10 Dec 2015 17:31:00 -0500
> Subject: [PATCH] staging: goldfish: Coding Style Fix - spaces preferred around
> that '+'
Regarding all the three patches: The above header information should not
be here.
Regarding this patch: This is a repeat of the previous patch with the
subject of the next patch.
regards
sudip
next prev parent reply other threads:[~2015-12-11 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 23:31 Benjamin Young
2015-12-11 6:44 ` Sudip Mukherjee [this message]
2015-12-11 20:24 ` Benjamin Young
2015-12-10 23:31 Benjamin Young
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=20151211064417.GB4763@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=youngcdev@gmail.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