All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Konstantin Shabanov <mail@etehtsea.me>
Cc: andersson@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, konradybcio@kernel.org,
	krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 0/4] Introduce HONOR MagicBook Art 14 Snapdragon device tree
Date: Mon, 29 Jun 2026 11:28:15 +0200	[thread overview]
Message-ID: <77dd2139-d687-4c6f-b082-df325bc4cd4d@oss.qualcomm.com> (raw)
In-Reply-To: <20260628082005.40036-1-mail@etehtsea.me>

On 6/28/26 10:20 AM, Konstantin Shabanov wrote:
> On Wed, 24 Jun 2026 14:10:10 +0200, Konrad Dybcio wrote:
>>> +&iris {
>>> +	firmware-name = "qcom/x1e80100/HONOR/MRO-XXX/qcvss8380.mbn";
>>
>> Is that a model name, or a placeholder?
> Yes, this is a model name (Intel variant of this laptop has MRA-XXX [1]).

I'm a little surprised, but okay!

Konrad

  reply	other threads:[~2026-06-29  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-20 17:51 [PATCH v3 0/4] Introduce HONOR MagicBook Art 14 Snapdragon device tree Konstantin Shabanov
2026-06-20 17:51 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: Add HONOR Konstantin Shabanov
2026-06-20 17:51 ` [PATCH v3 2/4] dt-bindings: arm: qcom: Add HONOR MagicBook Art 14 Konstantin Shabanov
2026-06-20 17:51 ` [PATCH v3 3/4] arm64: dts: qcom: Add HONOR MagicBook Art 14 device tree Konstantin Shabanov
2026-06-20 18:11   ` sashiko-bot
2026-06-24 12:07   ` Konrad Dybcio
2026-06-24 12:10   ` Konrad Dybcio
2026-06-28  8:20     ` [PATCH v3 0/4] Introduce HONOR MagicBook Art 14 Snapdragon " Konstantin Shabanov
2026-06-29  9:28       ` Konrad Dybcio [this message]
2026-06-20 17:51 ` [PATCH v3 4/4] firmware: qcom: scm: Allow QSEECOM on Honor Magicbook Art 14 Konstantin Shabanov

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=77dd2139-d687-4c6f-b082-df325bc4cd4d@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=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@etehtsea.me \
    --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.