Devicetree
 help / color / mirror / Atom feed
From: Konstantin Shabanov <mail@etehtsea.me>
To: konrad.dybcio@oss.qualcomm.com
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, mail@etehtsea.me, robh@kernel.org
Subject: Re: [PATCH v3 0/4] Introduce HONOR MagicBook Art 14 Snapdragon device tree
Date: Sun, 28 Jun 2026 15:20:05 +0700	[thread overview]
Message-ID: <20260628082005.40036-1-mail@etehtsea.me> (raw)
In-Reply-To: <2aed327e-abf6-401a-a05b-ba3f4a5cd7f3@oss.qualcomm.com>

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]).

[1]: https://linux-hardware.org/?view=computers&type=notebook&vendor=HONOR&model=MRA-XXX

  reply	other threads:[~2026-06-28  8:20 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     ` Konstantin Shabanov [this message]
2026-06-29  9:28       ` [PATCH v3 0/4] Introduce HONOR MagicBook Art 14 Snapdragon " Konrad Dybcio
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=20260628082005.40036-1-mail@etehtsea.me \
    --to=mail@etehtsea.me \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --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