Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1791355pxj; Fri, 18 Jun 2021 15:57:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyf6dGlWFGBHJbdRQo2Sj+mJXpcURwdmWFc4pGpBTYsMknObRroU2AE7Jr8mTNarxGiuRMP X-Received: by 2002:a50:ee13:: with SMTP id g19mr3599490eds.147.1624057045263; Fri, 18 Jun 2021 15:57:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624057045; cv=none; d=google.com; s=arc-20160816; b=E9Cv0d+nGa7z273u8AG+SuTUBfGF06u0Qn/EpFnbqxCSZ8nPe7rlILCpZ4pG8XrYzI ofyW5+XyXo7Z5h7o1tTPhyJXS3gsWM1jaG9jPCtVQQeVo+c7KDwUnuzfDC9d/9JGZ1Sz w8E7PhRSTujtbFLmT/lZNrchvdfA5mSJgioMwlADzyljxgY0/+UXKogoku01kvHH2EDY N0vVCdy2K0/W1kw2IROwA7Gqa5ImHV4VNFqfb7uIhRuHN3wDh1r7IAsIXKU7BdgYn35T OO8idydeCHkdg865khgHkkf1WC8StLqfc6RV1TOElejkwyaUJ/GRcFsmBIYBnOmJJjrz QD+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=BvdMYBnm6oT9jezt+5Q8YL5YbflCc61xbPoeXSMGn5E=; b=RQZMkkGeDUf9G8zSSJU5PGK5yLZkrLORNU/2wLzKy14H4y2QsmB6xuchQhruozbfv1 GBwCbSVLHYE6n5QQYSBRssYYUdpkPomcz7o7SWib9nyOaEmPoF1NlB9xpgDz+vsVuIOd K6+NwaUdtorem6S9li/JVYWDmGEeOwX3wSfUXQOBDO/yDaiurm+pDPI8cFDkwHrPa37T P+iq7PJa54kvM/abUo7/84YaggXaUyelQcdQ3hzCdaxKQoeuSngBB+J25PlBrrHS3h9m W2iW7i/wIhCMY+h5abr8v51jVzyCVpGd+cfiY1JFDWXOWJ2JzWhZEhbZM0GcJ2cw9A2I MVqg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="R/HYr50F"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n17si10087539edy.506.2021.06.18.15.57.02; Fri, 18 Jun 2021 15:57:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="R/HYr50F"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235973AbhFRQsF (ORCPT + 99 others); Fri, 18 Jun 2021 12:48:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:50164 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235740AbhFRQsD (ORCPT ); Fri, 18 Jun 2021 12:48:03 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id E4FB96127C; Fri, 18 Jun 2021 16:45:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1624034753; bh=ZTtwHmqh0rQ3M2ho9c60I0q0eOzXiN2NKnpGl1n9jAs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=R/HYr50FfFMgL8AT6+8hLyRxD/ZSJ4S2xb12SBGX3bFOa3uWO/saYDhlnVh86HZZi OPDTpRuYv/2ZQouGk4fRnlCJgkL18zxi+4aIaD64YAzf49WelDhz2fEAbY0JRP/RbJ VR1FI2PTAT6TbjogpFjK/WPi7QxmCYgwALtjhSbyhztW+Tjo7JUPS5dSdcGLjDT5A1 w5OHX7Fe1IquhO1WW9ds+tBjdvFYugD7ejgElqSQwxbbOUSkwwTVmZzxfTyxYEvOV8 s/Hgm/YM5MQ5/pN9z0oud2vd0ZPIKafP7cIaWCVfDbFVRZCpOjBzgT0HD4Wi/v2DQ0 4WeLullrbJTJg== Date: Fri, 18 Jun 2021 18:45:45 +0200 From: Mauro Carvalho Chehab To: Mark Brown Cc: Steven Rostedt , Geert Uytterhoeven , James Bottomley , Laurent Pinchart , Shuah Khan , Konstantin Ryabitsev , "Enrico Weigelt, metux IT consult" , David Hildenbrand , Greg KH , Christoph Lameter , Theodore Ts'o , Jiri Kosina , ksummit@lists.linux.dev, Linux Kernel Mailing List , linux-block@vger.kernel.org, Linux FS Devel , Linux MM , netdev , Linux-Arch , Linux API Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off Message-ID: <20210618184545.33ea3d47@coco.lan> In-Reply-To: <20210618155829.GD4920@sirena.org.uk> References: <5038827c-463f-232d-4dec-da56c71089bd@metux.net> <20210610182318.jrxe3avfhkqq7xqn@nitro.local> <20210610152633.7e4a7304@oasis.local.home> <37e8d1a5-7c32-8e77-bb05-f851c87a1004@linuxfoundation.org> <20210618103214.0df292ec@oasis.local.home> <20210618155829.GD4920@sirena.org.uk> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-redhat-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-kernel@vger.kernel.org Em Fri, 18 Jun 2021 16:58:29 +0100 Mark Brown escreveu: > On Fri, Jun 18, 2021 at 10:32:14AM -0400, Steven Rostedt wrote: > > On Fri, 18 Jun 2021 16:28:02 +0200 > > Geert Uytterhoeven wrote: > > > > What about letting people use the personal mic they're already > > > carrying, i.e. a phone? > > > Interesting idea. > > > I wonder how well that would work in practice. Are all phones good > > enough to prevent echo? > > Unless you get the latency for the WebRTC<->in room speaker down lower > than I'd expect it to be I'd expect echo cancellation to have fun, > though beam forming might reject a lot of in room noise including that - > higher end modern phones are astonishingly good at this stuff. I'd not > trust it to work reliably for all attendees though, it's the sort of > thing where you'll get lots of per device variation. The local audience should be listening to the in-room audio, in order to avoid echo. Also, all local mics should be muted, if someone is speaking from a remote location. Yet, echo is unavoidable if a remote participant is speaking while listening to the audio without headphones. If this ever happens, I guess the moderator should cut the remote audio and ask the remote participant to lower their speakers or use a headphone. Thanks, Mauro