From: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH v2 4/7] irqchip/renesas-rzv2h: Add rzv2h_icu_register_dma_req_ack
Date: Tue, 18 Feb 2025 22:10:45 +0000 [thread overview]
Message-ID: <TYCPR01MB12093F3EB265A8C315799DAC4C2FA2@TYCPR01MB12093.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <87a5ajk7hr.ffs@tglx>
Hi Thomas,
Thanks for your feedback!
> From: Thomas Gleixner <tglx@linutronix.de>
> Sent: 18 February 2025 08:00
> Subject: Re: [PATCH v2 4/7] irqchip/renesas-rzv2h: Add rzv2h_icu_register_dma_req_ack
>
> On Wed, Feb 12 2025 at 22:13, Fabrizio Castro wrote:
> > On the Renesas RZ/V2H(P) family of SoCs, DMAC IPs are connected
> > to the Interrupt Control Unit (ICU).
> > For DMA transfers, a request number and an ack number must be
> > registered with the ICU, which means that the DMAC driver has
> > to be able to instruct the ICU driver with the registration of
> > such ids.
> >
> > Export rzv2h_icu_register_dma_req_ack so that the DMA driver
> > can register both ids in one go.
>
> Please denote functions in the subject and change log body as fun()
> according to documentation:
Thanks for pointing this out. I'll address it in the next version.
Cheers,
Fab
>
> https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#function-references-in-changelogs
>
> With that fixed:
>
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
>
> under the assumption that this will be merged via the dmaengine tree.
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2025-02-18 22:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 22:12 [PATCH v2 0/7] Add DMAC support to the RZ/V2H(P) Fabrizio Castro
2025-02-12 22:12 ` [PATCH v2 1/7] clk: renesas: r9a09g057: Add entries for the DMACs Fabrizio Castro
2025-02-12 22:13 ` [PATCH v2 2/7] dt-bindings: dma: rz-dmac: Restrict properties for RZ/A1H Fabrizio Castro
2025-02-12 22:13 ` [PATCH v2 3/7] dt-bindings: dma: rz-dmac: Document RZ/V2H(P) family of SoCs Fabrizio Castro
2025-02-12 22:13 ` [PATCH v2 4/7] irqchip/renesas-rzv2h: Add rzv2h_icu_register_dma_req_ack Fabrizio Castro
2025-02-18 8:00 ` Thomas Gleixner
2025-02-18 22:10 ` Fabrizio Castro [this message]
2025-02-12 22:13 ` [PATCH v2 5/7] dmaengine: sh: rz-dmac: Allow for multiple DMACs Fabrizio Castro
2025-02-12 22:13 ` [PATCH v2 6/7] dmaengine: sh: rz-dmac: Add RZ/V2H(P) support Fabrizio Castro
2025-02-13 13:24 ` kernel test robot
2025-02-13 14:19 ` Geert Uytterhoeven
2025-02-13 14:23 ` Geert Uytterhoeven
2025-02-18 20:40 ` Fabrizio Castro
2025-02-18 20:39 ` Fabrizio Castro
2025-02-12 22:13 ` [PATCH v2 7/7] arm64: dts: renesas: r9a09g057: Add DMAC nodes Fabrizio Castro
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=TYCPR01MB12093F3EB265A8C315799DAC4C2FA2@TYCPR01MB12093.jpnprd01.prod.outlook.com \
--to=fabrizio.castro.jz@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tglx@linutronix.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®