Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	Devarsh Thakkar <devarsht@ti.com>,
	Jai Luthra <jai.luthra@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH 17/19] media: dt-bindings: ti,ds90ub960: Add "i2c-addr" link property
Date: Wed, 15 Jan 2025 21:25:46 +0100	[thread overview]
Message-ID: <a869e66e-4fb0-49b6-9307-9a20c73cb374@kernel.org> (raw)
In-Reply-To: <b083ab17-a34e-42cf-9696-ff774731dc58@ideasonboard.com>

On 15/01/2025 18:19, Tomi Valkeinen wrote:
> Hi,
> 
> On 15/01/2025 10:40, Krzysztof Kozlowski wrote:
> 
>>>> Why only these folks? Why not all of the maintainers?
>>>
>>> The whole series is sent to the media list and maintainers. I thought
>>> this single patch doesn't warrant sending the whole series to DT list
>>> and maintainers, so I cc'd them here.
>>
>>
>> I was wondering why only some of the DT maintainers, not all? My usual
>> assumption is: you are not using get_maintainers.pl or you are working
>> on an old kernel.
> 
> It's simpler than that: a copy-paste mistake. I'm not sure how I managed 
> to miss Conor there.
> 
> Any preference on cc'ing the DT maintainers and the dt-list only for 
> this patch (I'll use --- this time, I promise!), or just sending the 
> whole series also to DT people?
I think only Rob uses DT list entirely. I use both - DT list and being
directly CC-ed on emails, and I think Conor relies on being Cc-ed
directly. IOW, just cc all maintainers + DT list. Unless you touch
multiple subsystems, there is rarely a point to strip get_maintainers.pl
output from maintainers/reviewers/submitters. Do not confuse in skipping
non-maintainers pointed by Git-fallback (not applicable to b4, I think),
because these should be used carefully.

Best regards,
Krzysztof

  reply	other threads:[~2025-01-15 20:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  9:14 [PATCH 00/19] media: i2c: ds90ub9xx: Error handling, UB9702 improvements Tomi Valkeinen
2025-01-10  9:14 ` [PATCH 17/19] media: dt-bindings: ti,ds90ub960: Add "i2c-addr" link property Tomi Valkeinen
2025-01-11 10:31   ` Krzysztof Kozlowski
2025-01-14 11:50     ` Tomi Valkeinen
2025-01-15  8:40       ` Krzysztof Kozlowski
2025-01-15 17:19         ` Tomi Valkeinen
2025-01-15 20:25           ` Krzysztof Kozlowski [this message]
2025-01-15 15:53       ` Konstantin Ryabitsev
2025-01-15 16:09         ` Tomi Valkeinen
2025-01-15 16:46           ` Krzysztof Kozlowski
2025-01-15 17:14             ` Tomi Valkeinen

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=a869e66e-4fb0-49b6-9307-9a20c73cb374@kernel.org \
    --to=krzk@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jai.luthra@ideasonboard.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tomi.valkeinen@ideasonboard.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