linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Sean Wang <sean.wang@mediatek.com>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	LAK <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/3] dmaengine: Use platform_get_irq*() variants to fetch IRQ's
Date: Fri, 11 Mar 2022 16:06:38 +0530	[thread overview]
Message-ID: <YismNmydtp3KEmo+@matsya> (raw)
In-Reply-To: <CA+V-a8sRizPbhG1qrFy1SLhWWuL2AM4ZM68y_jb4cg0_G5VPUA@mail.gmail.com>

On 09-03-22, 11:37, Lad, Prabhakar wrote:
> Hi Sean/Vinod,
> 
> Not sure how I missed you to add in the To/CC list.
> 
> On Tue, Jan 4, 2022 at 4:35 PM Lad Prabhakar
> <prabhakar.mahadev-lad.rj@bp.renesas.com> wrote:
> >
> > Hi All,
> >
> > This patch series aims to drop using platform_get_resource() for IRQ types
> > in preparation for removal of static setup of IRQ resource from DT core
> > code.
> >
> > Dropping usage of platform_get_resource() was agreed based on
> > the discussion [0].
> >
> > [0] https://patchwork.kernel.org/project/linux-renesas-soc/
> > patch/20211209001056.29774-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
> >
> > Cheers,
> > Prabhakar
> >
> > Lad Prabhakar (3):
> >   dmaengine: nbpfaxi: Use platform_get_irq_optional() to get the
> >     interrupt
> >   dmaengine: mediatek: mtk-hsdma: Use platform_get_irq() to get the
> >     interrupt
> >   dmaengine: mediatek-cqdma: Use platform_get_irq() to get the interrupt
> >
> >  drivers/dma/mediatek/mtk-cqdma.c | 12 ++++--------
> >  drivers/dma/mediatek/mtk-hsdma.c | 11 ++++-------
> >  drivers/dma/nbpfaxi.c            | 14 ++++++--------
> >  3 files changed, 14 insertions(+), 23 deletions(-)
> >
> These patches aren't in -next yet. Do you want me to resend them?

Yes that would be ideal! But after upcoming merge window closes

-- 
~Vinod

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

      reply	other threads:[~2022-03-11 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 16:35 [PATCH v2 0/3] dmaengine: Use platform_get_irq*() variants to fetch IRQ's Lad Prabhakar
2022-01-04 16:35 ` [PATCH v2 2/3] dmaengine: mediatek: mtk-hsdma: Use platform_get_irq() to get the interrupt Lad Prabhakar
2022-01-06  5:27   ` Vinod Koul
2022-01-06  8:44     ` Lad, Prabhakar
2022-01-04 16:35 ` [PATCH v2 3/3] dmaengine: mediatek-cqdma: " Lad Prabhakar
2022-01-05  9:56 ` [PATCH v2 0/3] dmaengine: Use platform_get_irq*() variants to fetch IRQ's Andy Shevchenko
2022-03-09 11:37 ` Lad, Prabhakar
2022-03-11 10:36   ` Vinod Koul [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=YismNmydtp3KEmo+@matsya \
    --to=vkoul@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh+dt@kernel.org \
    --cc=sean.wang@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).