[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7fd1d23-ea4d-2c17-e3cb-b27f9eb4f687@gmail.com>
Date: Mon, 27 Jul 2020 03:25:48 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Hans Verkuil <hverkuil@...all.nl>,
Sowjanya Komatineni <skomatineni@...dia.com>,
thierry.reding@...il.com, jonathanh@...dia.com, frankc@...dia.com,
sakari.ailus@....fi, robh+dt@...nel.org, helen.koike@...labora.com
Cc: sboyd@...nel.org, gregkh@...uxfoundation.org,
linux-media@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-i2c@...r.kernel.org
Subject: Re: [RFC PATCH v4 00/14] Support for Tegra video capture from
external sensor
24.07.2020 12:43, Hans Verkuil пишет:
> Thierry, Dmitry,
>
> I'm happy with this series from a media perspective. However, patches 1-5 fix
> various i2c-tegra.c issues and patch 12 changes mipi calibration functions in
> drivers/gpu that patch 13 relies on.
>
> I think the i2c-tegra.c patches can be merged independently into the i2c
> subsystem, but patch 12 needs to be merged with the media patches. So for patch
> 12 I need an Acked-by from Thierry.
>
> I can also take the i2c-tegra patches if preferred, but there too I need Acks.
> Dmitry, can you either take these i2c patches, or reply with Acks if you want
> me to take it?
Hello, Hans and everyone! The I2C patches are good to me.
Either way of merging the patches should be fine since it's a hardware
bring up phase, and thus, it's not critical if patches will be applied
in a wrong order.
I'm listed as a reviewer and not a maintainer of the Tegra I2C driver,
so it should be up to Thierry and Wolfram to decide how to merge the I2C
patches.
Powered by blists - more mailing lists