From: Francis Laniel <laniel_francis@privacyrequired.com>
To: David Laight <David.Laight@aculab.com>
Cc: 'Andrew Morton' <akpm@linux-foundation.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dja@axtens.net" <dja@axtens.net>,
"keescook@chromium.org" <keescook@chromium.org>
Subject: Re: [PATCH v6 0/5] Fortify strscpy()
Date: Fri, 20 Nov 2020 16:51:41 +0100 [thread overview]
Message-ID: <6074200.xW2bGMXWAE@machine> (raw)
In-Reply-To: <824aad3a91254445b0f30359f1606e2a@AcuMS.aculab.com>
Le vendredi 20 novembre 2020, 14:33:53 CET David Laight a écrit :
> From: Andrew Morton
>
> > Sent: 20 November 2020 01:36
>
> ...
>
> > Could you please send along a reworked [0/n] cover letter? Explain in
> > your own words, without requiring that readers go off and read web
> > pages
> >
> > - What problem the patchset solves
> > - How it solves it
> > - The value of the patchset (to kernel developers or to end-users) so that
> > we>
> > can understand why it should be merged.
>
> - How much it slows things down.
I will add it for the next version!
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1
> 1PT, UK Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-11-20 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201119164915.10618-1-laniel_francis@privacyrequired.com>
2020-11-20 1:35 ` Andrew Morton
2020-11-20 13:33 ` David Laight
2020-11-20 15:51 ` Francis Laniel [this message]
[not found] ` <5676804.6kI0aEeX2c@machine>
2020-11-20 19:52 ` Kees Cook
[not found] ` <20201119164915.10618-2-laniel_francis@privacyrequired.com>
2020-11-20 1:38 ` [PATCH v6 1/5] string.h: detect intra-object overflow in fortified string functions Andrew Morton
2020-11-20 9:41 ` Francis Laniel
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=6074200.xW2bGMXWAE@machine \
--to=laniel_francis@privacyrequired.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=dja@axtens.net \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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