llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Jose E. Marchesi" <jemarch@gnu.org>,
	clang-built-linux <llvm@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Plumbers conf presentation on -fanalyze?
Date: Wed, 22 Jun 2022 15:12:49 -0400	[thread overview]
Message-ID: <4a9629d0e8f14afbbb3c342c17c1633c9e882e9a.camel@redhat.com> (raw)
In-Reply-To: <CAKwvOdmJgU_MZjwuVXz5QvFdA4+eTHKqxT06HMAq=Hau03ar9Q@mail.gmail.com>

On Tue, 2022-06-21 at 15:06 -0700, Nick Desaulniers wrote:
> On Thu, Apr 14, 2022 at 3:08 PM David Malcolm <dmalcolm@redhat.com>
> wrote:
> > 
> > On Thu, 2022-04-14 at 14:42 -0700, Nick Desaulniers wrote:
> > > Hi David,
> > > 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.
> > > 
> > > We had seen
> > >  
> > > https://developers.redhat.com/articles/2022/04/12/state-static-analysis-gcc-12-compiler#scaling_up_the_analyzer
> > > particularly the section on The Linux kernel and were wondering
> > > if
> > > you'd be interested in presenting more information about -
> > > fanalyze to
> > > kernel and toolchain developers there?
> > 
> > Thanks!  I'm very much interested, but am not yet sure about travel
> > (both in terms of (a) budget and (b) possible new virus strains). 
> > Is
> > this conference going to be purely in-person, or hybrid virtual/in-
> > person?
> 
> Hi David,
> If you're still considering attending Linux Plumbers conf, please
> submit a proposal:
> https://lpc.events/event/16/abstracts/
> Please make sure to select "Toolchains Track" as the "Track" after
> clicking on "Submit new abstract."
> 

Hi Nick

Thanks, I've registered to attend, and have submitted this abstract:

  https://lpc.events/event/16/abstracts/1293/

("GCC's -fanalyzer and the Linux kernel" #177)

Hope the above looks good.

Dave



      reply	other threads:[~2022-06-22 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 21:42 Plumbers conf presentation on -fanalyze? Nick Desaulniers
2022-04-14 22:08 ` David Malcolm
2022-04-14 22:13   ` Nick Desaulniers
2022-04-14 23:30     ` James Bottomley
2022-04-14 23:35       ` Steven Rostedt
2022-06-21 22:06   ` Nick Desaulniers
2022-06-22 19:12     ` David Malcolm [this message]

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=4a9629d0e8f14afbbb3c342c17c1633c9e882e9a.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=jemarch@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).