From: Karel Zak <kzak@redhat.com>
To: Huang Shijie <shijie@os.amperecomputing.com>
Cc: util-linux@vger.kernel.org, patches@amperecomputing.com,
zwang@amperecomputing.com, mas@amperecomputing.com,
ilkka@os.amperecomputing.com, jeremy.linton@arm.com,
jbastian@redhat.com, m.mizuma@jp.fujitsu.com
Subject: Re: [PATCH 1/2] lscpu: get the processor information by DMI
Date: Wed, 16 Jun 2021 11:17:23 +0200 [thread overview]
Message-ID: <20210616091723.ow5qwzydjt6n5fou@ws.net.home> (raw)
In-Reply-To: <20210615100639.51546-1-shijie@os.amperecomputing.com>
On Tue, Jun 15, 2021 at 10:06:38AM +0000, Huang Shijie wrote:
> sys-utils/lscpu-arm.c | 2 ++
> sys-utils/lscpu-dmi.c | 39 +++++++++++++++++++++++++++++++++++++++
> sys-utils/lscpu.h | 7 +++++++
> 3 files changed, 48 insertions(+)
Applied (both patches), thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2021-06-16 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:06 [PATCH 1/2] lscpu: get the processor information by DMI Huang Shijie
2021-06-15 10:06 ` [RFC PATCH 2/2] lscpu: add bios_family Huang Shijie
2021-06-16 9:17 ` Karel Zak [this message]
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=20210616091723.ow5qwzydjt6n5fou@ws.net.home \
--to=kzak@redhat.com \
--cc=ilkka@os.amperecomputing.com \
--cc=jbastian@redhat.com \
--cc=jeremy.linton@arm.com \
--cc=m.mizuma@jp.fujitsu.com \
--cc=mas@amperecomputing.com \
--cc=patches@amperecomputing.com \
--cc=shijie@os.amperecomputing.com \
--cc=util-linux@vger.kernel.org \
--cc=zwang@amperecomputing.com \
/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).