From: Bryan O'Donoghue <bod@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: p.zabel@pengutronix.de, xavier.roumegue@oss.nxp.com,
hverkuil@xs4all.nl, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Klug <stefan.klug@ideasonboard.com>
Subject: Re: [PATCH 2/2] MAINTAINERS: Add myself to dw100 as reviewer
Date: Tue, 2 Jun 2026 15:57:19 +0100 [thread overview]
Message-ID: <ea9f45f8-4389-4c78-a4ea-dc08d3e461c2@kernel.org> (raw)
In-Reply-To: <20260602142603.GB850227@killaraus.ideasonboard.com>
On 02/06/2026 15:26, Laurent Pinchart wrote:
> On Tue, Jun 02, 2026 at 11:10:24AM +0100, Bryan O'Donoghue wrote:
>> On 02/06/2026 09:55, Laurent Pinchart wrote:
>>> Thanks for volunteering 🙂
>>>
>>> This may however not be the best candidate. The dw100 driver is well
>>> maintained today, by Xavier as well as Stefan, as Ideas on Board makes
>>> active use of it (Stefan, you could also volunteer as a reviewer).
>>>
>>> Drivers that I think would most benefit from your reviews would be
>>> imx8mq-mipi-csi2, dw-mipi-csi2rx (technically a Synopsys driver, but
>>> used in NXP SoCs), and the new imx95-csi-formatter driver ([1]).
>>>
>>> Other candidates could be imx7-media-csi and imx-mipi-csis, but those
>>> see little activity as they support older hardware. The imx media
>>> staging drivers could also do with some love, but that would be active
>>> development and not just review.
>>>
>>> [1]https://lore.kernel.org/20260525-csi_formatter-v8-0-6b646231224b@oss.nxp.com
>>>
>>>> Signed-off-by: Bryan O'Donoghue<bod@kernel.org>
>>>> ---
>>>> MAINTAINERS | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index ec0743b41a463..35368c2ff0ca6 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -19243,6 +19243,7 @@ F: drivers/media/platform/nxp/imx8-isi/
>>>>
>>>> NXP i.MX 8MP DW100 V4L2 DRIVER
>>>> M: Xavier Roumegue<xavier.roumegue@oss.nxp.com>
>>>> +R: Bryan O'Donoghue<bod@kernel.org>
>>>> L: linux-media@vger.kernel.org
>>>> S: Maintained
>>>> F: Documentation/devicetree/bindings/media/nxp,dw100.yaml
>>> --
>>> Regards,
>>>
>>> Laurent Pinchart
>>
>> Ah, wrong set.
>>
>> No problem, I'll v2 for the above instead.
>
> Thank you. Don't get me wrong, your reviews for the dw100 driver would
> also be appreciated, but if you have limited time (and I assume we all
> do), the above drivers would benefit more from your comments.
>
> --
> Regards,
>
> Laurent Pinchart
Eh, not a bit of it.
You flagged we should do some cross review. I'm happy to be shown to
whichever drivers/files it is you mean.
---
bod
next prev parent reply other threads:[~2026-06-02 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 15:50 [PATCH 1/2] MAINTAINERS: Add myself to imx-pip " bod
2026-06-01 15:50 ` [PATCH 2/2] MAINTAINERS: Add myself to dw100 " bod
2026-06-02 2:38 ` Frank Li
2026-06-02 8:55 ` Laurent Pinchart
2026-06-02 10:10 ` Bryan O'Donoghue
2026-06-02 14:26 ` Laurent Pinchart
2026-06-02 14:57 ` Bryan O'Donoghue [this message]
2026-06-02 2:36 ` [PATCH 1/2] MAINTAINERS: Add myself to imx-pip " Frank Li
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=ea9f45f8-4389-4c78-a4ea-dc08d3e461c2@kernel.org \
--to=bod@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=stefan.klug@ideasonboard.com \
--cc=xavier.roumegue@oss.nxp.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
Powered by JetHome