public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/collectd/
Date: Sun,  3 Apr 2016 18:20:16 +0000 (UTC)	[thread overview]
Message-ID: <1459707603.53fc0fa4f22e1d13a2df6642b6cb7d7876ef0cb3.kensington@gentoo> (raw)

commit:     53fc0fa4f22e1d13a2df6642b6cb7d7876ef0cb3
Author:     Thomas D <whissi <AT> whissi <DOT> de>
AuthorDate: Sat Apr  2 13:14:39 2016 +0000
Commit:     Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Sun Apr  3 18:20:03 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=53fc0fa4

app-admin/collectd: Fix CGROUP kernel config check

Package-Manager: portage-2.2.28

 app-admin/collectd/collectd-5.5.1-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-admin/collectd/collectd-5.5.1-r2.ebuild b/app-admin/collectd/collectd-5.5.1-r2.ebuild
index 971532e..69290da 100644
--- a/app-admin/collectd/collectd-5.5.1-r2.ebuild
+++ b/app-admin/collectd/collectd-5.5.1-r2.ebuild
@@ -195,7 +195,7 @@ collectd_linux_kernel_checks() {
 	collectd_plugin_kernel_linux battery ACPI_BATTERY warn
 
 	# cgroups.c: /sys/fs/cgroup/
-	collectd_plugin_kernel_linux cgroups CONFIG_CGROUPS warn
+	collectd_plugin_kernel_linux cgroups CGROUPS warn
 
 	# cpufreq.c: /sys/devices/system/cpu/cpu%d/cpufreq/
 	collectd_plugin_kernel_linux cpufreq SYSFS warn


             reply	other threads:[~2016-04-03 18:20 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-03 18:20 Michael Palimaka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-04  1:50 [gentoo-commits] repo/gentoo:master commit in: app-admin/collectd/ Thomas Deutschmann
2018-03-30 23:27 Thomas Deutschmann
2018-03-22 11:56 Tobias Klausmann
2018-02-05 21:27 Markus Meier
2018-01-31  7:59 Agostino Sarubbo
2018-01-28 16:36 Thomas Deutschmann
2017-11-07 22:13 Sven Wegener
2017-09-24 15:10 Thomas Deutschmann
2017-08-04  4:29 Markus Meier
2017-06-07 20:16 Thomas Deutschmann
2017-06-05 21:54 Thomas Deutschmann
2017-06-05 21:54 Thomas Deutschmann
2017-06-05 21:54 Thomas Deutschmann
2017-05-09 13:38 Thomas Deutschmann
2017-04-06 15:50 Thomas Deutschmann
2017-04-01 16:06 Agostino Sarubbo
2017-03-20 16:45 Agostino Sarubbo
2017-03-19 21:12 Thomas Deutschmann
2017-01-29 14:12 Thomas Deutschmann
2016-12-08 16:49 Thomas Deutschmann
2016-11-30 15:17 Thomas Deutschmann
2016-11-03 16:19 Göktürk Yüksek
2016-10-11 10:31 Thomas Deutschmann
2016-10-07 15:17 Thomas Deutschmann
2016-09-22  0:10 Thomas Deutschmann
2016-08-10 22:40 Thomas Deutschmann
2016-08-10 20:44 Thomas Deutschmann
2016-08-10 20:44 Thomas Deutschmann
2016-06-11 23:39 Mikle Kolyada
2016-04-26  7:30 Patrice Clement
2016-04-04  9:00 Ian Delaney
2016-04-03 22:36 James Le Cuirot
2016-04-02 15:48 Alexis Ballier
2016-03-31 11:31 Sam Jorna
2016-03-29 19:17 Patrick Lauer
2016-03-24  8:33 Patrick Lauer
2016-03-23 23:41 Ian Delaney
2016-03-02  2:41 Ian Delaney
2016-02-29 21:42 Patrick Lauer
2016-01-05 11:45 Pacho Ramos
2016-01-05 11:45 Pacho Ramos
2016-01-02  6:55 Jason Zaman
2015-09-03  9:00 James Le Cuirot

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=1459707603.53fc0fa4f22e1d13a2df6642b6cb7d7876ef0cb3.kensington@gentoo \
    --to=kensington@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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