From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bryan O'Donoghue <bod@kernel.org>,
Hans de Goede <hansg@kernel.org>,
Jingjing Xiong <jingjing.xiong@intel.com>,
Hao Yao <hao.yao@intel.com>, Jim Lai <jim.lai@intel.com>,
You-Sheng Yang <vicamo.yang@canonical.com>,
Alan Stern <stern@rowland.harvard.edu>,
Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] media: i2c: ov02e10: add OV02E10 image sensor driver
Date: Tue, 15 Apr 2025 12:16:44 +0000 [thread overview]
Message-ID: <Z_5OLCUQEAYVBgHn@kekkonen.localdomain> (raw)
In-Reply-To: <20250407-b4-media-comitters-next-25-03-13-ov02e10-v4-2-211e3e6fae90@linaro.org>
Hi Bryan,
On Mon, Apr 07, 2025 at 10:13:08AM +0100, Bryan O'Donoghue wrote:
> From: Jingjing Xiong <jingjing.xiong@intel.com>
>
> Add in the ov02e10 driver from the Intel IPU6 repository.
This commit message is just too much for adding a driver. I've just dropped
what's below.
--
Sakari Ailus
next prev parent reply other threads:[~2025-04-15 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 9:13 [PATCH v4 0/2] Import IPU6 ov02e10 sensor driver and enable OF usage of it Bryan O'Donoghue
2025-04-07 9:13 ` [PATCH v4 1/2] media: dt-bindings: Add OmniVision OV02E10 Bryan O'Donoghue
2025-04-07 9:13 ` [PATCH v4 2/2] media: i2c: ov02e10: add OV02E10 image sensor driver Bryan O'Donoghue
2025-04-15 12:14 ` Sakari Ailus
2025-04-15 12:16 ` Sakari Ailus [this message]
2025-04-18 16:24 ` David Heidelberg
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=Z_5OLCUQEAYVBgHn@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=bod@kernel.org \
--cc=broonie@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hansg@kernel.org \
--cc=hao.yao@intel.com \
--cc=hdegoede@redhat.com \
--cc=jim.lai@intel.com \
--cc=jingjing.xiong@intel.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=vicamo.yang@canonical.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