From: Inki Dae <inki.dae@samsung.com>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>
Subject: Re: [PATCH 0/5] drm/exynos: Use platform_get_irq*() variants to fetch IRQ's
Date: Fri, 14 Jan 2022 20:47:48 +0900 [thread overview]
Message-ID: <6f044839-e1d8-b9a8-90c3-7e929d498838@samsung.com> (raw)
In-Reply-To: <20211222190134.24866-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi,
21. 12. 23. 오전 4:01에 Lad Prabhakar 이(가) 쓴 글:
> 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/
>
Applied.
Thanks,
Inki Dae
> Cheers,
> Prabhakar
>
> Lad Prabhakar (5):
> drm/exynos/exynos7_drm_decon: Use platform_get_irq_byname() to get the
> interrupt
> drm/exynos: mixer: Use platform_get_irq() to get the interrupt
> drm/exynos/exynos_drm_fimd: Use platform_get_irq_byname() to get the
> interrupt
> drm/exynos/fimc: Use platform_get_irq() to get the interrupt
> drm/exynos: gsc: Use platform_get_irq() to get the interrupt
>
> drivers/gpu/drm/exynos/exynos7_drm_decon.c | 12 +++---------
> drivers/gpu/drm/exynos/exynos_drm_fimc.c | 13 +++++--------
> drivers/gpu/drm/exynos/exynos_drm_fimd.c | 13 ++++---------
> drivers/gpu/drm/exynos/exynos_drm_gsc.c | 10 +++-------
> drivers/gpu/drm/exynos/exynos_mixer.c | 14 ++++++--------
> 5 files changed, 21 insertions(+), 41 deletions(-)
>
prev parent reply other threads:[~2022-01-14 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211222190157epcas1p1d556269940101a49ab245a4f1d7d45c0@epcas1p1.samsung.com>
2021-12-22 19:01 ` [PATCH 0/5] drm/exynos: Use platform_get_irq*() variants to fetch IRQ's Lad Prabhakar
2021-12-22 19:01 ` [PATCH 1/5] drm/exynos/exynos7_drm_decon: Use platform_get_irq_byname() to get the interrupt Lad Prabhakar
2021-12-22 19:01 ` [PATCH 2/5] drm/exynos: mixer: Use platform_get_irq() " Lad Prabhakar
2022-01-14 11:20 ` Inki Dae
2022-01-15 1:40 ` Lad, Prabhakar
2021-12-22 19:01 ` [PATCH 3/5] drm/exynos/exynos_drm_fimd: Use platform_get_irq_byname() " Lad Prabhakar
2021-12-22 19:01 ` [PATCH 4/5] drm/exynos/fimc: Use platform_get_irq() " Lad Prabhakar
2021-12-22 19:01 ` [PATCH 5/5] drm/exynos: gsc: " Lad Prabhakar
2022-01-14 11:47 ` Inki Dae [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=6f044839-e1d8-b9a8-90c3-7e929d498838@samsung.com \
--to=inki.dae@samsung.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jy0922.shim@samsung.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=sw0312.kim@samsung.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).