devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: "xiangsheng.hou" <xiangsheng.hou@mediatek.com>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, bin.zhang@mediatek.com,
	benliang.zhao@mediatek.com, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 1/2] arm64: dts: mt8173: Fix nor_flash node
Date: Fri, 8 Jul 2022 10:22:51 +0200	[thread overview]
Message-ID: <184ce9e3-6031-98ab-cae6-a4aa2015b5c4@gmail.com> (raw)
In-Reply-To: <e4a50d4e165887ac4741c0b8d68470dc2f060655.camel@mediatek.com>



On 08/07/2022 03:40, xiangsheng.hou wrote:
> Hi Matthias,
> 
> On Thu, 2022-07-07 at 16:43 +0200, Matthias Brugger wrote:
>>
>> On 30/06/2022 11:01, Xiangsheng Hou wrote:
>>> Add axi clock since the driver change to DMA mode which need
>>> to enable axi clock. And change spi clock to 26MHz as default.
>>>
>>> Signed-off-by: Xiangsheng Hou <xiangsheng.hou@mediatek.com>
>>
>> Applied, thanks!
>>
> I will send a new patch v3 since there need a change in [PATCH v2 2/2]
> by review.
> 

Thanks from letting me know. From what I can see, 1/2 in v3 did not change, so 
as I already applied it, you could have dropped it from the series.

Please correct me if I'm wrong.

Best regards,
Matthias

  parent reply	other threads:[~2022-07-08  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  9:01 [PATCH v2 0/2] arm64: dts: mt8173: Fix nor flash node Xiangsheng Hou
2022-06-30  9:01 ` [PATCH v2 1/2] arm64: dts: mt8173: Fix nor_flash node Xiangsheng Hou
2022-07-07 14:43   ` Matthias Brugger
     [not found]     ` <e4a50d4e165887ac4741c0b8d68470dc2f060655.camel@mediatek.com>
2022-07-08  8:22       ` Matthias Brugger [this message]
2022-06-30  9:01 ` [PATCH v2 2/2] dt-bindings: mediatek: Add assigned clock property and axi clock in example Xiangsheng Hou
2022-06-30 18:41   ` Krzysztof Kozlowski

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=184ce9e3-6031-98ab-cae6-a4aa2015b5c4@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=benliang.zhao@mediatek.com \
    --cc=bin.zhang@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=xiangsheng.hou@mediatek.com \
    /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).