From: Andrew Donnellan <ajd@linux.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: lwn@lwn.net
Subject: Re: [ANNOUNCE] [CFP] linux.conf.au Online 2022 Kernel Miniconf
Date: Sat, 4 Sep 2021 02:13:11 +1000 [thread overview]
Message-ID: <1f527127-6884-765f-3029-6f70b0cb61bd@linux.ibm.com> (raw)
In-Reply-To: <e7e0d0c0-799f-28b7-2a2e-418afe809f24@linux.ibm.com>
On 12/8/21 1:19 am, Andrew Donnellan wrote:
> LCA2022 Kernel Miniconf - Online - 2022-01-14
> ---------------------------------------------
>
> The linux.conf.au 2022 Kernel Miniconf Call for Proposals is now open.
> Start working on your talks!
>
> Date: 2022-01-14
> Location: The Internet (again)
> Submissions close: 2021-09-05, 23:59 AoE/UTC-12
> Submissions: https://linux.conf.au/proposals/submit/kernel-miniconf/
> More info: https://lca-kernel.ozlabs.org/2022-cfp.html
The CFP for both the Kernel Miniconf and the main linux.conf.au
conference has been extended to 2021-09-12, due to a shortage of
submissions.
We have an audience consisting of not just kernel developers but also
downstream users, so we are interested in a wide range of topics - if
you or someone you know has something that might even possibly be
interesting to talk about, please submit!
If you have any questions please contact me.
>
> Significant changes from last year:
> - All miniconf speakers are guaranteed a free ticket
> - All talks will be 30 minutes long
> - CFP is now being run at the same time as main conference CFP process:
> if your talk is of broader interest consider submitting to the main
> conference as well
>
> ***************************************************************************
>
> linux.conf.au 2022 will be held from 14-16 January 2022.
>
> Due to the ongoing COVID-19-related restrictions on events and travel,
> LCA2022 will once again be held online. (Silver lining is you can speak
> or attend from wherever you are without flying here!)
>
> The Kernel Miniconf is a single-day miniconf track, held on Friday 14
> January, about everything related to the kernel and low-level systems
> programming.
>
> The Kernel Miniconf invites talks about up-and-coming kernel
> developments, the future direction of the kernel, and kernel development
> community and process matters. Past Kernel Miniconfs have covered topics
> such as memory management, RCU, scheduling, testing/CI and filesystems,
> as well as community and process topics such as licensing, developer
> workflows, safety critical processes, and so on.
>
> We invite submissions on anything related to kernel and low-level
> systems programming. We welcome submissions from developers of all
> levels of experience, and from anyone connected with the kernel whether
> you are an upstream kernel developer, distro maintainer, academic
> researcher or a developer who works further downstream. The focus of the
> miniconf will primarily be on Linux, however non-Linux talks of
> sufficient interest to a primarily Linux audience will be considered.
>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
prev parent reply other threads:[~2021-09-03 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 15:19 Andrew Donnellan
2021-09-03 16:13 ` Andrew Donnellan [this message]
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=1f527127-6884-765f-3029-6f70b0cb61bd@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
/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
all inboxes | Powered by JetHome®