From: "H. Peter Anvin" <hpa@zytor.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Self- nomination - hpa
Date: Thu, 28 Jul 2016 22:39:21 -0700 [thread overview]
Message-ID: <49713840-7017-7dd5-50b3-9c3b15e12fc8@zytor.com> (raw)
Hello,
I would like to nominate myself to the kernel summit. I am part of the
tip team co-maintaining the x86, and in particular I am the direct
interface to Intel on that team. This also means I work directly with
the hardware and firmware architects on future developments (which has
occupied a fair bit of my time lately) trying to steer them in the
direction of being Linux-friendly; more recently we have gotten traction
at adding features specifically for the benefit of Linux.
I also have long since been acting as an informal bridge to the gcc,
llvm and icc teams, and it has been suggested that I should make that
bridge more formal. This would be a good thing to discuss at Kernel
Summit, perhaps as part of David Howell's proposed Compiler Shopping
List session.
I am also trying to develop direct connections with the C standards
committee.
-hpa
reply other threads:[~2016-07-29 5:39 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=49713840-7017-7dd5-50b3-9c3b15e12fc8@zytor.com \
--to=hpa@zytor.com \
--cc=ksummit-discuss@lists.linuxfoundation.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