mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Duda <sebastian.duda@fau.de>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
	"Theodore Y. Ts'o" <tytso@mit.edu>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com
Subject: Re: Status of Subsystems
Date: Thu, 22 Aug 2019 12:54:09 +0200	[thread overview]
Message-ID: <f0022b73-6199-cff2-fe78-0818062ef5be@fau.de> (raw)
In-Reply-To: <57a7ae11-282f-8b93-355c-4bc839f76b23@metux.net>

Hi,

below is a list of files explicitly mentioned twice (or more) in the 
MAINTAINERS file.

Kind regards
Sebastian

On 21.08.19 14:10, Enrico Weigelt, metux IT consult wrote:
> On 20.08.19 19:15, Theodore Y. Ts'o wrote:
> 
> Hi,
> 
>> There are some files which have no official
>> owner, and there are also some files which may be modified by more
>> than one subsystem.
> 
> hmm, wouldn't it be better to alway have explicit maintainers ?
> 
> I recall some discussion few weeks ago on some of my patches, where it
> turned out that amm acts as fallback for a lot of code that doesn't have
> a maintainer.
> 
> @Sebastian: maybe you could also create reports for quickly identifying
> those cases.
> 
>> We certainly don't talk about "inheritance" when we talk about
>> maintainers and sub-maintainers. 
> 
> What's the exact definition of the term "sub-maintainer" ?
> 
> Somebody who's maintaining some defined part of something bigger
> (eg. a driver within some subsystem, some platform within some
> arch, etc) or kinda deputee maintainer ?
> 
>> Furthermore, the relationships,
>> processes, and workflows between a particular maintainer and their
>> submaintainers can be unique to a particular maintainer.
> 
> Can we somehow find some (semi-formal) description for those
> relationships and workflows, so it's easier to learn about them
> when some is new to some particular area ?
> 
> (I'd volounteer maintaining such documentation, if the individual
> maintainers feed me the necessary information ;-)).
> 
> 
> --mtx
> 

Documentation/security/keys/trusted-encrypted.rst
drivers/power/supply/bq27xxx_battery.c
tools/power/acpi/
include/linux/lockd/
net/sunrpc/
drivers/i2c/busses/i2c-qcom-geni.c
drivers/block/virtio_blk.c
Documentation/devicetree/bindings/mfd/atmel-usart.txt
Documentation/i2c/busses/i2c-ali1563
include/linux/hippidevice.h
Documentation/PCI/pci-error-recovery.rst
include/linux/vga*
fs/nfs_common/
include/linux/pm.h
drivers/crypto/virtio/
include/linux/mlx5/
drivers/media/tuners/tda8290.*
drivers/crypto/nx/Kconfig
arch/x86/include/asm/pvclock-abi.h
drivers/scsi/53c700*
fs/lockd/
drivers/staging/iio/
drivers/i2c/busses/i2c-omap.c
Documentation/admin-guide/ras.rst
include/acpi/
drivers/staging/greybus/spi.c
drivers/base/power/
include/uapi/linux/media.h
include/uapi/linux/cciss*.h
include/linux/suspend.h
include/uapi/linux/uvcvideo.h
include/trace/events/xdp.h
drivers/staging/greybus/spilib.c
include/linux/cfag12864b.h
Documentation/devicetree/bindings/arm/renesas.yaml
include/linux/soc/renesas/
Documentation/scsi/NinjaSCSI.txt
include/linux/sunrpc/
drivers/crypto/nx/Makefile
drivers/gpu/vga/
include/linux/platform_data/i2c-omap.h
drivers/power/supply/bq27xxx_battery_i2c.c
drivers/mtd/nand/raw/ingenic/
drivers/i2c/busses/i2c-ali1563.c
drivers/soc/renesas/
include/uapi/linux/sunrpc/
drivers/md/Makefile
include/linux/power/bq27xxx_battery.h
include/linux/dmaengine.h
drivers/gpio/gpio-intel-mid.c
drivers/dma/
include/uapi/linux/ivtv*
kernel/power/
drivers/gpio/gpio-ich.c
drivers/net/ethernet/ibm/ibmvnic.*
include/linux/netdevice.h
include/linux/mlx4/
drivers/net/ethernet/ibm/ibmveth.*
drivers/media/platform/mtk-vpu/
drivers/dma/dma-jz4780.c
include/uapi/linux/meye.h
include/uapi/linux/netdevice.h
arch/arm/plat-omap/
include/linux/freezer.h
include/linux/cciss*.h
Documentation/gpu/
drivers/md/Kconfig
include/linux/cpu_cooling.h
include/linux/pwm_backlight.h
arch/mips/include/asm/mach-loongson64/

  reply	other threads:[~2019-08-22 10:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 13:05 Sebastian Duda
2019-08-20 13:14 ` Pali Rohár
2019-08-20 13:56   ` Sebastian Duda
2019-08-20 14:05     ` Pali Rohár
2019-08-20 14:09     ` Joe Perches
2019-08-20 17:15     ` Theodore Y. Ts'o
2019-08-21 12:10       ` Enrico Weigelt, metux IT consult
2019-08-22 10:54         ` Sebastian Duda [this message]
2019-08-22 14:08         ` Theodore Y. Ts'o
2019-08-22  9:28       ` Sebastian Duda
2019-08-22 12:49         ` Enrico Weigelt, metux IT consult

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=f0022b73-6199-cff2-fe78-0818062ef5be@fau.de \
    --to=sebastian.duda@fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metux.net \
    --cc=lukas.bulwahn@gmail.com \
    --cc=pali.rohar@gmail.com \
    --cc=tytso@mit.edu \
    /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

all inboxes | Powered by JetHome®