From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 138 (testing) report
Date: Sun, 17 Nov 2019 21:41:00 +0000 [thread overview]
Message-ID: <655ace54-a07f-adb3-a1b1-def5cf527f91@ipfire.org> (raw)
In-Reply-To: <c918fb3cf3c32cd8360633f0f7d84632@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
Hello Arne,
thanks for your quick reply.
I am still puzzled by the output of "grep microcode /var/log/bootlog". Does yours
differ from mine, especially when it comes to the microcode release date?
Thanks, and best regards,
Peter Müller
next prev parent reply other threads:[~2019-11-17 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 18:15 Peter Müller
2019-11-17 21:29 ` Arne Fitzenreiter
2019-11-17 21:41 ` Peter Müller [this message]
2019-11-18 8:24 ` Arne Fitzenreiter
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=655ace54-a07f-adb3-a1b1-def5cf527f91@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