From: Igor Stoppa <igor.stoppa@gmail.com>
To: "Stecklina, Julian" <jsteckli@amazon.de>,
"tycho@tycho.ws" <tycho@tycho.ws>
Cc: "liran.alon@oracle.com" <liran.alon@oracle.com>,
"jwadams@google.com" <jwadams@google.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [RFC PATCH 0/6] Process-local memory allocations
Date: Fri, 23 Nov 2018 18:24:08 +0200 [thread overview]
Message-ID: <5af3ae36-6e1a-b8f0-c4b6-8a93fb842343@gmail.com> (raw)
In-Reply-To: <1542904826.6344.1.camel@amazon.de>
On 22/11/2018 18:40, Stecklina, Julian wrote:
> On Wed, 2018-11-21 at 10:48 -0700, Tycho Andersen wrote:
>>> Where is the full set of patches?
>>> I'm sorry, I searched both KVM and LKML archives, but I couldn't find it.
>>
>> It looks like they were only sent to kernel hardening, but not sent to
>> the archives? I only see our replies here:
>>
>> https://www.openwall.com/lists/kernel-hardening/
>>
>> Julian, perhaps you can re-send with a CC to lkml as well?
>
> Will do. I messed up the threading, due to git send-email being hostile to me.
> Sorry for the confusion.
If you are not subscribed to the hardening ml, it will neither archive,
nor forward to subscribers your emails.
This very mail you wrote is not archived either.
--
igor
next prev parent reply other threads:[~2018-11-23 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1542722764.git.jsteckli@amazon.de>
2018-11-20 23:26 ` [RFC PATCH 0/6] Process-local memory allocations Tycho Andersen
2018-11-21 17:18 ` Igor Stoppa
2018-11-21 17:48 ` Tycho Andersen
2018-11-21 18:12 ` Igor Stoppa
[not found] ` <1542904826.6344.1.camel@amazon.de>
2018-11-23 16:24 ` Igor Stoppa [this message]
2018-11-23 17:04 ` Solar Designer
2018-11-23 17:23 ` Solar Designer
2018-12-13 14:28 ` Julian Stecklina
2018-12-14 2:09 ` Tycho Andersen
2018-12-19 23:00 ` Igor Stoppa
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=5af3ae36-6e1a-b8f0-c4b6-8a93fb842343@gmail.com \
--to=igor.stoppa@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jsteckli@amazon.de \
--cc=jwadams@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=liran.alon@oracle.com \
--cc=tycho@tycho.ws \
/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).