public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: libc-alpha@sourceware.org
Subject: Toolchain-and-Linux-kernel session at LPC
Date: Thu, 30 Jul 2020 17:48:21 +0200	[thread overview]
Message-ID: <87pn8dngvu.fsf@oracle.com> (raw)



Hi good peoples!

As you probably know there is gonna be a GNU Tools Track at the virtual
LPC 2020 conference.  Instructions on how to participate have been
already sent here and can be found at
https://gcc.gnu.org/wiki/linuxplumbers2020.

[By the way, the deadline to send proposals for talks is today, so
 please do so if you want to participate!]

Additionally to the regular talks/tutorials/etc in the track, and
considering we are collocated with the Linux Plumbers Conference, we
think it would be very interesting to have a Toolchain<->kernel session
as part of the track, since the kernel hackers will be there.

The purpose of this session would be to address specific discussions
between toolchain hackers and Linux kernel hackers.  Examples of such
topics are the wrapping of Linux syscalls, security features that the
kernel people would like the toolchain to support, impact of particular
optimizations on the kernel, debugging of the kernel, and the like.

So if you are working in an area where you would benefit from such
interaction with the kernel people, and you would be interested in doing
so during LPC, please send let me know at jemarch@gnu.org.

If we can gather enough interest then we will register the session as a
Micro-Conference in LPC.

Note that this session would _not_ overlap with the rest of the GNU
Tools track, and that the same topic may be presented and discussed as
both a regular talk/tutorial/whatever in the GNU Tools track and also as
part of the kernel discussion session.

                 reply	other threads:[~2020-07-30 15:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87pn8dngvu.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=libc-alpha@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).