All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Guru Das Srinagesh <quic_gurus@quicinc.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] treewide: Update Guru Das Srinagesh's email address
Date: Tue, 15 Aug 2023 19:04:05 +0100	[thread overview]
Message-ID: <20230815180405.GG648357@google.com> (raw)
In-Reply-To: <20230803011016.GA1630536-robh@kernel.org>

On Wed, 02 Aug 2023, Rob Herring wrote:

> On Fri, Jul 28, 2023 at 08:54:16AM +0100, Lee Jones wrote:
> > On Thu, 27 Jul 2023, Guru Das Srinagesh wrote:
> > 
> > > Clean up my email address as the codeaurora.org address is not used
> > > anymore.
> > > 
> > > Signed-off-by: Guru Das Srinagesh <quic_gurus@quicinc.com>
> > > ---
> > >  Documentation/devicetree/bindings/extcon/qcom,pm8941-misc.yaml | 2 +-
> > >  Documentation/devicetree/bindings/mfd/qcom,pm8008.yaml         | 2 +-
> > 
> > 2 patches isn't exactly 'treewide'.
> > 
> > Anyway, since there are not dependencies between the changes, please
> > separate them out, one per subsystem.
> 
> I'm happy to take these patches via the DT tree. No real advantage to 
> creating more work to split up these trivial changes.

Sounds good.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2023-08-15 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  0:16 [PATCH] treewide: Update Guru Das Srinagesh's email address Guru Das Srinagesh
2023-07-28  6:03 ` Mukesh Ojha
2023-07-28  7:14   ` Guru Das Srinagesh
2023-07-28  7:54 ` Lee Jones
2023-08-03  1:10   ` Rob Herring
2023-08-15 18:04     ` Lee Jones [this message]
2023-08-03  1:10 ` Rob Herring

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=20230815180405.GG648357@google.com \
    --to=lee@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=quic_gurus@quicinc.com \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.