From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Currently working on new intel-microcode package version...
Date: Wed, 13 Nov 2019 17:57:00 +0000 [thread overview]
Message-ID: <1bd3715b-e3c3-4370-d6f5-1623b125e139@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Hello *,
there were some rumors about new CPU vulnerabilites affecting Intel
processors coming up since a few days. Since the security advisory
was published today, I am currently working on a package update of
intel-microcode and will hand in a patch as soon this is done.
Just for your information, so we do not do things twice.
By the way: Did I mention I stared to hate Intel?
Thanks, and best regards,
Peter Müller
next reply other threads:[~2019-11-13 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 17:57 Peter Müller [this message]
2019-11-13 19:18 ` [PATCH] intel-microcode: update to 20191112 Peter Müller
2019-11-14 12:24 ` Michael Tremer
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=1bd3715b-e3c3-4370-d6f5-1623b125e139@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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