All of lore.kernel.org
 help / color / mirror / Atom feed
* Followup of yesterday's design session "refactoring the REST"
@ 2020-07-09  5:56 Jürgen Groß
  2020-07-09  9:22 ` Jan Beulich
  2020-07-09  9:34 ` Roger Pau Monné
  0 siblings, 2 replies; 4+ messages in thread
From: Jürgen Groß @ 2020-07-09  5:56 UTC (permalink / raw)
  To: xen-devel

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

Yesterday's design session at Xen Developer Summit "Hypervisor Team: .."
had one topic regarding whether we should find specific maintainers of
all the files currently assigned to "THE REST" in order to lower the
amount of reviews for those assigned to be "THE REST" maintainers.

Modifying the MAINTAINERS file adding "REST@x.y" as REST maintainer
and running the rune:

git ls-files | while true; do f=`line`; [ "$f" = "" ] && exit; \
echo $f `./scripts/get_maintainer.pl -f $f | awk '{print $(NF)}'`; \
done | awk '/REST/ { print $1}'

shows that basically the following files are covered by "THE REST":

- files directly in /
- config/
- most files in docs/ (not docs/man/)
- misc/ (only one file)
- scripts/
- lots of files in xen/common/
- xen/crypto/
- lots of files in xen/drivers/
- lots of files in xen/include/
- xen/scripts/
- some files in xen/tools/

I have attached the file list.

So the basic idea to have a "hypervisor REST" and a "tools REST"
wouldn't make a huge difference, if we don't assign docs/ to "tools
REST".

So I think it would make sense to:

- look through the docs/ and xen/include/ files whether some of those
   can be assigned to a component already having dedicated maintainers

- try to find maintainers for the other files, especially those in
   xen/common/ and xen/drivers/ (including the related include files, of
   course)

- if any of the REST maintainers doesn't want to receive mails for a
   group of the remaining REST files split the REST maintainers/files up
   accordingly

Thougts?


Juergen

