From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Should we get cpufreq@vger.kernel.org removed?
Date: Mon, 21 Apr 2014 20:52:30 +0200 [thread overview]
Message-ID: <1987233.unFhPF8rNJ@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpomWwGJA0wyao-7i19Q_63ThRZ4vpVxnToCHU3zpUi3ioA@mail.gmail.com>
On Monday, April 21, 2014 11:07:00 AM Viresh Kumar wrote:
> We always want people to use: linux-pm@vger.kernel.org for
> any cpufreq work. And sometimes people just send mails to
> cpufreq@vger.kernel.org, as MAINTAINERS file tells them to.
>
> Should we get the cpufreq mailing list removed physically and
> from MAINTAINERS file to make life simple?
We'd need to remove it from MAINTAINERS first and please feel free to
send a patch for this purpose.
Rafael
prev parent reply other threads:[~2014-04-21 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 5:37 Should we get cpufreq@vger.kernel.org removed? Viresh Kumar
2014-04-21 18:52 ` Rafael J. Wysocki [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=1987233.unFhPF8rNJ@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=cpufreq@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).