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=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, USER_AGENT_SANE_2 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 E59AEC4360C for ; Thu, 1 Apr 2021 18:28:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C5E5E60FD9 for ; Thu, 1 Apr 2021 18:28:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237674AbhDAS2q (ORCPT ); Thu, 1 Apr 2021 14:28:46 -0400 Received: from mail.kernel.org ([198.145.29.99]:45708 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237027AbhDASSp (ORCPT ); Thu, 1 Apr 2021 14:18:45 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B3E0361245; Thu, 1 Apr 2021 13:29:37 +0000 (UTC) Date: Thu, 1 Apr 2021 09:29:35 -0400 From: Steven Rostedt To: Nick Desaulniers Cc: Elena Zannoni , "Jose E. Marchesi" , linux-toolchains@vger.kernel.org, clang-built-linux , Kees Cook , Florian Weimer , Christian Brauner , nick.alcock@oracle.com, Segher Boessenkool Subject: Re: Plumbers CF MCs Message-ID: <20210401092935.43d3ed54@gandalf.local.home> In-Reply-To: References: <87o8fa3oua.fsf@gnu.org> <403153ed-7953-c42e-40a2-6ad313acd661@oracle.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-toolchains@vger.kernel.org On Wed, 31 Mar 2021 13:36:03 -0700 Nick Desaulniers wrote: > Steven, sorry if I missed it, but can the conf organizers pick and > post a date for the deadline for Call-for-MC submissions? This might You mean for MC topics, not the MC itself. > help MC organizers plan for putting out their own CFPs, and planning > deadlines. In our case, it would be figuring out whether one day vs > more (if possible) or splitting the MC in two is necessary by the > deadline. It might not even be an issue at all this year, but I think > that's the only concern folks have about doing a single > kernel+toolchain MC (vs split like last year). As I replied to Elena. We don't give out double slots when an MC is ready. It is only given out if they are slots available after all MCs have been accepted. Since it sounds like there will also be a toolchain track, I don't see why you would need multiple MCs along with it. -- Steve