ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Self Nomination - mcgrof
Date: Wed, 27 Jul 2016 18:56:04 +0200	[thread overview]
Message-ID: <20160727165604.GC5537@wotan.suse.de> (raw)


Mimi put out a nomination collateral for me, I confirm interest in the kernel
summit this year, with these main topics of interest:

  o Signature management - in my capacity to provide updates with regards
    to firmware signing work, with an aside effort to provide a new flexible
    API to the existing firmware API, the sysdata API

  o memory model descriptions - as suggested by David Howells, and augmented by
    Paul E. McKenney.

  o compiler features

  o 0-day: the past, present and future: my keen interest in this is the
    inevitability of further automation in both testing but later slowly
    more precise mechanical programming and software evolution. What are
    our limits and where we are going.

  o Complex dependencies and semantics

  Luis

                 reply	other threads:[~2016-07-27 16:56 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=20160727165604.GC5537@wotan.suse.de \
    --to=mcgrof@suse.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