From: Primoz Fiser <primoz.fiser@norik.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, upstream@lists.phytec.de
Subject: Re: [PATCH v2 0/2] ARM: dts: imx6: phytec-mira: phyBOARD-Mira fixes
Date: Thu, 1 Oct 2026 12:28:58 +0200 [thread overview]
Message-ID: <8a9299bf-4b92-4df2-89e5-eb8363e361b8@norik.com> (raw)
In-Reply-To: <CAOMZO5Aibmm3d=9Ucro0Tqvyh_s3EozLM25axV3XxeLuG67PCg@mail.gmail.com>
Hi Fabio,
On 10/1/26 12:14, Fabio Estevam wrote:
> Hi Primoz,
>
> On Thu, Oct 1, 2026 at 5:10 AM Primoz Fiser <primoz.fiser@norik.com> wrote:
>>
>> Two small fixes for the PHYTEC phyBOARD-Mira-i.MX6 boards:
>
> Shouldn't they have a Fixes tag, then?
For patch #1 it think it is pointless because those properties didn't
exist until aforementioned commit 888e5fad9b78 ("Input: stmpe - add axis
inversion and swapping capability"). So it is an addition not a fix as
commit message suggests.
For patch #2 I could add:
Fixes: 800d595151bb ("ARM: dts: imx6: Add initial support for
phyBOARD-Mira")
in v3 if you want?
BR,
Primoz
--
Primoz Fiser
phone: +386-41-390-545
email: primoz.fiser@norik.com
--
Norik systems d.o.o.
Your embedded software partner
Slovenia, EU
phone: +386-41-540-545
email: info@norik.com
prev parent reply other threads:[~2026-10-01 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 8:10 Primoz Fiser
2026-10-01 8:10 ` [PATCH v2 1/2] ARM: dts: imx6qdl-phytec-mira: Add touchscreen-inverted properties Primoz Fiser
2026-10-01 8:10 ` [PATCH v2 2/2] ARM: dts: imx6qdl-phytec-mira: Fix uart3 CTS/RTS pinmuxing Primoz Fiser
2026-10-01 10:14 ` [PATCH v2 0/2] ARM: dts: imx6: phytec-mira: phyBOARD-Mira fixes Fabio Estevam
2026-10-01 10:28 ` Primoz Fiser [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=8a9299bf-4b92-4df2-89e5-eb8363e361b8@norik.com \
--to=primoz.fiser@norik.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=upstream@lists.phytec.de \
/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
all inboxes | Powered by JetHome®