From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
tessolveupstream@gmail.com, 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:17:24 +0100 [thread overview]
Message-ID: <49ce6fee-36dd-4e0d-b2e2-b516b16a8b25@oss.qualcomm.com> (raw)
In-Reply-To: <d9267c08-4470-481c-b56b-390627e9e61e@kernel.org>
On 1/7/26 8:20 AM, Krzysztof Kozlowski wrote:
> On 07/01/2026 07:58, tessolveupstream@gmail.com wrote:
>>>>
>>>> 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.
>
>
> That's not how you work with your own code. You rebase onto new next and
> then only update trailers with b4.
JFYI Sudarshan, there is a neat oneliner to do this:
git rebase --onto linux-next/master $(git describe --abbrev=0)
where linux-next/master is the target commit/branch to rebase onto, and the
second argument is the pointer to the start of the chunk you want to rebase
Konrad
next prev parent reply other threads:[~2026-01-07 11:17 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
2026-01-07 7:20 ` Krzysztof Kozlowski
2026-01-07 11:17 ` Konrad Dybcio [this message]
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=49ce6fee-36dd-4e0d-b2e2-b516b16a8b25@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.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 \
--cc=tessolveupstream@gmail.com \
/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