From: Mike Rapoport <rppt@kernel.org>
To: linux-arch@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: [ANNOUNCE] linux/arch/* Microconference Accepted into 2020 Linux Plumbers Conference
Date: Wed, 15 Jul 2020 11:46:48 +0300 [thread overview]
Message-ID: <20200715084648.GC1181712@kernel.org> (raw)
Hi all,
This year we'll hold linux/arch/* micro-conference at Linux Plumbers [1]
to discuss, well, the code in linux/arch/*.
The purpose of this micro-conference is to bring architecture
maintainers and people working on the arch-specific code together and
see how can we consolidate and generalize this functionality.
Possible topics for the discussion could be:
* Reducing code duplication and generalizing the common code in arch/
* Moving syscall processing to C
* Memory models (FLAT, DISCONTIGOUS and SPARSE)
* 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://linuxplumbersconf.org/event/7/abstracts/
The deadline for the submissions is August, 10, 2020.
Mike and Arnd.
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: linux-arch@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: [ANNOUNCE] linux/arch/* Microconference Accepted into 2020 Linux Plumbers Conference
Date: Wed, 15 Jul 2020 11:46:48 +0300 [thread overview]
Message-ID: <20200715084648.GC1181712@kernel.org> (raw)
Message-ID: <20200715084648.e9-AWin4PO8eDXZjMR5RJqB7TzsVFmJ7LYjxDKKJVmM@z> (raw)
Hi all,
This year we'll hold linux/arch/* micro-conference at Linux Plumbers [1]
to discuss, well, the code in linux/arch/*.
The purpose of this micro-conference is to bring architecture
maintainers and people working on the arch-specific code together and
see how can we consolidate and generalize this functionality.
Possible topics for the discussion could be:
* Reducing code duplication and generalizing the common code in arch/
* Moving syscall processing to C
* Memory models (FLAT, DISCONTIGOUS and SPARSE)
* 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://linuxplumbersconf.org/event/7/abstracts/
The deadline for the submissions is August, 10, 2020.
Mike and Arnd.
--
[1] https://www.linuxplumbersconf.org/blog/2020/linux-arch-microconference-accepted-into-2020-linux-plumbers-conference/
--
Sincerely yours,
Mike.
next reply other threads:[~2020-07-15 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 8:46 Mike Rapoport [this message]
2020-07-15 8:46 ` [ANNOUNCE] linux/arch/* Microconference Accepted into 2020 Linux Plumbers Conference Mike Rapoport
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=20200715084648.GC1181712@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 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.