public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v2 6/6] staging: rtl8192e: Removed unnecessary parentheses
Date: Fri, 24 Feb 2017 18:53:08 -0800	[thread overview]
Message-ID: <1487991188.14159.56.camel@perches.com> (raw)
In-Reply-To: <CALrZqyPpeCm1zj3aqAhAQXe3Q=TouHdFv7qY_4ijNNDBzqJZNA@mail.gmail.com>

On Sat, 2017-02-25 at 04:18 +0530, SIMRAN SINGHAL wrote:
> On Fri, Feb 24, 2017 at 10:47 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Feb 20, 2017 at 10:41:47PM +0530, simran singhal wrote:
> > > Extra parentheses were causing checkpatch issues
> > > and were removed.
> > > 
> > > Signed-off-by: simran singhal <singhalsimran0@gmail.com>
> > > ---
> > > 
> > >  v2:
> > >    -Removed parentheses around argument of cast
> > >    -Removed cast
> > 
> > I can't keep track of random patches in the middle of a series that is
> > updated.
> > 
> > Please fix up and resend the whole series, as a series, that are linked
> > together in an email client, not as independent emails (i.e. use
> > git-send-email properly).
> 
>  I am using mutt for sending patches. In mutt I have to send each patch
>  of a particular patch series one by one. So, they come as independent
>  emails.
> 
>  And, they all get mix because of the reason, if I started sending new patch
>  series and at the same time sending new versions of patches of previous
>  patch series, so because of which their order changes.
> 
>  So, please suggest me some better way, considering I am using mutt.

git send-email

  reply	other threads:[~2017-02-25  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 17:11 [PATCH v2 6/6] staging: rtl8192e: Removed unnecessary parentheses simran singhal
2017-02-24 17:17 ` Greg KH
2017-02-24 22:48   ` SIMRAN SINGHAL
2017-02-25  2:53     ` Joe Perches [this message]
2017-02-25  7:52     ` Greg KH

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=1487991188.14159.56.camel@perches.com \
    --to=joe@perches.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=singhalsimran0@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