From: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
To: Vikash Garodia <quic_vgarodia@quicinc.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
Subject: [PATCH 0/2] media: update Dikshita Agarwal's email address
Date: Mon, 01 Sep 2025 13:03:27 +0530 [thread overview]
Message-ID: <20250901-update-email-v1-0-8fd49d58c0e5@oss.qualcomm.com> (raw)
I am switching to dikshita.agarwal@oss.qualcomm.com for my patch
submissions as the quic_dikshita@quicinc.com will go away in some time,
update all my emails in the code accordingly.
Signed-off-by: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
---
Dikshita Agarwal (2):
MAINTAINERS: update Dikshita Agarwal's email addresses
Documentation: media: update Dikshita Agarwal's email address
Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml | 2 +-
MAINTAINERS | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
---
base-commit: dffd279a8aa36479d127766e15fa817830387aba
change-id: 20250901-update-email-e4e7aaf42f71
Best regards,
--
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
next reply other threads:[~2025-09-01 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 7:33 Dikshita Agarwal [this message]
2025-09-01 7:33 ` [PATCH 1/2] MAINTAINERS: update Dikshita Agarwal's email addresses Dikshita Agarwal
2025-09-01 8:46 ` Bryan O'Donoghue
2025-09-01 7:33 ` [PATCH 2/2] Documentation: media: update Dikshita Agarwal's email address Dikshita Agarwal
2025-09-01 8:46 ` Bryan O'Donoghue
2025-09-02 8:29 ` Krzysztof Kozlowski
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=20250901-update-email-v1-0-8fd49d58c0e5@oss.qualcomm.com \
--to=dikshita.agarwal@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_vgarodia@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 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 NNTP newsgroup(s).