From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Subject: Re: [ANN] Reminder: deadline for LPC and netconf 2024 submission approaching
Date: Wed, 31 Jul 2024 07:53:25 -0700 [thread overview]
Message-ID: <20240731075325.3024fda9@kernel.org> (raw)
In-Reply-To: <20240725165102.4e1b55cb@kernel.org>
Final reminder, good people of netdev!
Please submit your topics for netconf and LPC by the end of the week!
On Thu, 25 Jul 2024 16:51:02 -0700 Jakub Kicinski wrote:
> Hi!
>
> The deadline for submissions to LPC and netconf is fast approaching
> (August 4th, we extended the previous netconf deadline to align).
>
> Quoting from the LPC CFP:
>
> Relevant topics span from proposals for kernel changes, through user
> space tooling, to presenting interesting use cases, new protocols
> or new, interesting problems waiting for a solution.
>
> The goal is to allow gathering early feedback on proposals, reach
> consensus on long running mailing list discussions and raise awareness
> of interesting work or use cases. We are seeking proposals of 30-45 min
> in length (including Q&A discussion). Presenting in person is preferred,
> however, exceptions could be given for remotely presenting if attending
> in person is challenging.
>
> LPC CFP: https://lore.kernel.org/all/20240605143056.4a850c40@kernel.org
> netconf: https://lore.kernel.org/all/20240410091255.2fd6a373@kernel.org
>
> Please feel free to submit the same topic to netconf and LPC.
>
> netconf is a great opportunity to discuss proposals and challenges with
> the maintainers and key contributors, refer to materials from previous
> editions to get a sense of the topics:
> https://netdev.bots.linux.dev/netconf/
> Submissions of LPC are via the website, for netconf please send me
> a few sentences over email. Don't be shy!
>
> Note that we have some speaker tickets to provide to those who haven't
> registered for LPC, yet.
>
> If there are any questions or concerns don't hesitate to reach out
> to me on- or off-list.
>
> Last but not least, remember that netconf is not the same thing as
> netdev.conf, which took place a week ago :)
next prev parent reply other threads:[~2024-07-31 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 23:51 [ANN] Reminder: deadline for LPC and netconf 2024 submission approaching Jakub Kicinski
2024-07-26 14:20 ` Jakub Kicinski
2024-07-31 14:53 ` Jakub Kicinski [this message]
2024-10-03 12:29 ` Jakub Kicinski
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=20240731075325.3024fda9@kernel.org \
--to=kuba@kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.