From: Sami Kerola <kerolasa@iki.fi>
To: zhenwei pi <pizhenwei@bytedance.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: [Phishing Risk] [External] irqtop todo note
Date: Sat, 8 Feb 2020 17:25:29 +0000 [thread overview]
Message-ID: <CAG27Bk0vNs+3s6FM2k44p2N+xkZYD1aL-R6Th8m9+-nZOaMMSg@mail.gmail.com> (raw)
In-Reply-To: <69b8ca4c-aa39-0c8f-1c48-e9ef514f55d8@bytedance.com>
On Thu, 6 Feb 2020 at 01:23, zhenwei pi <pizhenwei@bytedance.com> wrote:
> Hey, I notice that v2.35 has been released. How about continuing this work?
Yes, that's the plan: https://github.com/karelzak/util-linux/pull/952
--
Sami Kerola
http://www.iki.fi/kerolasa/
prev parent reply other threads:[~2020-02-08 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 10:20 irqtop todo note Sami Kerola
[not found] ` <3e1bf9df-b530-738b-fc7f-00e4cf144420@bytedance.com>
2020-01-06 10:52 ` [Phishing Risk] [External] " Karel Zak
2020-02-06 1:20 ` zhenwei pi
2020-02-08 17:25 ` Sami Kerola [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=CAG27Bk0vNs+3s6FM2k44p2N+xkZYD1aL-R6Th8m9+-nZOaMMSg@mail.gmail.com \
--to=kerolasa@iki.fi \
--cc=kerolasa@gmail.com \
--cc=kzak@redhat.com \
--cc=pizhenwei@bytedance.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).