From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Kate Hsuan <hpa@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans de Goede <johannes.goede@oss.qualcomm.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans de Goede <hansg@kernel.org>
Subject: Re: [PATCH v12] media: Add t4ka3 camera sensor driver
Date: Tue, 24 Mar 2026 14:48:15 +0100 [thread overview]
Message-ID: <63e50918-60d3-4a01-b28d-77c8580f1260@kernel.org> (raw)
In-Reply-To: <acKREpGPr1J_1Oaj@kekkonen.localdomain>
On 24/03/2026 14:26, Sakari Ailus wrote:
> Hi Hans,
>
> On Tue, Mar 24, 2026 at 02:17:38PM +0100, Hans Verkuil wrote:
>> I'm missing an entry for the MAINTAINERS file.
>
> Thanks for noticing. I already picked this and it's in a PR... there are a
> few other (minor) remaining matters, too, which I asked Kate to address on
> a follow-up patch. Would it be ok to address these at the same time, after
> the driver is merged?
>
I prefer to have the MAINTAINERS entry before I merge this driver. Other
minor matters are fine for a follow-up patch, but a new driver shouldn't
be merged without the corresponding MAINTAINERS entry.
If Kate can post a patch for that entry tomorrow, and you Ack it, then I can just
add it to the PR.
Regards,
Hans
next prev parent reply other threads:[~2026-03-24 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 7:16 [PATCH v12] media: Add t4ka3 camera sensor driver Kate Hsuan
2026-03-24 9:33 ` Sakari Ailus
2026-03-25 2:49 ` Kate Hsuan
2026-03-24 13:17 ` Hans Verkuil
2026-03-24 13:26 ` Sakari Ailus
2026-03-24 13:48 ` Hans Verkuil [this message]
2026-03-25 3:01 ` Kate Hsuan
2026-03-26 5:21 ` Kate Hsuan
2026-03-26 7:41 ` Hans Verkuil
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=63e50918-60d3-4a01-b28d-77c8580f1260@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=hansg@kernel.org \
--cc=hpa@redhat.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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