From: Karel Zak <kzak@redhat.com>
To: Sumanth Korikkar <sumanthk@linux.ibm.com>
Cc: util-linux@vger.kernel.org, heiko.carstens@de.ibm.com,
tmricht@linux.ibm.com, svens@linux.ibm.com
Subject: Re: [PATCH] lscpu: Add shared cached info for s390 lscpu -C
Date: Mon, 8 Jun 2020 09:55:55 +0200 [thread overview]
Message-ID: <20200608075555.vidolanraeu5qndh@ws.net.home> (raw)
In-Reply-To: <20200605161510.17641-1-sumanthk@linux.ibm.com>
On Fri, Jun 05, 2020 at 06:15:10PM +0200, Sumanth Korikkar wrote:
> sys-utils/lscpu.c | 169 +++++++++++++++++++++++++++-------------------
> 1 file changed, 101 insertions(+), 68 deletions(-)
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2020-06-08 7:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 16:15 [PATCH] lscpu: Add shared cached info for s390 lscpu -C Sumanth Korikkar
2020-06-08 7:55 ` 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=20200608075555.vidolanraeu5qndh@ws.net.home \
--to=kzak@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tmricht@linux.ibm.com \
--cc=util-linux@vger.kernel.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).