From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: "Luruo, Kuthonuzo" <kuthonuzo.luruo@hpe.com>
Cc: "glider@google.com" <glider@google.com>,
"dvyukov@google.com" <dvyukov@google.com>,
"cl@linux.com" <cl@linux.com>,
"penberg@kernel.org" <penberg@kernel.org>,
"rientjes@google.com" <rientjes@google.com>,
"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kasan-dev@googlegroups.com" <kasan-dev@googlegroups.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ynorov@caviumnetworks.com" <ynorov@caviumnetworks.com>
Subject: Re: [PATCH v5 1/2] mm, kasan: improve double-free detection
Date: Wed, 15 Jun 2016 19:38:30 +0300 [thread overview]
Message-ID: <57618486.1060104@virtuozzo.com> (raw)
In-Reply-To: <DF4PR84MB00893B1ADEC50ED3E4891FC6F4540@DF4PR84MB0089.NAMPRD84.PROD.OUTLOOK.COM>
On 06/14/2016 09:46 AM, Luruo, Kuthonuzo wrote:
>>> Next time, when/if you send patch series, send patches in one thread, i.e.
>>> patches should be replies to the cover letter.
>>> Your patches are not linked together, which makes them harder to track.
>
> Thanks for the tip; but doesn't this conflict with the advice in
> https://www.kernel.org/doc/Documentation/SubmittingPatches, specifically the
> use of the "summary phrase"...
>
No, it doesn't. 'summary phrase' is about "Subject:" line. My point is about setting 'In-Reaply-To' which section 15) of SubmittingPatches
For example, this one is good case:
http://thread.gmane.org/gmane.linux.kernel/2244577
All patches are replies to the cover letter, so they are in one thread.
And this is yours:
http://thread.gmane.org/gmane.linux.kernel/2237786
http://thread.gmane.org/gmane.linux.kernel/2237787
prev parent reply other threads:[~2016-06-15 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 18:03 [PATCH v5 1/2] mm, kasan: improve double-free detection Kuthonuzo Luruo
2016-06-09 13:32 ` Alexander Potapenko
2016-06-09 16:54 ` Luruo, Kuthonuzo
2016-06-09 17:00 ` Andrey Ryabinin
2016-06-10 17:03 ` Andrey Ryabinin
2016-06-10 17:09 ` Dmitry Vyukov
2016-06-15 16:18 ` Andrey Ryabinin
2016-06-13 11:56 ` Alexander Potapenko
2016-06-14 6:46 ` Luruo, Kuthonuzo
2016-06-15 16:38 ` Andrey Ryabinin [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=57618486.1060104@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=kuthonuzo.luruo@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=ynorov@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.