From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D07E4C433ED for ; Thu, 1 Apr 2021 20:11:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9FBF5610D0 for ; Thu, 1 Apr 2021 20:11:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234525AbhDAULh (ORCPT ); Thu, 1 Apr 2021 16:11:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34658 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234287AbhDAULg (ORCPT ); Thu, 1 Apr 2021 16:11:36 -0400 Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1FF70C0613E6 for ; Thu, 1 Apr 2021 13:11:35 -0700 (PDT) Received: by mail-lf1-x132.google.com with SMTP id m12so4599224lfq.10 for ; Thu, 01 Apr 2021 13:11:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GhLRmu0zRkS5+CQv/Ijd32sE0WcWmEsVVfX1YUmswBM=; b=aJWYheXyHFzpwdsO3AGT2syQBJzo6HmwjuuPHoXVGmlF3MVleAbcCVaDoMHZlmg0Yr eY7GX3GfBn7hhCZ2JYe+h8nnUKiLBG7KLpDs/6RpmXHRjWSL7h331bKAIHqmaTfenenp FMGHicTYqPr0q7OQPmOUMAhGkFw3rR9CyRwAf62rn188iWEJoXnSM1wJIH78IJHky7A3 5oj4Oxrvt/Il453uLR5yfLA9hidLux7wCkGJ+YxFZJFKMrBp3E9ilRs8e+xKILlWn+QF ncL3XyK62JeeU7RTY1SWz2vFQcD1irzAPJ+IG/sNOoi2y9EMoQ0NStqgWm0HcEI++so+ CkqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GhLRmu0zRkS5+CQv/Ijd32sE0WcWmEsVVfX1YUmswBM=; b=cx37wWHfgcqtyEWq0wwDhYBgTMU+j4BECZgs2psYNS7v0WRJfsbvJmGGbkeVFzfVw+ /JKtcqAGmZaInhgwplDOwQTvxrUigGIDcx6oiWOjWWQ2/lEnLjTr2QL8oEdSJ/sx2grt nGW9auAzK9lJDq02xoULvYIlmb4V8grtMC80VNiAdN/t3mWxcoQpnScyZzqwG1vH8tzB NMhwyeUYNrvV4SM9ZDPQpB900Y/70t2D7z9teTGENNYm45wiKrCCs1+JpaYeZML4BqIF M7yGBQ2/n/0jsJdX38KXop91dEZAawQ5KLDK4kZYYIRlmEy+QkmMEPBIsATC6D+R8g6+ nqOA== X-Gm-Message-State: AOAM530vcqcv14k6DWbQxg8rAaoFRicl7vdSVRqGnOb950CsANfzyMCa I5FR3z3Pf7fKkrXmmyxEpOiJUY7Dqn4jVuLdXCVOww== X-Google-Smtp-Source: ABdhPJwUbiicLbVWWjJs7FQ4Ff3IInErUKZx0KrdiDCViaz0men4DAkHjTW+cg1RdJ49/cTwqLHd9UkUErMy1Tx6g+c= X-Received: by 2002:a19:5055:: with SMTP id z21mr6464428lfj.297.1617307893432; Thu, 01 Apr 2021 13:11:33 -0700 (PDT) MIME-Version: 1.0 References: <87o8fa3oua.fsf@gnu.org> <403153ed-7953-c42e-40a2-6ad313acd661@oracle.com> <20210401092935.43d3ed54@gandalf.local.home> In-Reply-To: From: Nick Desaulniers Date: Thu, 1 Apr 2021 13:11:21 -0700 Message-ID: Subject: Re: Plumbers CF MCs To: Steven Rostedt Cc: "Jose E. Marchesi" , linux-toolchains@vger.kernel.org, clang-built-linux , Kees Cook , Florian Weimer , Christian Brauner , nick.alcock@oracle.com, Segher Boessenkool , Elena Zannoni Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-toolchains@vger.kernel.org On Thu, Apr 1, 2021 at 6:50 AM Elena Zannoni wrote: > > > Since it sounds like there will also be a toolchain track, I don't see why > > you would need multiple MCs along with it. > > Just like last year the toolchain track would be a substitute for > Cauldron and it would be a completely different thing 100% focused on > the toolchain. Here we are talking about discussing topics of interest > to the kernel as well. IIRC last year we had a llvm toolcahin MC as well. Precisely, recall last year there were 3 toolchain tracks. https://linuxplumbersconf.org/event/7/timetable/#all 1. GNU Tools Track (https://linuxplumbersconf.org/event/7/sessions/90/#all). This was a substitute for the GNU Tools Cauldron conference that got cancelled due to COVID. (https://gcc.gnu.org/wiki/cauldron2020) 2. GNU Toolchain MC (https://linuxplumbersconf.org/event/7/sessions/95/#20200828). 3. LLVM MC (https://linuxplumbersconf.org/event/7/sessions/84/#20200827) What we're discussing here is combining 2 and 3; it sounds like you're suggesting combining 1, 2, and 3. I don't think it would be appropriate for me to suggest LLVM specific topics (or kernel specific topics for that matter) for what is effectively a replacement for the GNU Tools Cauldron, and GNU Tools Cauldron isn't specific to the Linux kernel (where as 2 and 3 very much are, or were). While I suspect we can fit all relevant topics for GNU and LLVM specific to the kernel in one MC, we would like to first get a sense of CFP volume from potential speakers to decide whether to combine any MCs at all this year, or repeat what we did last year. Knowing when the deadline is for MC track proposals would help us help potential speakers have a deadline to notify us. But it's not clear when MC proposals for the MC tracks themselves are due, which is what I'm asking. Not deadlines for an MC track's actual talks. -- Thanks, ~Nick Desaulniers