From: CMB <CMB@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xen: update to 4.14.1.
Date: Fri, 08 Jan 2021 17:42:44 +0100 [thread overview]
Message-ID: <20210108164244.YrW6wnR50K62R5L-Um7j9mNWRRLI-oZbAI4UrGuOonU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27751@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
New comment by CMB on void-packages repository
https://github.com/void-linux/void-packages/pull/27751#issuecomment-756861668
Comment:
This really deserves a look; 4.14.0 is affected by a number of XSAs
fixed in 4.14.1.
next prev parent reply other threads:[~2021-01-08 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 22:46 [PR PATCH] " CMB
2021-01-08 0:07 ` [PR PATCH] [Updated] " CMB
2021-01-08 16:42 ` CMB [this message]
2021-01-08 17:46 ` [PR REVIEW] " ericonr
2021-01-09 9:43 ` [PR PATCH] [Updated] " CMB
2021-01-09 10:46 ` CMB
2021-01-09 10:47 ` CMB
2021-01-19 20:43 ` [PR PATCH] [Merged]: " ericonr
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=20210108164244.YrW6wnR50K62R5L-Um7j9mNWRRLI-oZbAI4UrGuOonU@z \
--to=cmb@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).