All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] LPC 2019 Call for Microconferences and Refereed-Track Proposals
Date: Tue, 21 May 2019 16:08:29 +0200	[thread overview]
Message-ID: <87ab01c0f4ee924e1e20684d150c4eed6f0f41ac.camel@redhat.com> (raw)
In-Reply-To: 9350bded-3576-0feb-9860-3ba56802aed2@tessares.net

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

On Tue, 2019-05-21 at 13:44 +0200, Matthieu Baerts wrote:
> A few weeks or months ago, we talked about (maybe) participating to LPC
> 2019. The Linux Plumbers Conference for 2019 has been set for September
> 9-11 at the Corinthia Hotel in Lisbon, Portugal.

Indeed I agree that an MPTCP talk/paper there would be very nice.

> One of my colleague just pointed me out that the Call for Proposals is
> open and the submission deadline is scheduled for the 23rd of May at
> 05:30 (my time I guess). Less than 48h from now then.
> 
> https://www.linuxplumbersconf.org/event/4/abstracts/

AFACIK the networking CfP is not yet out _and_ there will be a
networking CfP. MPTCP could fit that too, so there is almost for sure a
little more time (even if an undefined amount;)

Cheers,

Paolo


             reply	other threads:[~2019-05-21 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 14:08 Paolo Abeni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-22 10:58 [MPTCP] LPC 2019 Call for Microconferences and Refereed-Track Proposals Matthieu Baerts
2019-05-22  0:04 Mat Martineau
2019-05-21 14:22 Matthieu Baerts
2019-05-21 11:44 Matthieu Baerts

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=87ab01c0f4ee924e1e20684d150c4eed6f0f41ac.camel@redhat.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.