Util-Linux Archive on lore.kernel.org
 help / color / Atom feed
From: zhenwei pi <pizhenwei@bytedance.com>
To: Karel Zak <kzak@redhat.com>, kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [Phishing Risk] [External] irqtop todo note
Date: Thu, 6 Feb 2020 09:20:53 +0800
Message-ID: <69b8ca4c-aa39-0c8f-1c48-e9ef514f55d8@bytedance.com> (raw)
In-Reply-To: <20200106105256.3phh5bdgs4qgqzpp@10.255.255.10>

On 1/6/20 6:52 PM, Karel Zak wrote:
> On Sun, Jan 05, 2020 at 11:36:26AM +0800, zhenwei pi wrote:
>> On 1/4/20 6:20 PM, Sami Kerola wrote:
>>
>>> Hello,
>>>
>>> I notice irqtop to todo file, so I decided to look into that. Changes
>>> in my branch are nowhere near ready to be considered to upstream
>>> ready, so no pull request yet maybe sometime later January or early
>>> February. Meanwhile if someone else is working with the same I'm sure
>>> efforts can be combined.
>>>
>>> https://github.com/kerolasa/util-linux/commits/irqtop
>>>
>>> Things to fix with my work.
>>>
>>> * Save git history from https://github.com/pacepi/irqtop
>>> * Write proper commit messages
>>> * Use smartcolums
>>> * Change output header to include hostname and iso timestamp
>>> * Use signalfd to catch signals
>>> * Use timerfd  for periodic execution
>>> * Make main() shorter / simpler by moving bits and bobs to functions
>>> * And the things I don't know yet, but without doubt there will be some
>>>
>> Thanks for these works. Maybe it's ready to be merged into upstream.
>> Hey, Karel, how do you think about this?
> 
> Later, for v2.35 is too late ;-)
> 
>      Karel
> 

Hey, I notice that v2.35 has been released. How about continuing this work?

-- 
zhenwei pi

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04 10:20 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 [this message]
2020-02-08 17:25       ` Sami Kerola

Reply instructions:

You may reply publically 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=69b8ca4c-aa39-0c8f-1c48-e9ef514f55d8@bytedance.com \
    --to=pizhenwei@bytedance.com \
    --cc=kerolasa@gmail.com \
    --cc=kzak@redhat.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

Util-Linux Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/util-linux/0 util-linux/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 util-linux util-linux/ https://lore.kernel.org/util-linux \
		util-linux@vger.kernel.org
	public-inbox-index util-linux

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.util-linux


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git