All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Miroslav Benes <mbenes@suse.cz>,
	jpoimboe@kernel.org, jikos@kernel.org, pmladek@suse.com,
	joe.lawrence@redhat.com, nstange@suse.de, mpdesouza@suse.de,
	broonie@kernel.org, live-patching@vger.kernel.org,
	Nick Desaulniers <ndesaulniers@google.com>,
	elena.zannoni@oracle.com, indu.bhagat@oracle.com
Subject: Re: Live Patching Microconference at Linux Plumbers
Date: Fri, 14 Apr 2023 16:34:15 +0200	[thread overview]
Message-ID: <87a5za353s.fsf@oracle.com> (raw)
In-Reply-To: <CANiq72mk8-TZO59+oL2B6Xt8KyZNDBtyaP6TCNLVCdLASjJDnQ@mail.gmail.com> (Miguel Ojeda's message of "Fri, 14 Apr 2023 15:51:21 +0200")


> On Fri, Apr 14, 2023 at 2:54 PM Jose E. Marchesi
> <jose.marchesi@oracle.com> wrote:
>>
>> As for Rust... we have the Rust GCC support and that would fit in the MC
>> as well.  We can surely invite some of the hackers working in the
>> front-end.  But maybe it would be better to have that discussion in a
>> Rust MC, if there is gonna be one (Miguel?).
>
> It is likely we will submit a Rust MC proposal, yeah.
>
> Last year we had both Rust GCC and rustc_codegen_gcc presenting in the
> Rust MC (and Kangrejos too), and I would be grateful to have them
> again, but if it is best for everybody otherwise, we can change things
> of course.

I think it makes sense to discuss these toolchain-related topics in the
Rust MC.  Infrastructure tends to be traversal :)

> (Is it already known how tight timing will be this year for MCs?)
>
>> For starters, I would make sure that the involved MCs (Live Patching,
>> Toolchains, and an eventual Rust MC) do not overlap in the schedule.
>> Then we could have these discussions in either microconferences.
>
> Yeah, it sounds good to me.
>
> Cheers,
> Miguel

  reply	other threads:[~2023-04-14 14:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 12:05 Live Patching Microconference at Linux Plumbers Miroslav Benes
2023-03-29 16:28 ` Joe Lawrence
2023-04-14  9:11 ` Miroslav Benes
2023-04-14  9:53 ` Mark Rutland
2023-04-14 12:54   ` Jose E. Marchesi
2023-04-14 13:51     ` Miguel Ojeda
2023-04-14 14:34       ` Jose E. Marchesi [this message]
2023-04-14 14:14     ` Miroslav Benes
2023-04-14 17:12   ` Josh Poimboeuf
2023-04-14 19:04     ` Miguel Ojeda
2023-04-14 20:22       ` Arnaldo Carvalho de Melo
2023-04-14 20:29         ` Miguel Ojeda
2023-04-14 21:10       ` Josh Poimboeuf
2023-04-14 19:30     ` Peter Zijlstra
2023-04-15  4:39       ` Josh Poimboeuf
2023-04-17  7:48         ` Peter Zijlstra
2023-04-17  8:58     ` Mark Rutland
2023-04-18  3:53   ` James Morris
2023-05-03 20:05   ` Joe Lawrence
2023-05-03 20:33     ` Steven Rostedt
2023-05-22 18:41 ` Joe Lawrence

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=87a5za353s.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=broonie@kernel.org \
    --cc=elena.zannoni@oracle.com \
    --cc=indu.bhagat@oracle.com \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mbenes@suse.cz \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=mpdesouza@suse.de \
    --cc=ndesaulniers@google.com \
    --cc=nstange@suse.de \
    --cc=pmladek@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.