From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: lwn@lwn.net
Subject: [ANNOUNCE] Call for Papers - linux.conf.au Kernel Miniconf, Christchurch NZ, 21-25 Jan 2019
Date: Sun, 21 Oct 2018 12:10:53 +1100 [thread overview]
Message-ID: <4e8f907e-ce44-191e-8ded-29ba9ab1cd08@au1.ibm.com> (raw)
The linux.conf.au Kernel Miniconf is happening once again, this time in
Christchurch on 22 Jan 2019.
*** Submissions close on 2018-12-16, 23:59 AoE, with early submissions
(before 2018-11-16, 23:59 AoE) given priority. ***
*** Submission details: http://lca-kernel.ozlabs.org/2019-cfp.html ***
The Kernel Miniconf is a 1 day stream alongside the main LCA conference
to talk about kernel stuff.
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.
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 strongly encourage both first-time and seasoned speakers from all
backgrounds, ages, genders, nationalities, ethnicities, religions and
abilities. Like the main LCA conference itself, we respect and encourage
diversity at our miniconf.
Speakers will need to purchase an LCA ticket to attend.
See http://lca-kernel.ozlabs.org/2019-cfp.html for full details and the
submission form.
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com IBM Australia Limited
next reply other threads:[~2018-10-21 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 1:10 Andrew Donnellan [this message]
2018-12-15 7:06 ` [ANNOUNCE] Call for Papers - linux.conf.au Kernel Miniconf, Christchurch NZ, 21-25 Jan 2019 Andrew Donnellan
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=4e8f907e-ce44-191e-8ded-29ba9ab1cd08@au1.ibm.com \
--to=andrew.donnellan@au1.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;
as well as URLs for NNTP newsgroup(s).