public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nirujogi, Pratap" <pnirujog@amd.com>
To: Andi Shyti <andi.shyti@kernel.org>,
	Pratap Nirujogi <pratap.nirujogi@amd.com>
Cc: mlimonci@amd.com, christophe.jaillet@wanadoo.fr, krzk@kernel.org,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	benjamin.chan@amd.com, bin.du@amd.com,
	gjorgji.rosikopulos@amd.com, king.li@amd.com, dantony@amd.com,
	Venkata Narendra Kumar Gutta <vengutta@amd.com>
Subject: Re: [PATCH v2] i2c: amd-isp: Add ISP i2c-designware driver
Date: Mon, 28 Apr 2025 07:48:46 -0400	[thread overview]
Message-ID: <ae5b76fa-cc5c-46dc-a8f8-46e14034e2f1@amd.com> (raw)
In-Reply-To: <i4fqptobrabmsok6eaphyte3ihwgqnz6ar6k6h6tw7d5ovimek@vjp2tjlzm7oh>

Hi Andi,

Happy to see this patch is accepted and merged. Thanks very much!

Thanks,
Pratap

On 4/28/2025 3:30 AM, Andi Shyti wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
> 
> 
> Hi Pratap,
> 
> On Thu, Apr 24, 2025 at 02:49:26PM -0400, Pratap Nirujogi wrote:
>> The camera sensor is connected via ISP I2C bus in AMD SOC
>> architectures. Add new I2C designware driver to support
>> new camera sensors on AMD HW.
>>
>> Co-developed-by: Venkata Narendra Kumar Gutta <vengutta@amd.com>
>> Signed-off-by: Venkata Narendra Kumar Gutta <vengutta@amd.com>
>> Co-developed-by: Bin Du <bin.du@amd.com>
>> Signed-off-by: Bin Du <bin.du@amd.com>
>> Signed-off-by: Pratap Nirujogi <pratap.nirujogi@amd.com>
> 
> merged to i2c/i2c-host.
> 
> Thanks,
> Andi


  reply	other threads:[~2025-04-28 11:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 18:49 [PATCH v2] i2c: amd-isp: Add ISP i2c-designware driver Pratap Nirujogi
2025-04-24 18:58 ` Mario Limonciello
2025-04-28  7:30 ` Andi Shyti
2025-04-28 11:48   ` Nirujogi, Pratap [this message]
2025-05-09  7:11 ` Christophe JAILLET
2025-05-12 22:24   ` Nirujogi, Pratap
2025-05-13 17:23     ` Christophe JAILLET
2025-05-13 20:16       ` Nirujogi, Pratap

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=ae5b76fa-cc5c-46dc-a8f8-46e14034e2f1@amd.com \
    --to=pnirujog@amd.com \
    --cc=andi.shyti@kernel.org \
    --cc=benjamin.chan@amd.com \
    --cc=bin.du@amd.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dantony@amd.com \
    --cc=gjorgji.rosikopulos@amd.com \
    --cc=king.li@amd.com \
    --cc=krzk@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlimonci@amd.com \
    --cc=pratap.nirujogi@amd.com \
    --cc=vengutta@amd.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