linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: linux-arch@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: Re: [ANNOUNCE] linux/arch Microconference Accepted to 2022 Linux Plumbers Conference
Date: Tue, 28 Jun 2022 11:05:12 +0300	[thread overview]
Message-ID: <Yrq2OD8W6Lcaxx/4@kernel.org> (raw)
In-Reply-To: <YnvSR52cbIUHJjtV@kernel.org>

Hi all,

This is a reminder that deadline is approaching but there is still time to
submit your proposals.

And of course thanks a lot for those who already submitted their topics.

On Wed, May 11, 2022 at 06:12:07PM +0300, Mike Rapoport wrote:
> Hi all,
> 
> This year we'll hold linux/arch micro-conference at Linux Plumbers [1] to
> discuss how can we improve architecture specific code and its integration
> with the generic kernel. 
> 
> Possible topics for the discussion could be:
> 
> * Reducing code duplication and generalizing the common code in arch/
> * Making headers in include/asm consistent
> * On-boarding more architectures to use common entry code
> * Devicetree
> * Future of highmem
> * Identifying old machine support:
>   - Still in active use
>   - Only in hobbyist/retro-computing
>   - Completely obsolete and broken
> 
> Please send your topic proposals to the Linux Plumber's website using the
> linux/arch as the Track you're submitting at:
> 
> https://lpc.events/event/16/abstracts/
> 
> The deadline for the submissions is 10th of July, 2022.
> 
> Mike and Arnd.
> 
> [1] https://lpc.events

-- 
Sincerely yours,
Mike.

      reply	other threads:[~2022-06-28  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 15:12 [ANNOUNCE] linux/arch Microconference Accepted to 2022 Linux Plumbers Conference Mike Rapoport
2022-06-28  8:05 ` Mike Rapoport [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=Yrq2OD8W6Lcaxx/4@kernel.org \
    --to=rppt@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).