mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Joshua Crofts" <joshua.crofts1@gmail.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add mailing list to veml3328 entry
Date: Sun, 26 Jul 2026 19:22:37 +0100	[thread overview]
Message-ID: <20260726192237.17cd42ef@jic23-huawei> (raw)
In-Reply-To: <2d168bc5-1410-4771-923d-229041913c88@kernel.org>

On Sun, 26 Jul 2026 13:31:16 +0200
Krzysztof Kozlowski <krzk@kernel.org> wrote:

> On 25/07/2026 00:43, Jonathan Cameron wrote:
> > On Tue, 21 Jul 2026 16:28:19 +0200
> > Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> >   
> >> Add the IIO mailing list to VEML3328 entry in MAINTAINERS, as it is
> >> standard to do so.
> >>
> >> Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>  
> > Hmm. ok I guess, but I can't say I'm enthusiastic about this sort of
> > entry by entry update.
> >   
> 
> No, this is just wrong, please don't do this. The subsystem defines the
> list and tree. Individual drivers should not duplicate the information.
> 
> This is just not only pointless churn but ACTUAL information
> duplication, which is never a positive thing.
> 
I'll drop this, though I think there are arguments both ways on simplicity
vs duplication of info.  Anyhow, I also don't want to see mass patches
removing these lists from subsystem entries without a clear consensus on that
being worth the churn.

> Best regards,
> Krzysztof


      reply	other threads:[~2026-07-26 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 14:28 Joshua Crofts
2026-07-24 22:43 ` Jonathan Cameron
2026-07-26 11:31   ` Krzysztof Kozlowski
2026-07-26 18:22     ` Jonathan Cameron [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=20260726192237.17cd42ef@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=joshua.crofts1@gmail.com \
    --cc=krzk@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    /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®