All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Soumyajit Deb <debsoumyajit100@gmail.com>
Cc: outreachy-kernel@googlegroups.com, perex@perex.cz
Subject: Re: [PATCH 0/3] Resolve indentation and space warnings generated by checkpatch
Date: Mon, 23 Mar 2020 11:36:52 +0100	[thread overview]
Message-ID: <20200323103652.GC452208@kroah.com> (raw)
In-Reply-To: <20200323054836.48816-1-debsoumyajit100@gmail.com>

On Mon, Mar 23, 2020 at 11:18:33AM +0530, Soumyajit Deb wrote:
> This patchset adds space around operators and remove space after * in
> pointer declarations and lastly removes uneccesary blank lines for the
> same from the file hp100.c present under drivers/staging/hp/ directory.
> 
> Soumyajit Deb (3):
>   staging: hp100: Add space around operator +
>   staging: hp100: Remove space after * in pointer declarations
>   staging: hp100: Remove uneccessary blank lines and resolve indentation
>     issues
> 

I somehow don't see patch 1/3 here, did it get lost somewhere?

Also, be sure your subject line of the 0/3 matches the other patches
(you forgot "staging" and the driver name...)

thanks,

greg k-h


  parent reply	other threads:[~2020-03-23 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23  5:48 [PATCH 0/3] Resolve indentation and space warnings generated by checkpatch Soumyajit Deb
2020-03-23  5:48 ` [PATCH 1/3] staging: hp100: Add space around operator + Soumyajit Deb
2020-03-23  5:48 ` [PATCH 2/3] staging: hp100: Remove space after * in pointer declarations Soumyajit Deb
2020-03-23  5:48 ` [PATCH 3/3] staging: hp100: Remove uneccessary blank lines and resolve indentation issues Soumyajit Deb
2020-03-23 10:37   ` Greg KH
2020-03-23 10:36 ` Greg KH [this message]
2020-03-23 11:23   ` [PATCH 0/3] Resolve indentation and space warnings generated by checkpatch Greg KH
2020-03-23 11:27     ` Soumyajit Deb

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=20200323103652.GC452208@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=debsoumyajit100@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=perex@perex.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.