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
Date: Tue, 14 May 2024 09:05:40 -0700 [thread overview]
Message-ID: <20240514090540.23b79539@kernel.org> (raw)
In-Reply-To: <3werahgyztwoznysqijjk5nz25fexx7r2yas6osw4qqbb4k27c@euv6wu47seuv>
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
prev parent reply other threads:[~2024-05-14 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 1:30 [PATCH v3 0/2] Mark Ethernet devices on sa8775p as DMA-coherent Sagar Cheluvegowda
2024-05-08 1:31 ` [PATCH v3 1/2] arm64: dts: qcom: sa8775p: mark ethernet devices " Sagar Cheluvegowda
2024-05-08 18:39 ` Konrad Dybcio
2024-05-08 1:31 ` [PATCH v3 2/2] dt-bindings: net: qcom: ethernet: Allow dma-coherent Sagar Cheluvegowda
2024-05-08 7:01 ` Krzysztof Kozlowski
2024-05-08 18:45 ` [PATCH v3 0/2] Mark Ethernet devices on sa8775p as DMA-coherent Konrad Dybcio
2024-05-14 14:21 ` Andrew Halaney
2024-05-14 14:41 ` Jakub Kicinski
2024-05-14 15:11 ` Andrew Halaney
2024-05-14 16:05 ` Jakub Kicinski [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=20240514090540.23b79539@kernel.org \
--to=kuba@kernel.org \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bhupesh.sharma@linaro.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_scheluve@quicinc.com \
--cc=robh@kernel.org \
--cc=vkoul@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).