linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Shailendra Verma <shailendra.capricorn@gmail.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 11/11] i2c-core: Fix typo in comment
Date: Tue, 19 May 2015 12:20:25 +0530	[thread overview]
Message-ID: <20150519065025.GA5061@sudip-PC> (raw)
In-Reply-To: <20150519062046.GB4448@schokonusskuchen.bad>

On Tue, May 19, 2015 at 08:20:47AM +0200, Wolfram Sang wrote:
> On Tue, May 19, 2015 at 11:25:08AM +0530, Sudip Mukherjee wrote:
> 
> > You do not need to mention the count of your older patches here.
> 
> While technically true...
> 
> > When you mentioned 11/11, it meant your current submission is a patchset
> > of 11 patches. So when the maintainer decides to apply your patch he will
> > search your remaining 10 patches because he needs to apply them in series.
> 
> ... this doesn't matter much for such cleanup series. They obviously
> have no dependency and I assume that the other patches are for other
> subsystems. This is fine, too.
yes, I also asssumed the same. But it turned out that he has sent 10/10
on 15th May, and then 11/11 , 12/12 , 13/13 and 14/14 on May 18th.

So I assumed that it is a wrong setting while creating his patch.
isn't it?

regards
sudip

  reply	other threads:[~2015-05-19  6:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 16:54 [PATCH 11/11] i2c-core: Fix typo in comment Shailendra Verma
2015-05-19  4:48 ` Sudip Mukherjee
     [not found]   ` <CA+tKcn8exGWjb5Ttr9fMtKhSA_NKf2umZs5JDtC+uTfLKc9fAA@mail.gmail.com>
2015-05-19  5:55     ` Sudip Mukherjee
2015-05-19  6:20       ` Wolfram Sang
2015-05-19  6:50         ` Sudip Mukherjee [this message]
2015-05-31 23:43 ` Wolfram Sang

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=20150519065025.GA5061@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shailendra.capricorn@gmail.com \
    --cc=wsa@the-dreams.de \
    /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;
as well as URLs for NNTP newsgroup(s).