From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2] MEDIA: Driver for ON Semi AR0521 camera sensor
Date: Thu, 24 Jun 2021 15:51:07 +0200 [thread overview]
Message-ID: <m3sg174bhw.fsf@t19.piap.pl> (raw)
In-Reply-To: <20210624131048.1272f272@coco.lan> (Mauro Carvalho Chehab's message of "Thu, 24 Jun 2021 13:10:48 +0200")
Hi Mauro,
Mauro Carvalho Chehab <mchehab@kernel.org> writes:
> Media maintainers need a SoB in order to be able to review, as
> driver review takes a lot of time and efforts from reviewers, and
> the time they spend reviewing a driver prevents them to do their
> (paid) work.
Then how do you propose we solve the problem?
For example, how about a declaration: that if somebody is working on
a driver (in this case) and has actually presented a (possibly not yet
mergeable) patch, then versions of this code from other people will not
be accepted at the same time instead. Please note that I don't mean
abandoned code, I mean a code which simply needs some work and thus
a bit of time.
Those other people can always apply their changes once the original code
is accepted, right? And the changes may get a chance to be examined :-)
Or is it too much?
> That's said, on a very quick check, it sounds that this driver requires
> some work. For instance, it is based on an v4l2_subdev_pad_config,
> which was recently replaced upstream.
Well, TBH drivers/media is a fast moving target... But it's something.
I will obviously update this when I'm back from vacation.
Thanks.
--
Krzysztof Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
prev parent reply other threads:[~2021-06-24 13:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 11:18 [RFC v2] MEDIA: Driver for ON Semi AR0521 camera sensor Krzysztof Hałasa
2021-06-22 11:57 ` Laurent Pinchart
2021-06-23 4:21 ` Krzysztof Hałasa
2021-06-23 4:31 ` Laurent Pinchart
2021-06-23 5:28 ` Krzysztof Hałasa
2021-06-23 13:17 ` Laurent Pinchart
2021-06-23 14:27 ` Kieran Bingham
2021-06-24 4:57 ` Krzysztof Hałasa
2021-06-24 12:10 ` Laurent Pinchart
2021-06-24 12:39 ` Greg KH
2021-06-24 13:22 ` Krzysztof Hałasa
2021-06-24 13:29 ` Greg KH
2021-06-24 14:17 ` Krzysztof Hałasa
2021-06-24 14:31 ` Greg KH
2021-06-24 13:34 ` Laurent Pinchart
2021-06-24 14:42 ` Greg KH
2021-06-25 6:03 ` Krzysztof Hałasa
2021-06-25 6:59 ` Greg KH
2021-06-24 11:10 ` Mauro Carvalho Chehab
2021-06-24 13:51 ` Krzysztof Hałasa [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=m3sg174bhw.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/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