Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp90417imj; Thu, 14 Feb 2019 16:01:41 -0800 (PST) X-Google-Smtp-Source: AHgI3IZsI8EXx1yq3vVV7vpCI5hOYOzR7IGdHT7lBbwdfMVBqazxYdAqpT8l7ZVzsliYGHFP1I/2 X-Received: by 2002:a17:902:5a5:: with SMTP id f34mr7063136plf.161.1550188900925; Thu, 14 Feb 2019 16:01:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550188900; cv=none; d=google.com; s=arc-20160816; b=zNDdX6SgqNiKd1XFSflPS5qG4c2euR5Wf7TyX5jsYmOt935bl8XC2diCczod5+0TiA y1Cz4Rel707pHG9XSz5TzWdaPghiA4LR4UAxkR1dUJe5gantL1ULraPCOeEnyCkhYLsN kEY9ZMVsr1Rd7ktq0Jjig5ieWT5zNnXDyC0mTaMObx2RW+IBZ9eaTLH9zpfjEYIHmEse G2Lj7QEVNwWw0mHXGa4CK10dkcf8UW0pksPMtHVZ64MbNC6c/6uMDd2TxZppBaFgTXgC EakomSwMzXkmIVdxqMEgn6fjFoYmGMvux9XNzxikPTTY+S+H5FIEHUWIElCRxM3/sJt2 8L4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=tQcl4MrbtmQEjmQQjXwkodsx+D7+hCY612W563z9hoQ=; b=TufMqGORtCj0YaK+SCOHsfMiBMMUtjufh7aa1ElbYeXZAsniqBSbx6APqo2Bg90qu1 gWX/OWnmN8YGiQBtZDXfEZKMxr67UyZYYsTYyFj59HCFkVtfo2mfm5W8ijI22gH+FtBP Gm1GC9U3TuOsxROe7rS73i/uluLUvA8VniWpjiLMXgTJx0XWBDSXY5snxmJdaMq0+SiS uwpq598KX46wJkMlBFal2rQ5/k/6wIBV18mFzoBf86JZYUahE+p9uslms/L16MxvlcnE SNh18gNjYIp87HtMeZyM2e0oFl1TTqBIMZbTNPBwyiay2Pb17m/MTrBa9r7Bq6wnVdO/ IVcw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 43si239056plb.299.2019.02.14.16.01.23; Thu, 14 Feb 2019 16:01:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2393120AbfBNOI0 (ORCPT + 99 others); Thu, 14 Feb 2019 09:08:26 -0500 Received: from mx2.suse.de ([195.135.220.15]:57544 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2389847AbfBNOIZ (ORCPT ); Thu, 14 Feb 2019 09:08:25 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5329BACE3; Thu, 14 Feb 2019 14:08:23 +0000 (UTC) Date: Thu, 14 Feb 2019 15:08:22 +0100 From: Michal Hocko To: Jens Axboe Cc: linux-fsdevel , linux-mm , "linux-block@vger.kernel.org" , IDE/ATA development list , linux-scsi , "linux-nvme@lists.infradead.org" , bpf@vger.kernel.org, "lsf-pc@lists.linux-foundation.org" , "linux-kernel@vger.kernel.org" , ast@kernel.org Subject: Re: [Lsf-pc] LSF/MM 2019: Call for Proposals (UPDATED!) Message-ID: <20190214140822.GA7251@dhcp22.suse.cz> References: <4f5a15c1-4f9e-acae-5094-2f38c8eebd96@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4f5a15c1-4f9e-acae-5094-2f38c8eebd96@kernel.dk> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 07-02-19 08:35:06, Jens Axboe wrote: [...] > 2) Requests to attend the summit for those that are not proposing a > topic should be sent to: > > lsf-pc@lists.linux-foundation.org > > Please summarize what expertise you will bring to the meeting, and > what you would like to discuss. Please also tag your email with > [LSF/MM ATTEND] and send it as a new thread so there is less chance of > it getting lost. Just a reminder. Please do not forget to send the ATTEND request and make it clear which track you would like to participate in the most. It is quite common that people only send topic proposals without and expclicit ATTEND request or they do not mention the track. Thanks! -- Michal Hocko SUSE Labs