From: Andrew Donnellan <ajd@linux.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: lwn@lwn.net
Subject: Re: [ANNOUNCE] [CFP] Call for Sessions - linux.conf.au Online 2021 Kernel Miniconf
Date: Sun, 3 Jan 2021 18:47:45 +1100 [thread overview]
Message-ID: <626b30c1-0546-2abd-90eb-6681fbc3e25c@linux.ibm.com> (raw)
In-Reply-To: <f43afd8c-5ce6-c505-3f4c-bd8f130ff904@linux.ibm.com>
On 30/11/20 1:45 pm, Andrew Donnellan wrote:
> LCA2021 Kernel Miniconf - Online - 2021-01-23
> ---------------------------------------------
>
> LCA Kernel Miniconf submissions now open! (Ever wanted to present at
> LCA, but couldn't justify flying to Australia? Well, 2021 is your chance
> - we're going online-only for reasons you're probably aware of.)
>
> Submissions close: 2020-12-18, 23:59 AoE/UTC-12
> Submissions: https://linux.conf.au/proposals/submit/kernel-miniconf/
> More info: https://lca-kernel.ozlabs.org/2021-cfs.html
The deadline has been extended until January 7 - we're looking for talks
on a broad range of kernel topics, so please feel free to submit a
proposal about anything kernel-related!
>
> ***************************************************************************
>
> linux.conf.au 2021 will be held at the Australian National University,
> Canberra^W^W^W^W^W^Win the comfort of your own homes, by the magic of
> the internet, from 23-25 January 2021.
>
> The Kernel Miniconf is a single-day miniconf track, held on Saturday 23
> January, about everything related to the kernel and low-level systems
> programming.
>
> The Kernel Miniconf will focus on a variety of kernel-related topics -
> technical presentations on up-and-coming kernel developments, the future
> direction of the kernel, and kernel development community and process
> matters. Past Kernel Miniconfs have included technical talks on topics
> such as memory management, RCU, scheduling and filesystems, as well as
> talks on Linux kernel community topics such as licensing and Linux
> kernel development process.
>
> We invite submissions on anything related to kernel and low-level
> systems programming. We welcome submissions from developers of all
> levels of experience in the kernel community, covering a broad range of
> topics. 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-01-03 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 2:45 Andrew Donnellan
[not found] ` <CABfRCziSf1iw3tb--j6F0ebPwx+kgtL_Jk9fA37gN7uDqEVPvg@mail.gmail.com>
2020-11-30 3:46 ` Andrew Donnellan
2020-11-30 4:11 ` Andrew Donnellan
2021-01-03 7:47 ` 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=626b30c1-0546-2abd-90eb-6681fbc3e25c@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®