From: Christoph Hellwig <hch@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Lee Jones <lee.jones@linaro.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>, Greg KH <greg@kroah.com>,
Stephen Hemminger <stephen@networkplumber.org>,
ksummit@lists.linux.dev, Lee Jones <lee@kernel.org>
Subject: Re: Validating MAINTAINERS entries?
Date: Thu, 11 Aug 2022 01:42:21 -0700 [thread overview]
Message-ID: <YvTA7RiAx77zTnYc@infradead.org> (raw)
In-Reply-To: <CAMuHMdV2Ktw5h3Bvsc6iCq8mxLG+yf5BVXLvJts1MboD=eHgaQ@mail.gmail.com>
On Thu, Aug 11, 2022 at 10:35:52AM +0200, Geert Uytterhoeven wrote:
> Perhaps scripts/get_maintainer.pl can be taught to only consider the
> subsystem maintainer, and ignore git history, for changes to Makefiles
> and Kconfig files?
In general looking at git history is pretty much always the wrong thing,
except maybe for the initial commit.
> Or move the Kconfig/Makefile bits into the driver sources, next to
> the MODULE_*() bits, which I believe was part of Roman Zippel's big
> plan when he wrote the new Kconfig system...
I don't think having Kconfig in source files is a good thing. Being
able to integrate the Makefile into Kconfig OTOH would be really nice..
config FOOBAR
tristate 'Foo driver'
depends on PCI
help
This is the driver for the foo hardware.
module foo
sources foo_core.c foo_sysfs.c foo_debugfs.c
next prev parent reply other threads:[~2022-08-11 8:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 0:13 Validating MAINTAINERS entries? Stephen Hemminger
2022-08-10 8:23 ` Greg KH
2022-08-10 8:26 ` Dan Carpenter
2022-08-10 8:36 ` Greg KH
2022-08-10 8:55 ` Lukas Bulwahn
2022-08-10 9:10 ` Dan Carpenter
2022-08-10 11:50 ` Lee Jones
2022-08-10 12:04 ` Dan Carpenter
2022-08-10 12:12 ` Serge E. Hallyn
2022-08-10 12:50 ` Mark Brown
2022-08-10 13:25 ` Lee Jones
2022-08-10 13:54 ` Rob Herring
2022-08-10 14:01 ` Mark Brown
2022-08-10 14:19 ` Konstantin Ryabitsev
2022-08-10 14:20 ` Rob Herring
2022-08-10 14:35 ` Mark Brown
2022-08-11 12:36 ` Sudip Mukherjee
2022-08-10 15:29 ` Lee Jones
2022-08-11 8:35 ` Geert Uytterhoeven
2022-08-11 8:42 ` Christoph Hellwig [this message]
2022-08-10 8:46 ` Lukas Bulwahn
2022-08-10 8:42 ` Lukas Bulwahn
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=YvTA7RiAx77zTnYc@infradead.org \
--to=hch@infradead.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=ksummit@lists.linux.dev \
--cc=lee.jones@linaro.org \
--cc=lee@kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=stephen@networkplumber.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