From: Ingo Molnar <mingo@kernel.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: mingo@elte.hu, tglx@linutronix.de,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH RESEND] x86: consider effective protection attributes in W+X check
Date: Tue, 20 Feb 2018 11:17:27 +0100 [thread overview]
Message-ID: <20180220101727.c4akak6cgoqbgn2y@gmail.com> (raw)
In-Reply-To: <5A8BEDBE02000078001A9763@prv-mh.provo.novell.com>
* Jan Beulich <JBeulich@suse.com> wrote:
> >>> On 20.02.18 at 09:37, <mingo@kernel.org> wrote:
>
> > * Jan Beulich <JBeulich@suse.com> wrote:
> >
> >> I'll see what I can do; it's a pity that the change here, which had
> >> been sent weeks ago and is a bug fix, hadn't gone in before that
> >> other change (being more an improvement than a bug fix).
> >
> > When was it submitted, got a link or Message-ID of the previous submission?
>
> On Dec 12th (https://patchwork.kernel.org/patch/10106593/).
Indeed! There was a bit of a back and forth in the submission, with v2 and v3
patches sent for the #1 patch, which combined with the whole Meltdown/PTI mess
that was in overdrive during the holliday season just made us miss this...
Next time anything like this happens just ping the original thread and I'll pick
it up. (But a resend is fine too, of course.)
I assume the Xen fix got merged meanwhile?
Thanks,
Ingo
next prev parent reply other threads:[~2018-02-20 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 7:41 Jan Beulich
2018-02-20 8:10 ` Ingo Molnar
2018-02-20 8:22 ` Jan Beulich
2018-02-20 8:32 ` Ingo Molnar
2018-02-20 8:37 ` Ingo Molnar
2018-02-20 8:43 ` Jan Beulich
2018-02-20 10:17 ` Ingo Molnar [this message]
2018-02-20 11:09 ` Jan Beulich
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=20180220101727.c4akak6cgoqbgn2y@gmail.com \
--to=mingo@kernel.org \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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
Powered by JetHome