Received-SPF: pass (google.com: domain of linux-kernel+bounces-178907-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Tue, 14 May 2024 09:05:40 -0700
From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: Sagar Cheluvegowda <quic_scheluve@quicinc.com>, Bjorn Andersson
 <andersson@kernel.org>, Konrad Dybcio <konrad.dybcio@linaro.org>, Rob
 Herring <robh@kernel.org>, Krzysztof Kozlowski <krzk+dt@kernel.org>, Conor
 Dooley <conor+dt@kernel.org>, Bartosz Golaszewski
 <bartosz.golaszewski@linaro.org>, Vinod Koul <vkoul@kernel.org>, "David S.
 Miller" <davem@davemloft.net>, Eric Dumazet <edumazet@google.com>, Paolo
 Abeni <pabeni@redhat.com>, Bhupesh Sharma <bhupesh.sharma@linaro.org>,
 kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
 netdev@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Mark Ethernet devices on sa8775p as DMA-coherent
Message-ID: <20240514090540.23b79539@kernel.org>
In-Reply-To: <3werahgyztwoznysqijjk5nz25fexx7r2yas6osw4qqbb4k27c@euv6wu47seuv>
References: <20240507-mark_ethernet_devices_dma_coherent-v3-0-dbe70d0fa971@quicinc.com>
	<5z22b7vrugyxqj7h25qevyd5aj5tsofqqyxqn7mfy4dl4wk7zw@fipvp44y4kbb>
	<20240514074142.007261f2@kernel.org>
	<3werahgyztwoznysqijjk5nz25fexx7r2yas6osw4qqbb4k27c@euv6wu47seuv>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 14 May 2024 10:11:35 -0500 Andrew Halaney wrote:
> But ignoring that, let me know if there's a good way to know who really
> picks things up outside of experience contributing. It's Sagar's first
> submission upstream, etc, so I've been fielding some first time
> contribution questions and realized I didn't have a good answer to that
> other than troll through lkml or the git log and see who picked those up
> in the past!

I'm not sure how well define it is to be honest. MAINTAINERS is focused
a bit too much on CCing people rather than code flow. Which hurts us in
more than one way. I _think_ the right way to find the responsible tree
is to do an longest prefix match on the path in MAINTAINERS, looking
just at the entries which have a T: attribute. (Q: attribute for that
entry may also be useful.) In practice I myself usually look at:

	git log --format=committer -- $path

where:

[pretty]
	committer = %<(20)%cn %cs  %<(47,trunc)%s