mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Cc: linux-kernel@vger.kernel.org, linux-parport@lists.infradead.org,
	sudip.mukherjee@codethink.co.uk, akpm@linux-foundation.org
Subject: Re: [PATCH 1/5] parport: add newline to trailing statements
Date: Tue, 8 Aug 2017 02:12:37 +0530	[thread overview]
Message-ID: <20170807204237.GA2880@mukherjee.sudip> (raw)
In-Reply-To: <20170717163702.17427-2-palminha@synopsys.com>

Hi,

On Mon, Jul 17, 2017 at 05:36:58PM +0100, Carlos Palminha wrote:
> based on checkpatch, add newline to trailing statements
> 
> Signed-off-by: Carlos Palminha <palminha@synopsys.com>
> ---
>  drivers/parport/daisy.c        |  7 +++++--
>  drivers/parport/ieee1284.c     | 17 +++++++++--------
>  drivers/parport/ieee1284_ops.c |  8 ++++++--
>  drivers/parport/parport_cs.c   |  4 +++-
>  drivers/parport/parport_gsc.c  |  6 ++++--
>  drivers/parport/probe.c        |  4 +++-
>  6 files changed, 30 insertions(+), 16 deletions(-)

<snip>

>  		goto try_again;
>  	success:
>  		parport_frob_control (port, PARPORT_CONTROL_STROBE, 0);
> diff --git a/drivers/parport/parport_cs.c b/drivers/parport/parport_cs.c
> index e9b52e4a4648..993565fef73b 100644
> --- a/drivers/parport/parport_cs.c
> +++ b/drivers/parport/parport_cs.c
> @@ -88,7 +88,9 @@ static int parport_probe(struct pcmcia_device *link)
>  
>      /* Create new parport device */
>      info = kzalloc(sizeof(*info), GFP_KERNEL);
> -    if (!info) return -ENOMEM;
> +    if (!info)
> +        return -ENOMEM;

Please use tab to indent the code. I know some part of this file uses
4 spaces to indent, so if you use one tab before 'return -ENOMEM', it
will look perfect.


--
Regards
Sudip

  reply	other threads:[~2017-08-07 20:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 16:36 [PATCH 0/5] parport: cleanup several checkpatch issues Carlos Palminha
2017-07-17 16:36 ` [PATCH 1/5] parport: add newline to trailing statements Carlos Palminha
2017-08-07 20:42   ` Sudip Mukherjee [this message]
2017-07-17 16:36 ` [PATCH 2/5] parport: cleanup prohibited space after functions name Carlos Palminha
2017-08-07 20:49   ` Sudip Mukherjee
2017-07-17 16:37 ` [PATCH 3/5] parport: cleanup statics initialization to NULL or 0 Carlos Palminha
2017-07-17 16:37 ` [PATCH 4/5] parport: move open braces to the same line Carlos Palminha
2017-07-17 16:40 ` [PATCH 5/5] parport: remove unnecessary braces Carlos Palminha

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=20170807204237.GA2880@mukherjee.sudip \
    --to=sudipm.mukherjee@gmail.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parport@lists.infradead.org \
    --cc=sudip.mukherjee@codethink.co.uk \
    /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

all inboxes | Powered by JetHome®