From: tessolveupstream@gmail.com
To: Krzysztof Kozlowski <krzk@kernel.org>,
andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 1/5] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform
Date: Wed, 7 Jan 2026 12:28:30 +0530 [thread overview]
Message-ID: <dce7702f-e845-4940-8679-a8d80563988a@gmail.com> (raw)
In-Reply-To: <d23e3693-0cf8-4b31-a3e4-e562621911d5@kernel.org>
On 05-01-2026 12:42, Krzysztof Kozlowski wrote:
> On 04/01/2026 14:11, tessolveupstream@gmail.com wrote:
>>
>>
>> On 30-12-2025 20:33, Krzysztof Kozlowski wrote:
>>> On 30/12/2025 14:02, Sudarshan Shetty wrote:
>>>> Add binding support for the Qualcomm Technologies, Inc. Talos EVK
>>>> SMARC platform based on the QCS615 SoC.
>>>>
>>>> Signed-off-by: Sudarshan Shetty <tessolveupstream@gmail.com>
>>>> ---
>>>
>>>
>>> Why did you decide to drop the tag and where did you explain that?
>>>
>>> <form letter>
>>> This is a friendly reminder during the review process.
>>>
>>> It looks like you received a tag and forgot to add it.
>>>
>>> If you do not know the process, here is a short explanation:
>>> Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
>>> of patchset, under or above your Signed-off-by tag, unless patch changed
>>> significantly (e.g. new properties added to the DT bindings). Tag is
>>> "received", when provided in a message replied to you on the mailing
>>> list. Tools like b4 can help here. However, there's no need to repost
>>> patches *only* to add the tags. The upstream maintainer will do that for
>>> tags received on the version they apply.
>>>
>>> Please read:
>>> https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
>>>
>>> If a tag was not added on purpose, please state why and what changed.
>>> </form letter>
>>>
>>
>> I apologize for missing the Acked-by tag in this version.
>
> How missing? It WAS THERE ALREADY!
>
> You had to explicitly remove it.
While updating the linux-next kernel source and reapplying the
changes, the Acked-by tag was inadvertently omitted. I’ll ensure
that all previously received tags are retained in future revisions
in accordance with the submission guidelines. My apologies for
the oversight.
>
>> I will make sure to include all received tags in the next patch
>> as per the submission guidelines.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2026-01-07 6:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 13:02 [PATCH v10 0/5] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2025-12-30 13:02 ` [PATCH v10 1/5] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-12-30 15:03 ` Krzysztof Kozlowski
2026-01-04 13:11 ` tessolveupstream
2026-01-05 7:12 ` Krzysztof Kozlowski
2026-01-07 6:58 ` tessolveupstream [this message]
2026-01-07 7:20 ` Krzysztof Kozlowski
2026-01-07 11:17 ` Konrad Dybcio
2026-01-14 6:53 ` tessolveupstream
2025-12-30 13:02 ` [PATCH v10 2/5] dt-bindings: backlight: gpio-backlight: allow multiple GPIOs Sudarshan Shetty
2026-01-05 15:52 ` Bjorn Andersson
2025-12-30 13:02 ` [PATCH v10 3/5] backlight: gpio: add support for multiple GPIOs for backlight control Sudarshan Shetty
2026-01-05 15:38 ` Bjorn Andersson
2026-01-07 5:57 ` tessolveupstream
2026-01-07 8:12 ` Dmitry Baryshkov
2025-12-30 13:02 ` [PATCH v10 4/5] arm64: dts: qcom: talos: Fix inconsistent USB PHY node naming Sudarshan Shetty
2025-12-30 14:42 ` Dmitry Baryshkov
2026-01-07 8:23 ` yuanjiey
2026-01-08 4:51 ` tessolveupstream
2025-12-30 13:02 ` [PATCH v10 5/5] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2025-12-30 14:45 ` Dmitry Baryshkov
2025-12-30 14:51 ` Konrad Dybcio
2026-01-04 13:46 ` tessolveupstream
2026-01-05 22:13 ` Dmitry Baryshkov
2026-01-06 7:30 ` tessolveupstream
2026-01-08 7:36 ` tessolveupstream
2026-01-08 8:36 ` Konrad Dybcio
2026-01-08 13:02 ` tessolveupstream
2026-01-08 13:06 ` Konrad Dybcio
2026-01-07 8:37 ` yuanjiey
2026-01-08 9:29 ` tessolveupstream
2026-01-08 13:14 ` Konrad Dybcio
2026-01-09 7:21 ` tessolveupstream
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=dce7702f-e845-4940-8679-a8d80563988a@gmail.com \
--to=tessolveupstream@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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