cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: cpufreq@vger.kernel.org
Cc: postmaster@vger.kernel.org
Subject: RFC: sunsetting the cpufreq list
Date: Wed, 18 Oct 2023 12:40:43 -0400	[thread overview]
Message-ID: <20231018-lunchroom-sierra-a85b06@meerkat> (raw)

Hello, all:

We are currently in the process of migrating vger lists to new infrastructure,
and it seems like a good time to evaluate if it is a good time to sunset some
of the less active lists.

The cpufreq list is archived on https://lore.kernel.org/cpufreq/ and it
appears to be mostly inactive since 2015. It appears that the preferred list
for cpufreq discussions and patches is the linux-pm list.

I recommend that we close this list with a bounce message going out to anyone
attempting to post to it that they should send their messages to
linux-pm@vger.kernel.org instead.

Are there any objections to this plan?

Best regards,
Konstantin

                 reply	other threads:[~2023-10-18 16:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231018-lunchroom-sierra-a85b06@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=postmaster@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
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).