From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
Marco Felsch <m.felsch@pengutronix.de>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Subject: Re: [PATCH v2] media: mt9m111: add regulator support
Date: Fri, 31 May 2019 21:29:57 +0200 [thread overview]
Message-ID: <87blzi5sne.fsf@belgarion.home> (raw)
In-Reply-To: <20190531100240.6f9e5c12@coco.lan> (Mauro Carvalho Chehab's message of "Fri, 31 May 2019 10:03:44 -0300")
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> writes:
> Hi Sakari,
>
> Em Fri, 31 May 2019 14:27:24 +0300
> Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
>
>> Hi Mauro,
>>
>> On Wed, May 29, 2019 at 03:25:18PM -0400, Mauro Carvalho Chehab wrote:
>> > From: Robert Jarzmik <robert.jarzmik@free.fr>
>
> As stated here, this patch is not really mine. It is a rebased version of a
> patch that was delegated to a sub-maintainer, being on his queue for more
> than 2 years.
Hi Mauro,
And if you need it, I can respin this patch for a v3, as I'm the original author
AFAIR. And as soon as my brain recovers from my flu, I can also test it if need
be.
You can ask whatever you need, I will help.
Cheers.
--
Robert
next prev parent reply other threads:[~2019-05-31 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 19:25 [PATCH v2] media: mt9m111: add regulator support Mauro Carvalho Chehab
2019-05-30 14:21 ` Akinobu Mita
2019-05-31 19:43 ` Robert Jarzmik
2019-06-02 15:05 ` Akinobu Mita
2019-05-31 11:27 ` Sakari Ailus
2019-05-31 13:03 ` Mauro Carvalho Chehab
2019-05-31 19:29 ` Robert Jarzmik [this message]
2019-06-18 11:51 ` Sakari Ailus
2019-06-03 19:54 ` Robert Jarzmik
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=87blzi5sne.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=akinobu.mita@gmail.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=linux-media@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=m.grzeschik@pengutronix.de \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.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 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.