From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Vladimir Yakovlev" <vovchkir@gmail.com>
Cc: <Laurent.pinchart@ideasonboard.com>, <airlied@gmail.com>,
<andrzej.hajda@intel.com>, <dmitry.baryshkov@oss.qualcomm.com>,
<dri-devel@lists.freedesktop.org>, <jernej.skrabec@gmail.com>,
<jonas@kwiboo.se>, <linux-kernel@vger.kernel.org>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<neil.armstrong@linaro.org>, <rfoss@kernel.org>,
<simona@ffwll.ch>, <tzimmermann@suse.de>
Subject: Re: [PATCH v2 0/1] drm/bridge: lontium-lt9611uxc: use irq as optional
Date: Wed, 07 Jan 2026 10:09:39 +0100 [thread overview]
Message-ID: <DFI8N16SORJ9.3P2KY2DK6ACFS@bootlin.com> (raw)
In-Reply-To: <20260107032342.332758-1-vovchkir@gmail.com>
On Wed Jan 7, 2026 at 4:23 AM CET, Vladimir Yakovlev wrote:
> Hello!
>
> This patch add support IRQ as optional for lt9611uxc
>
> Changes in v2:
> - As Luca Ceresoli recommended earlier, I added a patch to replace
> - request_threaded_irq with devm_request_threaded_irq before making
> - these changes.
> -
> - Since the updates only affected this patch, and the previous patch
> - was new, I made v2 just for this one. I apologize if this is incorrect.
This series depends on "[PATCH] drm/bridge: lontium-lt9611uxc: change to
use devm_request_threaded_irq" which you have sent separately, so it cannot
be applied as-is. The best thing to do would have been sending a v2 series
with 2 patches: first the devm conversion, then this one.
However no need to send again just for this, it can be handled while
applying.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-01-07 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 3:23 [PATCH v2 0/1] drm/bridge: lontium-lt9611uxc: use irq as optional Vladimir Yakovlev
2026-01-07 3:23 ` [PATCH v2 1/1] drm/bridge: lontium-lt9611uxc: use irq as optional parameter Vladimir Yakovlev
2026-01-07 9:23 ` Luca Ceresoli
2026-01-07 9:09 ` Luca Ceresoli [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=DFI8N16SORJ9.3P2KY2DK6ACFS@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vovchkir@gmail.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 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.