devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: linux-arm-kernel@lists.infradead.org, marex@denx.de
Cc: christophe.kerello@foss.st.com, robh+dt@kernel.org,
	mcoquelin.stm32@gmail.com, devicetree@vger.kernel.org,
	alexandre.torgue@foss.st.com,
	linux-stm32@st-md-mailman.stormreply.com,
	linus.walleij@linaro.org
Subject: Re: [PATCH] dt-bindings: memory-controller: st,stm32: Fix st,fmc2_ebi-cs-write-address-setup-ns
Date: Wed, 28 Sep 2022 09:12:48 +0200	[thread overview]
Message-ID: <c54f15a6-b4e6-d512-654f-28819eeaab4c@linaro.org> (raw)
In-Reply-To: <166434910296.10148.2597210651020575227.b4-ty@linaro.org>

On 28/09/2022 09:11, Krzysztof Kozlowski wrote:
> On Tue, 27 Sep 2022 00:20:03 +0200, Marek Vasut wrote:
>> The property st,fmc2_ebi-cs-write-address-setup-ns should really be
>> st,fmc2-ebi-cs-write-address-setup-ns (there is underscore _ between
>> fmc2 and ebi and there should be a dash - instead). This is a remnant
>> from conversion of old non-upstream bindings. Fix it.
>>
>>
> 
> Applied, thanks!
> 
> [1/1] dt-bindings: memory-controller: st,stm32: Fix st,fmc2_ebi-cs-write-address-setup-ns
>       https://git.kernel.org/krzk/linux-mem-ctrl/c/587f9891ec9661e16df7e5268543416a7d8cb547

Just a note: it's late for me in the cycle to pick up patches. I applied
this but there is a change it will miss this merge window. If that
happens, I will keep it for next cycle (no need to resend).

Best regards,
Krzysztof


  reply	other threads:[~2022-09-28  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 22:20 [PATCH] dt-bindings: memory-controller: st,stm32: Fix st,fmc2_ebi-cs-write-address-setup-ns Marek Vasut
2022-09-26 22:26 ` Rob Herring
2022-09-28  7:11 ` Krzysztof Kozlowski
2022-09-28  7:12   ` Krzysztof Kozlowski [this message]
2022-09-28 12:51     ` Marek Vasut

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=c54f15a6-b4e6-d512-654f-28819eeaab4c@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=christophe.kerello@foss.st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=marex@denx.de \
    --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;
as well as URLs for NNTP newsgroup(s).