public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Drew Fustini <dfustini@baylibre.com>
To: Atish Patra <atishp@atishpatra.org>
Cc: linux-riscv <linux-riscv@lists.infradead.org>,
	"open list:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv)"
	<kvm-riscv@lists.infradead.org>,
	OpenSBI <opensbi@lists.infradead.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	"open list:RISC-V" <qemu-riscv@nongnu.org>
Subject: Re: CFP open for RISC-V MC at Linux Plumbers Conference 2023
Date: Mon, 26 Jun 2023 21:12:45 -0700	[thread overview]
Message-ID: <ZJphvbTsp6Q4Dfrq@x1> (raw)
In-Reply-To: <CAOnJCU+uMF-brnyjA1HLhupYPqL0ebOVu+ivrSn2AewuSrhtBw@mail.gmail.com>

On Mon, Jun 19, 2023 at 12:55:39PM -0700, Atish Patra wrote:
> The CFP for topic proposals for the RISC-V micro conference[1] 2023 is open now.
> Please submit your proposal before it's too late!

Thanks for posting. I am looking forward to it!

> The Linux plumbers event will be both in person and remote
> (hybrid)virtual this year. More details can be found here [2].
> 
> We will start accepting proposals after 15th August 2023 to avoid last
> minute visa/travel hassles.
> The conference registration sells out pretty quickly too. Thus, we
> would prefer to sort out the schedule sooner than later.
> 
> The final deadline is 15th October 2023 though.
> 
> [1] https://lpc.events/event/16/contributions/1148/

I think that page is from 2022 and that this would be a better link:
https://lpc.events/blog/current/index.php/2023/06/23/risc-v-microconference-cfp/

Drew

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-06-27  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 19:55 CFP open for RISC-V MC at Linux Plumbers Conference 2023 Atish Patra
2023-06-27  4:12 ` Drew Fustini [this message]
2023-06-27  6:21   ` Atish Patra
2023-08-11 18:21     ` Atish Patra

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=ZJphvbTsp6Q4Dfrq@x1 \
    --to=dfustini@baylibre.com \
    --cc=atishp@atishpatra.org \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=opensbi@lists.infradead.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=u-boot@lists.denx.de \
    /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