All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] netatop: new package
Date: Sat, 08 Oct 2016 18:58:41 -0300	[thread overview]
Message-ID: <57f96c11c505c_78bc3fbbfa97ee242476d@ultri3.mail> (raw)
In-Reply-To: 20161007231920.2a4050e6@free-electrons.com

Thomas,

On Fri, Oct 07, 2016 at 06:19 PM, Thomas Petazzoni wrote:
[snip]
> In addition to the kernel module, netatop also builds a daemon,
> netatopd, which gets started by the init script if available. But
> your .mk file does not seem to build the netatopd daemon. Why so?

Short answer ... for no good reason.

While I was creating the patch series I decided to send a small patch.
But I removed too much.
atop and netatop module work without this daemon. But it adds the functionality
of tracking counters of exited processes.

I will add the daemon to the .mk file when I resend.

Thank you for your review.

Regards,
Ricardo

  reply	other threads:[~2016-10-08 21:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 20:30 [Buildroot] [PATCH 1/4] atop: new package Ricardo Martincoski
2016-10-07 20:30 ` [Buildroot] [PATCH 2/4] netatop: " Ricardo Martincoski
2016-10-07 21:19   ` Thomas Petazzoni
2016-10-08 21:58     ` Ricardo Martincoski [this message]
2016-10-07 20:30 ` [Buildroot] [PATCH 3/4] netatop: enable required kernel feature Ricardo Martincoski
2016-10-07 21:20   ` Thomas Petazzoni
2016-10-08 20:45     ` Ricardo Martincoski
2016-10-07 20:30 ` [Buildroot] [PATCH 4/4] DEVELOPERS: list {, net}atop package under my name Ricardo Martincoski
2016-10-07 21:21   ` Thomas Petazzoni
2016-10-07 21:18 ` [Buildroot] [PATCH 1/4] atop: new package Thomas Petazzoni

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=57f96c11c505c_78bc3fbbfa97ee242476d@ultri3.mail \
    --to=ricardo.martincoski@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.