Linux Media Controller development
 help / color / mirror / Atom feed
From: Bin Du <Bin.Du@amd.com>
To: "sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	"laurent.pinchart+renesas@ideasonboard.com"
	<laurent.pinchart+renesas@ideasonboard.com>,
	"bryan.odonoghue@linaro.org" <bryan.odonoghue@linaro.org>,
	"prabhakar.mahadev-lad.rj@bp.renesas.com"
	<prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"sultan@kerneltoast.com" <sultan@kerneltoast.com>,
	"Nirujogi, Pratap" <Pratap.Nirujogi@amd.com>,
	"Chan, Benjamin (Koon Pan)" <Benjamin.Chan@amd.com>,
	"Li, King" <King.Li@amd.com>,
	"gjorgji.rosikopulos@amd.com" <gjorgji.rosikopulos@amd.com>,
	"Jawich, Phil" <Phil.Jawich@amd.com>,
	"Antony, Dominic" <Dominic.Antony@amd.com>,
	"Gong, Richard" <Richard.Gong@amd.com>,
	"Tsao, Anson" <anson.tsao@amd.com>
Subject: Re: [PATCH v10 0/7] Add AMD ISP4 driver
Date: Tue, 7 Apr 2026 15:19:20 +0800	[thread overview]
Message-ID: <21dfb3d2-d838-4325-8a6a-6024b851cbc5@amd.com> (raw)
In-Reply-To: <adSlwqPVF81feLHx@kekkonen.localdomain>

Hi Sakari,

Thank you very much for picking up the series and for updating 
Patchwork. I really appreciate your help and support. It means a lot to us.
Yes, that's right. <20260303224433.87242-1-kinncj@gmail.com> is no 
longer needed.

>-----Original Message-----
>From: sakari.ailus@linux.intel.com <sakari.ailus@linux.intel.com>
>Sent: Tuesday, April 7, 2026 2:36 PM
>To: Du, Bin <Bin.Du@amd.com>
>Cc: Limonciello, Mario <Mario.Limonciello@amd.com>; mchehab@kernel.org;
>hverkuil@xs4all.nl; laurent.pinchart+renesas@ideasonboard.com;
>bryan.odonoghue@linaro.org; prabhakar.mahadev-lad.rj@bp.renesas.com;
>linux-media@vger.kernel.org; linux-kernel@vger.kernel.org;
>sultan@kerneltoast.com; Nirujogi, Pratap <Pratap.Nirujogi@amd.com>; Chan,
>Benjamin (Koon Pan) <Benjamin.Chan@amd.com>; Li, King
><King.Li@amd.com>; gjorgji.rosikopulos@amd.com; Jawich, Phil
><Phil.Jawich@amd.com>; Antony, Dominic <Dominic.Antony@amd.com>; Gong,
>Richard <Richard.Gong@amd.com>; Tsao, Anson <anson.tsao@amd.com>
>Subject: Re: [PATCH v10 0/7] Add AMD ISP4 driver
>
>Hi Bin,
>
>On Fri, Apr 03, 2026 at 03:17:18AM +0000, Du, Bin wrote:
>> Hi Laurent and Sakari,
>>
>> Just a gentle reminder regarding the review request below. When you
>> have a moment, I would appreciate it if you could take a look at this
>> patch series. Your feedback would be very helpful to ensure the
>> changes align with upstream expectations and maintainability.
>> Thank you very much for your time and support.
>
>The set is in my tree (amdisp4 branch) and I intend to send a PR for 7.2 once we
>have rc1 in the media tree (or whatever process we manage to get working by
>then).
>
>I updated the state in patchwork, too. I understand <20260303224433.87242-1-
>kinncj@gmail.com> isn't needed, is that right?
>
>--
>Kind regards,
>
>Sakari Ailus

Regards,
Bin

  reply	other threads:[~2026-04-07  7:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  8:41 [PATCH v10 0/7] Add AMD ISP4 driver Bin Du
2026-03-20  8:41 ` [PATCH v10 1/7] media: platform: amd: Introduce amd isp4 capture driver Bin Du
2026-03-20  8:41 ` [PATCH v10 2/7] media: platform: amd: low level support for isp4 firmware Bin Du
2026-03-20  8:41 ` [PATCH v10 3/7] media: platform: amd: Add isp4 fw and hw interface Bin Du
2026-03-20  8:41 ` [PATCH v10 4/7] media: platform: amd: isp4 subdev and firmware loading handling added Bin Du
2026-03-20  8:41 ` [PATCH v10 5/7] media: platform: amd: isp4 video node and buffers " Bin Du
2026-03-20  8:41 ` [PATCH v10 6/7] media: platform: amd: isp4 debug fs logging and more descriptive errors Bin Du
2026-03-20  8:41 ` [PATCH v10 7/7] Documentation: add documentation of AMD isp 4 driver Bin Du
2026-03-20 10:26 ` [PATCH v10 0/7] Add AMD ISP4 driver Du, Bin
2026-03-20 14:01   ` Mario Limonciello
2026-04-03  3:17     ` Du, Bin
2026-04-07  6:35       ` sakari.ailus
2026-04-07  7:19         ` Bin Du [this message]
2026-05-05 20:24           ` sakari.ailus
2026-05-06  9:41             ` Bin Du
2026-05-07  6:44               ` Bin Du
2026-05-07  9:34                 ` sakari.ailus
     [not found]                   ` <bd5ab106-e0ef-47d5-aefa-7304ad84105a@amd.com>
2026-05-08 21:30                     ` sakari.ailus
2026-05-09  1:59                       ` Bin Du
2026-05-09 23:49                         ` Ricardo Ribalda
2026-05-11  7:17                           ` Bin Du
     [not found] ` <69bd3a57.050a0220.1b4541.789b@mx.google.com>
2026-03-23  3:32   ` [v10,0/7] " Du, Bin

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=21dfb3d2-d838-4325-8a6a-6024b851cbc5@amd.com \
    --to=bin.du@amd.com \
    --cc=Benjamin.Chan@amd.com \
    --cc=Dominic.Antony@amd.com \
    --cc=King.Li@amd.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=Phil.Jawich@amd.com \
    --cc=Pratap.Nirujogi@amd.com \
    --cc=Richard.Gong@amd.com \
    --cc=anson.tsao@amd.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=gjorgji.rosikopulos@amd.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sultan@kerneltoast.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