ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
Subject: [Ksummit-discuss] Maintainer's / Kernel Summit 2022 CFP
Date: Fri, 17 Jun 2022 10:40:47 +0200	[thread overview]
Message-ID: <da1a3fdf-70d0-90db-3a8a-7cb0fcbdb37b@redhat.com> (raw)
In-Reply-To: <CAL_JsqLz6b_r_d96C=Q21exqq8TQg1G5GkW6ttiEUTUZ+QYBJA@mail.gmail.com>


On 6/16/22 22:54, Rob Herring wrote:
> On Tue, Jun 14, 2022 at 10:25 PM Theodore Ts'o <tytso@mit.edu> wrote:
>> This year, the Maintainer's Summit will be held in Dublin on September
>> 15th, 2022, just after the Linux Plumber's Conference (September
>> 12-14).
>> As in previous years, the Maintainers Summit is invite-only, where the
>> primary focus will be process issues around Linux Kernel Development.
>> It will be limited to 30 invitees and a handful of sponsored
>> attendees.
>> Linus will be generating a core list of people to be invited to the
>> Maintainers Summit.  The top ten people from that list will receive
>> invites, and then program committee will use the rest of Linus's list
>> as a starting point of people to be considered.  People who suggest
>> topics that should be discussed at the Maintainers Summit will also
>> be added to the list for consideration.  To make topic suggestions for
>> the Maintainers Summit, please send e-mail to the
>> ksummit-discuss@lists.linuxfoundation.org list with a subject prefix
> Last year we moved to ksummit@lists.linux.dev. Did we move back?
> There's posts to both lists now.

Right, I send my "[TECH TOPIC] New userspace API for display-panel
brightness control" email to ksummit@lists.linux.dev because that
is specified as the list to use at:


under "Kernel Summit Presentation Proposals" this says:

"also send an e-mail for each submission to the ksummit@lists.linux.dev
mailing list with the subject prefix [TECH TOPIC]."

I would be happy to resend it to ksummit-discuss@lists.linuxfoundation.org,
as I later noticed was mentioned in the CFP email, but I'm waiting
for clarification which one is the list to use.



  reply	other threads:[~2022-06-17  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  4:25 [Ksummit-discuss] Maintainer's / Kernel Summit 2022 CFP Theodore Ts'o
2022-06-16 20:54 ` Rob Herring
2022-06-17  8:40   ` Hans de Goede [this message]
2022-06-17 12:17   ` Konstantin Ryabitsev

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=da1a3fdf-70d0-90db-3a8a-7cb0fcbdb37b@redhat.com \
    --to=hdegoede@redhat.com \


* 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 NNTP newsgroup(s).