public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: devel@driverdev.osuosl.org, outreachy-kernel@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] staging: rtl8192e: Removed unnecessary parentheses
Date: Sat, 25 Feb 2017 08:52:07 +0100	[thread overview]
Message-ID: <20170225075207.GA1614@kroah.com> (raw)
In-Reply-To: <CALrZqyPpeCm1zj3aqAhAQXe3Q=TouHdFv7qY_4ijNNDBzqJZNA@mail.gmail.com>

On Sat, Feb 25, 2017 at 04:18:27AM +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.

Please do not do that.  Would you like to receive patches out of order,
not threaded, and all mixed up in the middle of hundreds of other
patches?  How would you be able to figure it out?  Please consider that
someone has to read what you send out :)

>  So, please suggest me some better way, considering I am using mutt.

You can use mutt for that, but you need to know what you are doing and
how to thread emails with it.  It's not simple, so please just use git
send-email for now until you learn mutt better.

good luck!

greg k-h

      parent reply	other threads:[~2017-02-25  7:54 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
2017-02-25  7:52     ` Greg KH [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=20170225075207.GA1614@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.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