From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: [PATCH 1/3] MAINTAINERS: Add bug tracking system location entry for cpufreq
Date: Wed, 30 Nov 2016 02:31:02 +0100 [thread overview]
Message-ID: <1749629.bXnquB1jqi@aspire.rjw.lan> (raw)
In-Reply-To: <1768401.hlc2LWNWsP@aspire.rjw.lan>
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
The kernel Bugzilla is used for tracking cpufreq bugs, so document
that.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
Index: linux-pm/MAINTAINERS
===================================================================
--- linux-pm.orig/MAINTAINERS
+++ linux-pm/MAINTAINERS
@@ -3349,6 +3349,7 @@ L: linux-pm@vger.kernel.org
S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
T: git git://git.linaro.org/people/vireshk/linux.git (For ARM Updates)
+B: https://bugzilla.kernel.org
F: Documentation/cpu-freq/
F: drivers/cpufreq/
F: include/linux/cpufreq.h
next prev parent reply other threads:[~2016-11-30 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 1:29 [PATCH 0/3] MAINTAINERS updates for cpufreq and cpuidle Rafael J. Wysocki
2016-11-30 1:31 ` Rafael J. Wysocki [this message]
2016-11-30 3:02 ` [PATCH 1/3] MAINTAINERS: Add bug tracking system location entry for cpufreq Viresh Kumar
2016-11-30 1:32 ` [PATCH 2/3] MAINTAINERS: Add bug tracking system location entries for cpuidle Rafael J. Wysocki
2016-11-30 1:33 ` [PATCH 3/3] MAINTAINERS: Add Jacob Pan as a new intel_idle maintainer Rafael J. Wysocki
2016-12-01 5:58 ` [PATCH 0/3] MAINTAINERS updates for cpufreq and cpuidle Len Brown
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=1749629.bXnquB1jqi@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=daniel.lezcano@linaro.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.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