From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Matthias Männich" <maennich@google.com>,
"Giuliano Procida" <gprocida@google.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
clang-built-linux <llvm@lists.linux.dev>,
"Dodji Seketeli" <dodji@seketeli.org>,
guillermo.e.martinez@oracle.com
Subject: Re: Kernel ABI Monitoring and toolchain support
Date: Wed, 20 Apr 2022 18:02:19 +0200 [thread overview]
Message-ID: <87fsm7rbec.fsf@oracle.com> (raw)
In-Reply-To: <CAKwvOdnb-MV+Fw2oeZ5qiGQH9FPOjgYTDtVrYc1=ynY7=NReDQ@mail.gmail.com> (Nick Desaulniers's message of "Thu, 14 Apr 2022 14:33:17 -0700")
[Adding Dodji Seketeli, libabigail maintainer,
and Guillermo Martinez, who works in the CTF support for libabigail
including kernel support.]
> Hi Matthias and Giuliano,
> Jose and I are currently in the planning process to put together a
> Kernel+Toolchain microconference track at Linux Plumbers Conference
> this year (Sept 12-14) in Dublin, Ireland.
>
> Would you all be interested in a leading session on Kernel ABI
> Monitoring and perhaps what toolchain vendors can do to help, as part
> of our MC (which itself is currently still in planning phase).
next prev parent reply other threads:[~2022-04-20 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 21:33 Kernel ABI Monitoring and toolchain support Nick Desaulniers
2022-04-20 16:02 ` Jose E. Marchesi [this message]
[not found] ` <CAGvU0H=sjwsWEmq1R7LKHiPjB3aBkzQ_qJqXDxhT_rFJShgVFg@mail.gmail.com>
2022-05-07 2:15 ` Guillermo E. Martinez
2022-06-20 13:42 ` Matthias Männich
2022-06-21 21:19 ` Nick Desaulniers
2022-06-21 21:27 ` Elena Zannoni
2022-06-22 2:14 ` Guillermo E. Martinez
2022-06-22 15:27 ` Guillermo E. Martinez
2022-06-22 19:47 ` Nick Desaulniers
2022-06-23 11:54 ` Dodji Seketeli
2022-06-24 9:03 ` Dodji Seketeli
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=87fsm7rbec.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=guillermo.e.martinez@oracle.com \
--cc=jemarch@gnu.org \
--cc=llvm@lists.linux.dev \
--cc=maennich@google.com \
--cc=ndesaulniers@google.com \
/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