linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeff Layton <jlayton@poochiereds.net>,
	linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-cifs@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 linux-nfs@vger.kernel.org, linux-scsi@vger.kernel.org,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
	ceph-devel@vger.kernel.org, linux-nvme@lists.infradead.org
Cc: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Subject: Re: LSF/MM 2017: Call for Proposals
Date: Wed, 07 Dec 2016 06:57:06 -0800	[thread overview]
Message-ID: <1481122626.2354.14.camel@HansenPartnership.com> (raw)
In-Reply-To: <1480601506.2511.7.camel@poochiereds.net>

On Thu, 2016-12-01 at 09:11 -0500, Jeff Layton wrote:
> 1) Proposals for agenda topics should be sent before January 15th, 
> 2016 to:
> 
>     lsf-pc@lists.linux-foundation.org
> 
> and cc the Linux list or lists that are relevant for the topic in
> question:
> 
>     ATA:   linux-ide@vger.kernel.org
>     Block: linux-block@vger.kernel.org
>     FS:    linux-fsdevel@vger.kernel.org
>     MM:    linux-mm@kvack.org
>     SCSI:  linux-scsi@vger.kernel.org
>     NVMe:  linux-nvme@lists.infradead.org
> 
> Please tag your proposal with [LSF/MM TOPIC] to make it easier to 
> track.

Just on this point, since there seems to be a lot of confusion: lsf-pc
is the list for contacting the programme committee, so you cannot
subscribe to it.

There is no -discuss equivalent, like kernel summit has, because we
expect you to cc the relevant existing mailing list and have the
discussion there instead rather than expecting people to subscribe to a
new list.

James

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-12-07 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 14:11 LSF/MM 2017: Call for Proposals Jeff Layton
2016-12-07 14:57 ` James Bottomley [this message]
2016-12-08 12:26   ` Michal Hocko
2016-12-08 12:34     ` [Lsf-pc] " Jan Kara
2016-12-08 15:30     ` James Bottomley
2016-12-08 15:37       ` Michal Hocko
  -- strict thread matches above, loose matches on Subject: below --
2016-12-27 17:19 Jeff Layton

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1481122626.2354.14.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jlayton@poochiereds.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).