public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: tessolveupstream@gmail.com
To: Rob Herring <robh@kernel.org>
Cc: andersson@kernel.org, konradybcio@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 v11 0/4] Add Qualcomm Technologies, Inc. Talos EVK SMARC support
Date: Wed, 14 Jan 2026 10:59:32 +0530	[thread overview]
Message-ID: <65f51660-a521-4803-ba7c-eacd53993982@gmail.com> (raw)
In-Reply-To: <20260112153134.GA215739-robh@kernel.org>



On 12-01-2026 21:01, Rob Herring wrote:
> On Fri, Jan 09, 2026 at 03:22:16PM +0530, Sudarshan Shetty wrote:
>> Hi all,
> 
> From the mail headers:
>> Content-Type: text/plain; charset=y                                                                        
>> Content-Transfer-Encoding: 8bit                                                                            
> 
> When git-send-email prompts you for which encoding to use, the correct 
> answer is not 'y'. The default utf-8 is correct, so just hit enter. 
> IIRC, newer git versions fixed this.
>

Okay, got it.
 
> Rob


      reply	other threads:[~2026-01-14  5:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  9:52 [PATCH v11 0/4] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2026-01-09  9:52 ` [PATCH v11 1/4] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2026-01-09  9:52 ` [PATCH v11 2/4] arm64: dts: qcom: talos: Fix inconsistent USB PHY node naming Sudarshan Shetty
2026-01-09  9:52 ` [PATCH v11 3/4] arm64: dts: qcom: qcs615-ride: Fix USB PHY label reference Sudarshan Shetty
2026-01-09  9:59   ` Konrad Dybcio
2026-01-14  5:23     ` tessolveupstream
2026-01-09  9:52 ` [PATCH v11 4/4] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2026-01-12  3:18   ` yuanjiey
2026-01-14  9:02     ` tessolveupstream
2026-01-15 13:17   ` Qian Zhang
2026-01-16  6:58     ` tessolveupstream
2026-01-16  7:56       ` Dmitry Baryshkov
2026-01-16 11:27         ` tessolveupstream
2026-01-16 11:49           ` Dmitry Baryshkov
2026-01-20 11:03             ` tessolveupstream
2026-01-20 22:57               ` Dmitry Baryshkov
2026-01-12 15:31 ` [PATCH v11 0/4] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Rob Herring
2026-01-14  5:29   ` tessolveupstream [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=65f51660-a521-4803-ba7c-eacd53993982@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=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