From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: 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
Cc: lsf-pc@lists.linux-foundation.org
Subject: LSF/MM 2016: Call for Proposals
Date: Tue, 12 Jan 2016 11:05:45 -0500 [thread overview]
Message-ID: <yq14meiye92.fsf@sermon.lab.mkp.net> (raw)
The annual Linux Storage, Filesystem and Memory Management Summit for
2016 will be held on April 18th and 19th at the Raleigh Marriott City
center, Raleigh, NC.
Like last year, LSF/MM will be colocated with the Linux Foundation Vault
conference which takes place on April 20th and 21st in the same
venue. For those that do not know, Vault is designed to be an event
where open source storage and filesystem practitioners meet storage
implementors and, as such, it would be of benefit for LSF/MM attendees
to attend.
http://events.linuxfoundation.org/events/linux-storage-filesystem-and-mm-summit
http://events.linuxfoundation.org/events/vault
On behalf of the committee I am issuing a call for agenda proposals that
are suitable for cross-track discussion as well as technical subjects
for the breakout sessions.
1) Proposals for agenda topics should be sent before February 29th, 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
If advance notice is required for visa applications then please send
proposals before February 11th. The committee will complete the first
round of selections near that date to accommodate applications.
Please tag your proposal with [LSF/MM TOPIC] to make it easier to
track. In addition, please make sure to start a new thread for each
topic rather than following up to an existing one.
Agenda topics and attendees will be selected by the program committee,
but the final agenda will be formed by consensus of the attendees at the
summit.
We will try to cap attendance at around 25-30 per track to facilitate
discussions, although the final numbers will depend on the room sizes at
the venue.
2) Requests to attend the summit should be sent to:
lsf-pc@lists.linux-foundation.org
Please summarise what expertise you will bring to the meeting, and what
you would like to discuss. Please also tag your email with [LSF/MM
ATTEND] so there is less chance of it getting lost.
Presentations are allowed to guide discussion, but are strongly
discouraged. There will be no recording or audio bridge. However, we
expect that written minutes will be published as we did in previous
years
2015:
https://lwn.net/Articles/lsfmm2015/
2014:
http://lwn.net/Articles/LSFMM2014/
2013:
http://lwn.net/Articles/548089/
3) If you have feedback on last year's meeting that we can use to
improve this year's, please also send that to:
lsf-pc@lists.linux-foundation.org
Thank you on behalf of the program committee:
Storage:
Jens Axboe (track chair)
James Bottomley
Christoph Hellwig
Martin K. Petersen (program chair)
Filesystems:
Josef Bacik
Jan Kara
Jeff Layton (track chair)
Anna Schumaker
Theodore Ts'o
Ric Wheeler
MM:
Mel Gorman
Johannes Weiner
Rik van Riel (track chair)
--
Martin K. Petersen Oracle Linux Engineering
--
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>
next reply other threads:[~2016-01-12 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 16:05 Martin K. Petersen [this message]
2016-01-15 8:10 ` [LSF/MM ATTEND] 2016: Requests to attend MM-summit Jesper Dangaard Brouer
2016-01-15 16:49 ` Christoph Lameter
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=yq14meiye92.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--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-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