mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] ARM: dts: stm32mp13: fix compatible for BSEC
Date: Thu, 27 Oct 2022 17:02:42 +0200	[thread overview]
Message-ID: <e25bd4c2-c0d1-2884-5bcf-93fe205c06a7@foss.st.com> (raw)
In-Reply-To: <c33c5490-c43d-17d5-f0fb-0b930dd46928@linaro.org>

Hi,

On 10/18/22 03:55, Krzysztof Kozlowski wrote:
> On 17/10/2022 07:44, Patrick Delaunay wrote:
>> Use the new compatible for stm32mp13 support.
>>
>> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
>> ---
>> This device tree modification depends on the binding modification
>> introduced by the patch:
>>
>> dt-bindings: nvmem: add new stm32mp13 compatible for stm32-romem
>> https://patchwork.kernel.org/project/linux-arm-kernel/patch/20221014172324.1.Ifc1812116ff63f5501f3edd155d3cf5c0ecc846c@changeid/
> This breaks users of DTS. The patch above did not describe devices as
> compatible and that's the problem sending patches separately, without
> context.
>
> You need to keep compatible.
>
> Best regards,
> Krzysztof

I will sent a V2 patch in a serie with binding change, driver updates 
and explanations.

Regards

Patrick


      reply	other threads:[~2022-10-27 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 11:44 Patrick Delaunay
2022-10-18  1:55 ` Krzysztof Kozlowski
2022-10-27 15:02   ` Patrick DELAUNAY [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=e25bd4c2-c0d1-2884-5bcf-93fe205c06a7@foss.st.com \
    --to=patrick.delaunay@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=robh+dt@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
all inboxes | Powered by JetHome®