mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: NeilBrown <neil@brown.name>
To: Sankalp Negi <sankalpnegi2310@gmail.com>, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	sankalpnegi2310@gmail.com
Subject: Re: [PATCH v3 0/5] staging: mt7621-spi: Fix C Coding style issues.
Date: Mon, 04 Jun 2018 10:18:32 +1000	[thread overview]
Message-ID: <874lijqu93.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20180602183731.12395-1-sankalpnegi2310@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

On Sun, Jun 03 2018, Sankalp Negi wrote:

> This patch series lists different changes for coding style fixes
> as reported by checkpatch.pl, changes can be broken down as :
>
> 1. Indent switch and case labels at the same level.
> 2. Fix a line over 80 columns by refactoring.
> 3. Use tabs for indentation instead of spaces.
> 4. Add a space before open paranthesis in switch.
> 5. Remove unnecessary braces {} from single statement if block.
>
> version 2 changes
> - segregated changes in individual commits as per fix category.
>
> version 3 changes
> - added unique subjects for each patch in the series.
>
>
> Sankalp Negi (5):
>   staging: mt7621-spi: Indent case labels and switch at the same level.
>   staging: mt7621-spi: Fix line over 80 characters by refactoring.
>   staging: mt7621-spi: Use tabs for indentation instead of spaces.
>   staging: mt7621-spi: Add a space before open paranthesis.
>   staging: mt7621-spi: Remove unnecessary braces {} from single
>     statement if block.
>

Thanks,
All
  Reviewed-by: NeilBrown <neil@brown.name>

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      parent reply	other threads:[~2018-06-04  0:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 18:55 [PATCH] staging: mt7621-spi: Fix Coding style issues reported by checkpatch.pl Sankalp Negi
2018-05-31 21:03 ` NeilBrown
2018-05-31 22:14 ` Joe Perches
2018-06-01  9:15 ` Greg Kroah-Hartman
2018-06-02 14:26   ` [PATCH v2 0/5] staging: mt7621-spi: Fix Coding style issues Sankalp Negi
2018-06-02 14:26     ` [PATCH v2 1/5] staging: mt7621-spi: Fix Coding style issues reported by checkpatch.pl Sankalp Negi
2018-06-02 14:26     ` [PATCH v2 2/5] " Sankalp Negi
2018-06-02 14:26     ` [PATCH v2 3/5] " Sankalp Negi
2018-06-02 14:26     ` [PATCH v2 4/5] " Sankalp Negi
2018-06-02 14:26     ` [PATCH v2 5/5] " Sankalp Negi
2018-06-02 15:27     ` [PATCH v2 0/5] staging: mt7621-spi: Fix Coding style issues Joe Perches
2018-06-02 18:37       ` [PATCH v3 0/5] staging: mt7621-spi: Fix C " Sankalp Negi
2018-06-02 18:37         ` [PATCH v3 1/5] staging: mt7621-spi: Indent case labels and switch at the same level Sankalp Negi
2018-06-02 18:37         ` [PATCH v3 2/5] staging: mt7621-spi: Fix line over 80 characters by refactoring Sankalp Negi
2018-06-02 18:37         ` [PATCH v3 3/5] staging: mt7621-spi: Use tabs for indentation instead of spaces Sankalp Negi
2018-06-02 18:37         ` [PATCH v3 4/5] staging: mt7621-spi: Add a space before open paranthesis Sankalp Negi
2018-06-02 18:37         ` [PATCH v3 5/5] staging: mt7621-spi: Remove unnecessary braces {} from single statement if block Sankalp Negi
2018-06-04  0:18         ` NeilBrown [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=874lijqu93.fsf@notabene.neil.brown.name \
    --to=neil@brown.name \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sankalpnegi2310@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