From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Jacopo Mondi <jacopo@jmondi.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@iki.fi>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH v8 2/2] On Semi AR0521 sensor driver
Date: Fri, 06 May 2022 08:10:16 +0200 [thread overview]
Message-ID: <m3pmkryywn.fsf@t19.piap.pl> (raw)
In-Reply-To: <m37d7ufrzx.fsf@t19.piap.pl> ("Krzysztof Hałasa"'s message of "Tue, 12 Apr 2022 13:41:54 +0200")
Hi Mauro et al,
Mauro, you are the drivers/media maintainer. Is the AR0521 driver ready
to be merged, are there still unresolved issues, or the driver is not no
be merged at all? I understand everyone's so busy but a simple yes or no
isn't too much, is it?
> Since it appears all remaining issues with the AR0521 driver have been
> resolved weeks ago... is there anything I should do in order to have the
> driver merged, should I rather proceed with the "staging" thing, or
> maybe some other option should be used?
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2022-05-06 6:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:33 [PATCH v8 0/2] On Semi AR0521 sensor driver Krzysztof Hałasa
2022-03-01 8:38 ` [PATCH v8 1/2] " Krzysztof Hałasa
2022-03-01 8:41 ` [PATCH v8 2/2] " Krzysztof Hałasa
2022-03-01 9:31 ` Jacopo Mondi
2022-03-01 12:34 ` Krzysztof Hałasa
2022-03-01 14:30 ` Jacopo Mondi
2022-03-02 6:39 ` Krzysztof Hałasa
2022-04-12 11:41 ` Krzysztof Hałasa
2022-05-06 6:10 ` Krzysztof Hałasa [this message]
2022-06-29 23:37 ` Sakari Ailus
2022-06-30 4:29 ` Krzysztof Hałasa
2022-06-30 7:13 ` Sakari Ailus
2022-06-20 11:47 ` Krzysztof Hałasa
2022-03-01 13:39 ` Sakari Ailus
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=m3pmkryywn.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=devicetree@vger.kernel.org \
--cc=jacopo@jmondi.org \
--cc=joe@perches.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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.