All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zong Li <zongbox@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Conor.Dooley@microchip.com, green.wan@sifive.com,
	vkoul@kernel.org, robh+dt@kernel.org, krzk+dt@kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, geert@linux-m68k.org,
	alexandre.ghiti@canonical.com, palmer@sifive.com,
	dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: sifive: fu540-c000: align dma node name with dtschema
Date: Tue, 19 Apr 2022 20:18:47 +0800	[thread overview]
Message-ID: <CA+ZOyaiWPZm6TQ0H7mvOS6UqBtCy7R1GSJrZg1AmC=4xwVWxfg@mail.gmail.com> (raw)
In-Reply-To: <20b63bd8-b527-43e0-884d-bf9fe3cacb19@linaro.org>

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 於 2022年4月19日 週二 下午6:59寫道:
>
> On 19/04/2022 12:57, Conor.Dooley@microchip.com wrote:
> >>> Not sure that this one is actually needed Krzysztof, Zong Li has a fix
> >>> for this in his series of fixes for the sifive pdma:
> >>> https://lore.kernel.org/linux-riscv/edd72c0cca1ebceddc032ff6ec2284e3f48c5ad3.1648461096.git.zong.li@sifive.com/
> >>>
> >>> Maybe you could add your review to his version?
> >>
> >> Zong's Li patch was sent 10 days after my patch... [1] Why riscv DTS
> >> patches take so much time to pick up?
> >>
> >
> > Oh, my bad. I incorrectly assumed that that patch was present before v8,
> > I should've checked further back - sorry!
>
> No problem :)
>
> I don't mind Zong's patch to be taken although in general I believe more
> in FIFO (or FIF Served) style.
>

Hi all,
Thanks Conor brings me here. The patch 1 and 4 in my series has been
applied into dmaengine/next, but patch 2 and 3 should go by riscv
tree, so I guess that I could re-send the patch 2 based on top of
Krzysztof's patch, then let's drop the patch 2 & 3 of another
patchset. I will keep follow up here. Thanks all.

> Best regards,
> Krzysztof
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Zong Li <zongbox@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Conor.Dooley@microchip.com, green.wan@sifive.com,
	vkoul@kernel.org,  robh+dt@kernel.org, krzk+dt@kernel.org,
	paul.walmsley@sifive.com,  palmer@dabbelt.com,
	aou@eecs.berkeley.edu, geert@linux-m68k.org,
	 alexandre.ghiti@canonical.com, palmer@sifive.com,
	dmaengine@vger.kernel.org,  devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: sifive: fu540-c000: align dma node name with dtschema
Date: Tue, 19 Apr 2022 20:18:47 +0800	[thread overview]
Message-ID: <CA+ZOyaiWPZm6TQ0H7mvOS6UqBtCy7R1GSJrZg1AmC=4xwVWxfg@mail.gmail.com> (raw)
In-Reply-To: <20b63bd8-b527-43e0-884d-bf9fe3cacb19@linaro.org>

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 於 2022年4月19日 週二 下午6:59寫道:
>
> On 19/04/2022 12:57, Conor.Dooley@microchip.com wrote:
> >>> Not sure that this one is actually needed Krzysztof, Zong Li has a fix
> >>> for this in his series of fixes for the sifive pdma:
> >>> https://lore.kernel.org/linux-riscv/edd72c0cca1ebceddc032ff6ec2284e3f48c5ad3.1648461096.git.zong.li@sifive.com/
> >>>
> >>> Maybe you could add your review to his version?
> >>
> >> Zong's Li patch was sent 10 days after my patch... [1] Why riscv DTS
> >> patches take so much time to pick up?
> >>
> >
> > Oh, my bad. I incorrectly assumed that that patch was present before v8,
> > I should've checked further back - sorry!
>
> No problem :)
>
> I don't mind Zong's patch to be taken although in general I believe more
> in FIFO (or FIF Served) style.
>

Hi all,
Thanks Conor brings me here. The patch 1 and 4 in my series has been
applied into dmaengine/next, but patch 2 and 3 should go by riscv
tree, so I guess that I could re-send the patch 2 based on top of
Krzysztof's patch, then let's drop the patch 2 & 3 of another
patchset. I will keep follow up here. Thanks all.

> Best regards,
> Krzysztof
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2022-04-19 12:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 16:20 [PATCH 1/2] dt-bindings: dmaengine: sifive, fu540-c000: include generic schema Krzysztof Kozlowski
2022-03-18 16:20 ` [PATCH 1/2] dt-bindings: dmaengine: sifive,fu540-c000: " Krzysztof Kozlowski
2022-03-18 16:20 ` [PATCH 2/2] riscv: dts: sifive: fu540-c000: align dma node name with dtschema Krzysztof Kozlowski
2022-03-18 16:20   ` Krzysztof Kozlowski
2022-04-19 10:09   ` Krzysztof Kozlowski
2022-04-19 10:09     ` Krzysztof Kozlowski
2022-04-19 10:45     ` Conor.Dooley
2022-04-19 10:45       ` Conor.Dooley
2022-04-19 10:50       ` Krzysztof Kozlowski
2022-04-19 10:50         ` Krzysztof Kozlowski
2022-04-19 10:57         ` Conor.Dooley
2022-04-19 10:57           ` Conor.Dooley
2022-04-19 10:59           ` Krzysztof Kozlowski
2022-04-19 10:59             ` Krzysztof Kozlowski
2022-04-19 12:18             ` Zong Li [this message]
2022-04-19 12:18               ` Zong Li
2022-03-21 18:55 ` [PATCH 1/2] dt-bindings: dmaengine: sifive,fu540-c000: include generic schema Rob Herring
2022-03-21 18:55   ` Rob Herring

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='CA+ZOyaiWPZm6TQ0H7mvOS6UqBtCy7R1GSJrZg1AmC=4xwVWxfg@mail.gmail.com' \
    --to=zongbox@gmail.com \
    --cc=Conor.Dooley@microchip.com \
    --cc=alexandre.ghiti@canonical.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=green.wan@sifive.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.