From: Bjorn Helgaas <helgaas@kernel.org>
To: bingbu.cao@intel.com
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
hdegoede@redhat.com, hans@hansg.org,
stanislaw.gruszka@linux.intel.com, jerry.w.hu@intel.com,
tian.shu.qiu@intel.com, daxing.li@intel.com, hao.yao@intel.com,
bingbu.cao@linux.intel.com
Subject: Re: [RFC PATCH 0/7] Intel IPU7 PCI and input system device drivers
Date: Mon, 3 Mar 2025 10:23:44 -0600 [thread overview]
Message-ID: <20250303162344.GA168964@bhelgaas> (raw)
In-Reply-To: <20250221075252.3347582-1-bingbu.cao@intel.com>
On Fri, Feb 21, 2025 at 03:52:45PM +0800, bingbu.cao@intel.com wrote:
> From: Bingbu Cao <bingbu.cao@intel.com>
>
> This patch series adds a driver for Intel IPU7 input system.
> IPU7 is the seventh generation of Imaging Processing Unit, it is a
> PCI device which can be found in some Intel Client Platforms such as
> Intel Lunar Lake and Panther Lake, etc.
> User can use IPU7 to capture images from MIPI camera sensors, support
> both MIPI CSI DPHY and CPHY.
Minor whitespace nit:
$ git am m/20250221_bingbu_cao_intel_ipu7_pci_and_input_system_device_drivers.mbx
Applying: media: Rename the IPU PCI device table header and add IPU7 PCI IDs
Applying: media: ipu7: add Intel IPU7 PCI device driver
Applying: media: ipu7: add IPU7 DMA APIs and MMU mapping
Applying: media: ipu7: add firmware parse, syscom interface and boot sequence
.git/rebase-apply/patch:871: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Applying: media: ipu7: add IPU7 firmware ABI headers
Applying: media: ipu7: add IPU7 input system device driver
Applying: media: ipu7: add Makefile and Kconfig for IPU7
prev parent reply other threads:[~2025-03-03 16:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 7:52 [RFC PATCH 0/7] Intel IPU7 PCI and input system device drivers bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 1/7] media: Rename the IPU PCI device table header and add IPU7 PCI IDs bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 2/7] media: ipu7: add Intel IPU7 PCI device driver bingbu.cao
2025-02-24 14:38 ` Philipp Stanner
2025-02-25 9:39 ` Bingbu Cao
2025-02-27 4:06 ` Bingbu Cao
2025-03-03 15:01 ` Philipp Stanner
2025-03-03 15:18 ` Philipp Stanner
2025-02-26 10:00 ` Philipp Stanner
2025-02-27 3:47 ` Bingbu Cao
2025-02-21 7:52 ` [RFC PATCH 3/7] media: ipu7: add IPU7 DMA APIs and MMU mapping bingbu.cao
2025-03-03 16:13 ` Bjorn Helgaas
2025-02-21 7:52 ` [RFC PATCH 4/7] media: ipu7: add firmware parse, syscom interface and boot sequence bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 5/7] media: ipu7: add IPU7 firmware ABI headers bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 6/7] media: ipu7: add IPU7 input system device driver bingbu.cao
2025-02-21 7:52 ` [RFC PATCH 7/7] media: ipu7: add Makefile and Kconfig for IPU7 bingbu.cao
2025-02-25 5:55 ` Bingbu Cao
2025-02-21 12:55 ` [RFC PATCH 0/7] Intel IPU7 PCI and input system device drivers Sakari Ailus
2025-04-09 20:23 ` Laurent Pinchart
2025-03-03 16:23 ` Bjorn Helgaas [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=20250303162344.GA168964@bhelgaas \
--to=helgaas@kernel.org \
--cc=bingbu.cao@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=daxing.li@intel.com \
--cc=hans@hansg.org \
--cc=hao.yao@intel.com \
--cc=hdegoede@redhat.com \
--cc=jerry.w.hu@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stanislaw.gruszka@linux.intel.com \
--cc=tian.shu.qiu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox