mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Rajan Vaja <rajan.vaja@gmail.com>
Cc: carlos@cgarcia.org, mahfouz.saif.elyazal@gmail.com,
	rodriguez.twister@gmail.com, peter@hurleysoftware.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fwserial: Fix coding style problems
Date: Mon, 30 Nov 2015 07:16:01 -0800	[thread overview]
Message-ID: <20151130151601.GA28140@kroah.com> (raw)
In-Reply-To: <1448867683-1985-1-git-send-email-rajan.vaja@gmail.com>

On Mon, Nov 30, 2015 at 12:44:43PM +0530, Rajan Vaja wrote:
> Fix below coding style problems reported by checkpatch:
>   - Check for pointer comparisons to NULL
>   - No space after a cast

That's two different things, please break this into two different
patches.

thanks,

greg k-h

      reply	other threads:[~2015-11-30 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30  7:14 Rajan Vaja
2015-11-30 15:16 ` Greg KH [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=20151130151601.GA28140@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=carlos@cgarcia.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahfouz.saif.elyazal@gmail.com \
    --cc=peter@hurleysoftware.com \
    --cc=rajan.vaja@gmail.com \
    --cc=rodriguez.twister@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