public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: jitendra kumar khasdev <jkhasdev@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
	devel@driverdev.osuosl.org, pankaj.saraf@nektech.in,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Staging: comedi: fix line over 80 characters warning
Date: Sun, 4 Jan 2015 22:00:45 -0800	[thread overview]
Message-ID: <20150105060045.GA20709@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1501050934180.3526@jitendra>


A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Mon, Jan 05, 2015 at 09:34:57AM +0530, jitendra kumar khasdev wrote:
> Hello,
> Will I have to resubmit by combining all 5 into 1 patch? Please give me 
> suggestion  so that I can do it in correct way.

I don't know, I didn't read the patches, but if you do send a series of
patches, they each have to be doing something different to make them
different patches, right?

thanks,

greg k-h

  reply	other threads:[~2015-01-05  6:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 12:46 [PATCH 1/5] Staging: comedi: fix line over 80 characters warning jitendra kumar khasdev
2015-01-03 12:46 ` [PATCH 2/5] " jitendra kumar khasdev
2015-01-03 12:46 ` [PATCH 3/5] " jitendra kumar khasdev
2015-01-03 12:46 ` [PATCH 4/5] " jitendra kumar khasdev
2015-01-03 12:46 ` [PATCH 5/5] " jitendra kumar khasdev
2015-01-03 13:25 ` [PATCH 1/5] " Sudip Mukherjee
2015-01-04 23:41 ` Greg KH
2015-01-05  4:04   ` jitendra kumar khasdev
2015-01-05  6:00     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-03  8:36 [PATCH 0/5] *** SUBJECT HERE *** jitendra kumar khasdev
2015-01-03  8:36 ` [PATCH 1/5] Staging: comedi: fix line over 80 characters warning jitendra kumar khasdev
2015-01-03 12:20   ` 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=20150105060045.GA20709@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=hsweeten@visionengravers.com \
    --cc=jkhasdev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.saraf@nektech.in \
    /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