[-- Attachment #2: rest.txt --]
[-- Type: text/plain, Size: 11263 bytes --]

.gitarchive-info
.gitattributes
.gitignore
.hgignore
.hgsigs
.hgtags
CODING_STYLE
CONTRIBUTING
COPYING
CREDITS
Config.mk
INSTALL
MAINTAINERS
Makefile
README
SUPPORT.md
config.guess
config.sub
config/FreeBSD.mk
config/Linux.mk
config/NetBSD.mk
config/NetBSDRump.mk
config/OpenBSD.mk
config/StdGNU.mk
config/SunOS.mk
config/arm32.mk
config/arm64.mk
config/x86_32.mk
config/x86_64.mk
docs/INDEX
docs/README.colo
docs/README.source
docs/admin-guide/index.rst
docs/admin-guide/introduction.rst
docs/admin-guide/microcode-loading.rst
docs/admin-guide/xen-overview.drawio.svg
docs/conf.py
docs/designs/argo.pandoc
docs/designs/dmop.pandoc
docs/designs/non-cooperative-migration.md
docs/designs/qemu-deprivilege.md
docs/designs/xenstore-migration.md
docs/features/dom0less.pandoc
docs/features/feature-levelling.pandoc
docs/features/hypervisorfs.pandoc
docs/features/intel_psr_cat_cdp.pandoc
docs/features/intel_psr_mba.pandoc
docs/features/livepatch.pandoc
docs/features/migration.pandoc
docs/features/qemu-deprivilege.pandoc
docs/features/sched_credit.pandoc
docs/features/sched_credit2.pandoc
docs/features/sched_rtds.pandoc
docs/features/template.pandoc
docs/figs/Makefile
docs/figs/network-basic.fig
docs/figs/network-bridge.fig
docs/figs/xenlogo.eps
docs/gen-html-index
docs/glossary.rst
docs/guest-guide/index.rst
docs/guest-guide/x86/hypercall-abi.rst
docs/guest-guide/x86/index.rst
docs/hypervisor-guide/code-coverage.rst
docs/hypervisor-guide/index.rst
docs/hypervisor-guide/x86/how-xen-boots.rst
docs/hypervisor-guide/x86/index.rst
docs/index.rst
docs/misc/9pfs.pandoc
docs/misc/amd-ucode-container.txt
docs/misc/block-scripts.txt
docs/misc/console.txt
docs/misc/crashdb.txt
docs/misc/distro_mapping.txt
docs/misc/dump-core-format.txt
docs/misc/efi.pandoc
docs/misc/grant-tables.txt
docs/misc/hvm-emulated-unplug.pandoc
docs/misc/hypfs-paths.pandoc
docs/misc/kconfig-language.rst
docs/misc/kconfig-macro-language.rst
docs/misc/kconfig.rst
docs/misc/kexec_and_kdump.txt
docs/misc/libxl_memory.txt
docs/misc/netif-staging-grants.pandoc
docs/misc/printk-formats.txt
docs/misc/pv-drivers-lifecycle.pandoc
docs/misc/pvcalls.pandoc
docs/misc/pvh.pandoc
docs/misc/qemu-backends.txt
docs/misc/status-override-table-spec.fodt
docs/misc/stubdom.txt
docs/misc/support-matrix-head.html
docs/misc/vtd-pi.txt
docs/misc/vtd.txt
docs/misc/x86-xenpv-bootloader.pandoc
docs/misc/xen-command-line.pandoc
docs/misc/xen-env-table-spec.fodt
docs/misc/xen-error-handling.txt
docs/misc/xen-makefiles/makefiles.rst
docs/misc/xen_config.html
docs/misc/xenmon.txt
docs/misc/xenpaging.txt
docs/misc/xenstore-paths.pandoc
docs/misc/xenstore-ring.txt
docs/misc/xenstore.txt
docs/misc/xl-psr.pandoc
docs/parse-support-md
docs/process/RUBRIC
docs/process/branching-checklist.txt
docs/process/release-technician-checklist.txt
docs/process/tags.pandoc
docs/process/xen-release-management.pandoc
docs/specs/libxc-migration-stream.pandoc
docs/specs/libxl-migration-stream.pandoc
docs/support-matrix-generate
docs/xen-headers
misc/coverity/model.c
scripts/add_maintainers.pl
scripts/get_maintainer.pl
scripts/git-checkout.sh
version.sh
xen/COPYING
xen/Kconfig
xen/Kconfig.debug
xen/Makefile
xen/Rules.mk
xen/arch/Kconfig
xen/common/COPYING
xen/common/Kconfig
xen/common/Makefile
xen/common/README.source
xen/common/bitmap.c
xen/common/bsearch.c
xen/common/bunzip2.c
xen/common/compat/domain.c
xen/common/compat/grant_table.c
xen/common/compat/kernel.c
xen/common/compat/memory.c
xen/common/compat/multicall.c
xen/common/compat/xenoprof.c
xen/common/compat/xlat.c
xen/common/core_parking.c
xen/common/coverage/Makefile
xen/common/coverage/coverage.c
xen/common/coverage/coverage.h
xen/common/coverage/gcc_3_4.c
xen/common/coverage/gcc_4_7.c
xen/common/coverage/gcc_4_9.c
xen/common/coverage/gcc_5.c
xen/common/coverage/gcc_7.c
xen/common/coverage/gcov.c
xen/common/coverage/gcov.h
xen/common/coverage/gcov_base.c
xen/common/coverage/llvm.c
xen/common/cpu.c
xen/common/debugtrace.c
xen/common/decompress.c
xen/common/decompress.h
xen/common/domain.c
xen/common/domctl.c
xen/common/earlycpio.c
xen/common/event_2l.c
xen/common/event_channel.c
xen/common/event_fifo.c
xen/common/gdbstub.c
xen/common/grant_table.c
xen/common/guestcopy.c
xen/common/gunzip.c
xen/common/hypfs.c
xen/common/inflate.c
xen/common/irq.c
xen/common/kernel.c
xen/common/keyhandler.c
xen/common/lib.c
xen/common/libelf/COPYING
xen/common/libelf/Makefile
xen/common/libelf/README
xen/common/libelf/libelf-dominfo.c
xen/common/libelf/libelf-loader.c
xen/common/libelf/libelf-private.h
xen/common/libelf/libelf-tools.c
xen/common/list_sort.c
xen/common/lz4/decompress.c
xen/common/lz4/defs.h
xen/common/lzo.c
xen/common/memory.c
xen/common/multicall.c
xen/common/notifier.c
xen/common/page_alloc.c
xen/common/pdx.c
xen/common/perfc.c
xen/common/preempt.c
xen/common/radix-tree.c
xen/common/random.c
xen/common/rangeset.c
xen/common/rbtree.c
xen/common/rcupdate.c
xen/common/rwlock.c
xen/common/shutdown.c
xen/common/smp.c
xen/common/softirq.c
xen/common/sort.c
xen/common/spinlock.c
xen/common/stop_machine.c
xen/common/string.c
xen/common/symbols-dummy.c
xen/common/symbols.c
xen/common/sysctl.c
xen/common/tasklet.c
xen/common/time.c
xen/common/timer.c
xen/common/ubsan/Makefile
xen/common/ubsan/ubsan.c
xen/common/ubsan/ubsan.h
xen/common/unlz4.c
xen/common/unlzma.c
xen/common/unlzo.c
xen/common/unxz.c
xen/common/version.c
xen/common/virtual_region.c
xen/common/vmap.c
xen/common/vsprintf.c
xen/common/wait.c
xen/common/warning.c
xen/common/xenoprof.c
xen/common/xmalloc_tlsf.c
xen/common/xz/crc32.c
xen/common/xz/dec_bcj.c
xen/common/xz/dec_lzma2.c
xen/common/xz/dec_stream.c
xen/common/xz/lzma2.h
xen/common/xz/private.h
xen/common/xz/stream.h
xen/crypto/Makefile
xen/crypto/README.source
xen/crypto/rijndael.c
xen/crypto/vmac.c
xen/drivers/Kconfig
xen/drivers/Makefile
xen/drivers/char/Kconfig
xen/drivers/char/Makefile
xen/drivers/char/console.c
xen/drivers/char/consoled.c
xen/drivers/char/ehci-dbgp.c
xen/drivers/char/ns16550.c
xen/drivers/char/serial.c
xen/drivers/char/xen_pv_console.c
xen/drivers/pci/Kconfig
xen/drivers/pci/Makefile
xen/drivers/pci/pci.c
xen/drivers/video/Kconfig
xen/drivers/video/Makefile
xen/drivers/video/font.h
xen/drivers/video/font_8x14.c
xen/drivers/video/font_8x16.c
xen/drivers/video/font_8x8.c
xen/drivers/video/lfb.c
xen/drivers/video/lfb.h
xen/drivers/video/modelines.h
xen/drivers/video/vesa.c
xen/drivers/video/vga.c
xen/include/Makefile
xen/include/crypto/README.source
xen/include/crypto/rijndael.h
xen/include/crypto/vmac.h
xen/include/public/COPYING
xen/include/public/arch-x86_32.h
xen/include/public/arch-x86_64.h
xen/include/public/callback.h
xen/include/public/device_tree_defs.h
xen/include/public/dom0_ops.h
xen/include/public/domctl.h
xen/include/public/elfnote.h
xen/include/public/errno.h
xen/include/public/event_channel.h
xen/include/public/features.h
xen/include/public/grant_table.h
xen/include/public/hvm/dm_op.h
xen/include/public/hvm/e820.h
xen/include/public/hvm/hvm_info_table.h
xen/include/public/hvm/hvm_op.h
xen/include/public/hvm/hvm_vcpu.h
xen/include/public/hvm/hvm_xs_strings.h
xen/include/public/hvm/params.h
xen/include/public/hvm/pvdrivers.h
xen/include/public/hvm/save.h
xen/include/public/hypfs.h
xen/include/public/kexec.h
xen/include/public/memory.h
xen/include/public/nmi.h
xen/include/public/physdev.h
xen/include/public/platform.h
xen/include/public/pmu.h
xen/include/public/sched.h
xen/include/public/sysctl.h
xen/include/public/tmem.h
xen/include/public/trace.h
xen/include/public/vcpu.h
xen/include/public/version.h
xen/include/public/xen-compat.h
xen/include/public/xen.h
xen/include/public/xencomm.h
xen/include/public/xenoprof.h
xen/include/public/xsm/flask_op.h
xen/include/xen/8250-uart.h
xen/include/xen/acpi.h
xen/include/xen/atomic.h
xen/include/xen/bitmap.h
xen/include/xen/bitops.h
xen/include/xen/byteorder/big_endian.h
xen/include/xen/byteorder/generic.h
xen/include/xen/byteorder/little_endian.h
xen/include/xen/byteorder/swab.h
xen/include/xen/cache.h
xen/include/xen/compat.h
xen/include/xen/compile.h.in
xen/include/xen/compiler.h
xen/include/xen/config.h
xen/include/xen/console.h
xen/include/xen/consoled.h
xen/include/xen/const.h
xen/include/xen/coverage.h
xen/include/xen/cper.h
xen/include/xen/cpu.h
xen/include/xen/cpuidle.h
xen/include/xen/cpumask.h
xen/include/xen/ctype.h
xen/include/xen/decompress.h
xen/include/xen/delay.h
xen/include/xen/dmi.h
xen/include/xen/domain.h
xen/include/xen/domain_page.h
xen/include/xen/early_printk.h
xen/include/xen/earlycpio.h
xen/include/xen/efi.h
xen/include/xen/elf.h
xen/include/xen/elfcore.h
xen/include/xen/elfstructs.h
xen/include/xen/err.h
xen/include/xen/errno.h
xen/include/xen/event.h
xen/include/xen/event_fifo.h
xen/include/xen/gdbstub.h
xen/include/xen/grant_table.h
xen/include/xen/guest_access.h
xen/include/xen/gunzip.h
xen/include/xen/hash.h
xen/include/xen/hypercall.h
xen/include/xen/hypfs.h
xen/include/xen/init.h
xen/include/xen/inttypes.h
xen/include/xen/iocap.h
xen/include/xen/irq.h
xen/include/xen/irq_cpustat.h
xen/include/xen/kconfig.h
xen/include/xen/kernel.h
xen/include/xen/kexec.h
xen/include/xen/keyhandler.h
xen/include/xen/kimage.h
xen/include/xen/lib.h
xen/include/xen/libelf.h
xen/include/xen/list.h
xen/include/xen/list_sort.h
xen/include/xen/lz4.h
xen/include/xen/lzo.h
xen/include/xen/mm.h
xen/include/xen/multiboot.h
xen/include/xen/multiboot2.h
xen/include/xen/multicall.h
xen/include/xen/nodemask.h
xen/include/xen/nospec.h
xen/include/xen/notifier.h
xen/include/xen/numa.h
xen/include/xen/p2m-common.h
xen/include/xen/page-defs.h
xen/include/xen/paging.h
xen/include/xen/param.h
xen/include/xen/pci.h
xen/include/xen/pci_ids.h
xen/include/xen/pci_regs.h
xen/include/xen/pdx.h
xen/include/xen/percpu.h
xen/include/xen/perfc.h
xen/include/xen/perfc_defn.h
xen/include/xen/pfn.h
xen/include/xen/pmstat.h
xen/include/xen/preempt.h
xen/include/xen/prefetch.h
xen/include/xen/pv_console.h
xen/include/xen/radix-tree.h
xen/include/xen/random.h
xen/include/xen/rangeset.h
xen/include/xen/rbtree.h
xen/include/xen/rcupdate.h
xen/include/xen/rwlock.h
xen/include/xen/sched.h
xen/include/xen/serial.h
xen/include/xen/shared.h
xen/include/xen/shutdown.h
xen/include/xen/sizes.h
xen/include/xen/smp.h
xen/include/xen/softirq.h
xen/include/xen/sort.h
xen/include/xen/spinlock.h
xen/include/xen/stdarg.h
xen/include/xen/stdbool.h
xen/include/xen/stop_machine.h
xen/include/xen/string.h
xen/include/xen/stringify.h
xen/include/xen/symbols.h
xen/include/xen/tasklet.h
xen/include/xen/time.h
xen/include/xen/timer.h
xen/include/xen/types.h
xen/include/xen/typesafe.h
xen/include/xen/version.h
xen/include/xen/vga.h
xen/include/xen/video.h
xen/include/xen/virtual_region.h
xen/include/xen/vmap.h
xen/include/xen/wait.h
xen/include/xen/warning.h
xen/include/xen/watchdog.h
xen/include/xen/xenoprof.h
xen/include/xen/xmalloc.h
xen/include/xlat.lst
xen/lib/Makefile
xen/scripts/Kbuild.include
xen/scripts/Kconfig.include
xen/scripts/Makefile.clean
xen/scripts/clang-version.sh
xen/scripts/gcc-version.sh
xen/test/Makefile
xen/tools/Makefile
xen/tools/binfile
xen/tools/compat-build-header.py
xen/tools/compat-build-source.py
xen/tools/gen-cpuid.py
xen/tools/get-fields.sh
xen/tools/process-banner.sed
xen/tools/scmversion
xen/tools/symbols.c
xen/tools/xen.flf

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Followup of yesterday's design session "refactoring the REST"
  2020-07-09  5:56 Followup of yesterday's design session "refactoring the REST" Jürgen Groß
@ 2020-07-09  9:22 ` Jan Beulich
  2020-07-10 12:11   ` Jürgen Groß
  2020-07-09  9:34 ` Roger Pau Monné
  1 sibling, 1 reply; 4+ messages in thread
From: Jan Beulich @ 2020-07-09  9:22 UTC (permalink / raw)
  To: Jürgen Groß; +Cc: xen-devel

On 09.07.2020 07:56, Jürgen Groß wrote:
> Yesterday's design session at Xen Developer Summit "Hypervisor Team: .."
> had one topic regarding whether we should find specific maintainers of
> all the files currently assigned to "THE REST" in order to lower the
> amount of reviews for those assigned to be "THE REST" maintainers.
> 
> Modifying the MAINTAINERS file adding "REST@x.y" as REST maintainer
> and running the rune:
> 
> git ls-files | while true; do f=`line`; [ "$f" = "" ] && exit; \
> echo $f `./scripts/get_maintainer.pl -f $f | awk '{print $(NF)}'`; \
> done | awk '/REST/ { print $1}'
> 
> shows that basically the following files are covered by "THE REST":
> 
> - files directly in /
> - config/
> - most files in docs/ (not docs/man/)
> - misc/ (only one file)
> - scripts/
> - lots of files in xen/common/
> - xen/crypto/
> - lots of files in xen/drivers/
> - lots of files in xen/include/
> - xen/scripts/
> - some files in xen/tools/
> 
> I have attached the file list.
> 
> So the basic idea to have a "hypervisor REST" and a "tools REST"
> wouldn't make a huge difference, if we don't assign docs/ to "tools
> REST".
> 
> So I think it would make sense to:
> 
> - look through the docs/ and xen/include/ files whether some of those
>    can be assigned to a component already having dedicated maintainers
> 
> - try to find maintainers for the other files, especially those in
>    xen/common/ and xen/drivers/ (including the related include files, of
>    course)

At least for files in xen/common/ I think it was really intentional
that they - as core hypervisor files - fall under THE REST. We could
of course have a "Core Hypervisor" (or so) group, which would already
...

> - if any of the REST maintainers doesn't want to receive mails for a
>    group of the remaining REST files split the REST maintainers/files up
>    accordingly

... allow moving some into this direction.

For files under xen/drivers/ not currently covered by other entries it
may indeed be (more) feasible to find individual maintainers.

Jan


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Followup of yesterday's design session "refactoring the REST"
  2020-07-09  5:56 Followup of yesterday's design session "refactoring the REST" Jürgen Groß
  2020-07-09  9:22 ` Jan Beulich
@ 2020-07-09  9:34 ` Roger Pau Monné
  1 sibling, 0 replies; 4+ messages in thread
From: Roger Pau Monné @ 2020-07-09  9:34 UTC (permalink / raw)
  To: Jürgen Groß; +Cc: xen-devel

On Thu, Jul 09, 2020 at 07:56:58AM +0200, Jürgen Groß wrote:
> Yesterday's design session at Xen Developer Summit "Hypervisor Team: .."
> had one topic regarding whether we should find specific maintainers of
> all the files currently assigned to "THE REST" in order to lower the
> amount of reviews for those assigned to be "THE REST" maintainers.
> 
> Modifying the MAINTAINERS file adding "REST@x.y" as REST maintainer
> and running the rune:
> 
> git ls-files | while true; do f=`line`; [ "$f" = "" ] && exit; \
> echo $f `./scripts/get_maintainer.pl -f $f | awk '{print $(NF)}'`; \
> done | awk '/REST/ { print $1}'
> 
> shows that basically the following files are covered by "THE REST":
> 
> - files directly in /
> - config/
> - most files in docs/ (not docs/man/)
> - misc/ (only one file)
> - scripts/
> - lots of files in xen/common/
> - xen/crypto/
> - lots of files in xen/drivers/
> - lots of files in xen/include/
> - xen/scripts/
> - some files in xen/tools/
> 
> I have attached the file list.

Thanks! I still have to go over the list in more detail, just some
comments below.

> So the basic idea to have a "hypervisor REST" and a "tools REST"
> wouldn't make a huge difference, if we don't assign docs/ to "tools
> REST".
> 
> So I think it would make sense to:
> 
> - look through the docs/ and xen/include/ files whether some of those
>   can be assigned to a component already having dedicated maintainers
> 
> - try to find maintainers for the other files, especially those in
>   xen/common/ and xen/drivers/ (including the related include files, of
>   course)

I think it's important that xen/common files (specially the ones
containing interfaces exposed to guests) have at least one maintainer
from each supported architecture (Arm and x86 ATM), plus whatever
common code maintainers we want to have. It's sometimes easy (at least
for me) to forget about other arches or make wrong assumptions about
them when modifying common code.

Drivers could also benefit from something similar IMO, where common
code has a shared group of maintainers, for example IOMMU should
ideally have a mix of maintainers from the current implementations
(Arm/Intel/AMD) plus again whatever common code maintainers we want
to have.

Roger.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Followup of yesterday's design session "refactoring the REST"
  2020-07-09  9:22 ` Jan Beulich
@ 2020-07-10 12:11   ` Jürgen Groß
  0 siblings, 0 replies; 4+ messages in thread
From: Jürgen Groß @ 2020-07-10 12:11 UTC (permalink / raw)
  To: Jan Beulich; +Cc: xen-devel

On 09.07.20 11:22, Jan Beulich wrote:
> On 09.07.2020 07:56, Jürgen Groß wrote:
>> Yesterday's design session at Xen Developer Summit "Hypervisor Team: .."
>> had one topic regarding whether we should find specific maintainers of
>> all the files currently assigned to "THE REST" in order to lower the
>> amount of reviews for those assigned to be "THE REST" maintainers.
>>
>> Modifying the MAINTAINERS file adding "REST@x.y" as REST maintainer
>> and running the rune:
>>
>> git ls-files | while true; do f=`line`; [ "$f" = "" ] && exit; \
>> echo $f `./scripts/get_maintainer.pl -f $f | awk '{print $(NF)}'`; \
>> done | awk '/REST/ { print $1}'
>>
>> shows that basically the following files are covered by "THE REST":
>>
>> - files directly in /
>> - config/
>> - most files in docs/ (not docs/man/)
>> - misc/ (only one file)
>> - scripts/
>> - lots of files in xen/common/
>> - xen/crypto/
>> - lots of files in xen/drivers/
>> - lots of files in xen/include/
>> - xen/scripts/
>> - some files in xen/tools/
>>
>> I have attached the file list.
>>
>> So the basic idea to have a "hypervisor REST" and a "tools REST"
>> wouldn't make a huge difference, if we don't assign docs/ to "tools
>> REST".
>>
>> So I think it would make sense to:
>>
>> - look through the docs/ and xen/include/ files whether some of those
>>     can be assigned to a component already having dedicated maintainers
>>
>> - try to find maintainers for the other files, especially those in
>>     xen/common/ and xen/drivers/ (including the related include files, of
>>     course)
> 
> At least for files in xen/common/ I think it was really intentional
> that they - as core hypervisor files - fall under THE REST. We could

Depends on the files. Those files are under xen/common/ as they are not
architecture dependent. I agree that many of those files are core
hypervisor files, but OTOH e.g. common/sched/core.c has dedicated
maintainers in spite of being a core file.

I don't think files like xen/common/gdbstub.c or xen/common/xenoprof.c
fall in this category, so revisiting the file list would surely be a
good idea.

> of course have a "Core Hypervisor" (or so) group, which would already
> ...
> 
>> - if any of the REST maintainers doesn't want to receive mails for a
>>     group of the remaining REST files split the REST maintainers/files up
>>     accordingly
> 
> ... allow moving some into this direction.

Yes.

> For files under xen/drivers/ not currently covered by other entries it
> may indeed be (more) feasible to find individual maintainers.

I agree.


Juergen


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-07-10 12:11 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-09  5:56 Followup of yesterday's design session "refactoring the REST" Jürgen Groß
2020-07-09  9:22 ` Jan Beulich
2020-07-10 12:11   ` Jürgen Groß
2020-07-09  9:34 ` Roger Pau Monné

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.