public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Bogicevic Sasa <brutallesale@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drivers:staging:gdm724x Fill all alignment should match open parentheses
Date: Fri, 30 Oct 2015 15:06:42 +0530	[thread overview]
Message-ID: <20151030093642.GA19993@sudip-pc> (raw)
In-Reply-To: <20151030085919.GA3525@gmail.com>

On Fri, Oct 30, 2015 at 09:59:19AM +0100, Bogicevic Sasa wrote:
> On 10/30/2015, Sudip Mukherjee wrote:
> >On Thu, Oct 29, 2015 at 09:15:01PM +0100, Bogicevic Sasa wrote:
> >>This fixes all errors about alignment with open parentheses as well as
> >>one spacing needed around "-" sign since the patch would not be valid if
> >>I left it there
> >
> >1) That becomes two different type of change.
> >2) This has already been done by
> >a4785ef81023 ("staging: gdm724x: properly indent to match open paranthesis")
> >I think you need to refresh your tree against current staging tree.
> >
> >3) your patch subject says 2/2, the next patch says 3/3 and the one
> >after that is saying 4/4. There is something wrong in the way you are
> >generating the patches. This 2/2 or 3/3 should not be here unless you
> >are sending a series of patch.
> >
> >regards
> >sudip
> Ok 1) When I changed the alignment in one of the lines then
> checkpatch.pl starts complaining about the spaces in the same line so
> what do you do in that situation a) just submit anyway or b) fix it
> I guess a according to your email

It depends on how big that change will be. In this case it was ' '
around '-', although if we go by the books, it should not be allowed,
but one space related change can be overlooked. I wont have commented if
points 2 and 3 were not there.

> 2) I'll see what the hell did I do to not notice this
> 3) I just pull, make a change, commit and do git format-patch
> master..somebranch. Do I need to create separate branches for all
> issues?

No, separate branch should not be necessary. I have only one branch for
staging related work. Did you use -n option while using git format-patch?

regards
sudip

  reply	other threads:[~2015-10-30  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 20:15 [PATCH 2/2] drivers:staging:gdm724x Fill all alignment should match open parentheses Bogicevic Sasa
2015-10-30  7:31 ` Sudip Mukherjee
2015-10-30  8:59   ` Bogicevic Sasa
2015-10-30  9:36     ` Sudip Mukherjee [this message]
2015-10-30 11:48       ` Bogicevic Sasa
2015-10-30 11:55         ` Sudip Mukherjee
2015-10-30 12:05           ` Bogicevic Sasa
2015-10-30 12:12             ` Sudip Mukherjee

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=20151030093642.GA19993@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=brutallesale@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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