From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Pratap Nirujogi <pratap.nirujogi@amd.com>
Cc: rdunlap@infradead.org, Hans de Goede <hdegoede@redhat.com>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
benjamin.chan@amd.com, bin.du@amd.com,
gjorgji.rosikopulos@amd.com, king.li@amd.com, dantony@amd.com
Subject: Re: [PATCH 2/3] i2c: amd-isp: Initialize unique adpater name
Date: Sat, 31 May 2025 08:06:58 +0300 (EEST) [thread overview]
Message-ID: <8670fa5f-5bf6-7dfe-1ec7-5cd1ec4472aa@linux.intel.com> (raw)
In-Reply-To: <20250530200234.1539571-3-pratap.nirujogi@amd.com>
Hi Pratap,
Please send the next version(s) to all relevant people as indicated by
scripts/get_maintainer.pl.
On Fri, 30 May 2025, Pratap Nirujogi wrote:
> Initialize unique name for amdisp i2c adapter, which is used
> in the platform driver to detect the matching adapter for
> i2c_client creation.
>
> Fixes: 90b85567e457 ("platform/x86: Add AMD ISP platform config for OV05C10")
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Link: https://lore.kernel.org/all/04577a46-9add-420c-b181-29bad582026d@infradead.org
> Signed-off-by: Pratap Nirujogi <pratap.nirujogi@amd.com>
> ---
> drivers/i2c/busses/i2c-designware-amdisp.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-designware-amdisp.c b/drivers/i2c/busses/i2c-designware-amdisp.c
> index ad6f08338124..e8cb3785c740 100644
> --- a/drivers/i2c/busses/i2c-designware-amdisp.c
> +++ b/drivers/i2c/busses/i2c-designware-amdisp.c
> @@ -62,6 +62,8 @@ static int amd_isp_dw_i2c_plat_probe(struct platform_device *pdev)
>
> adap = &isp_i2c_dev->adapter;
> adap->owner = THIS_MODULE;
> + snprintf(adap->name, sizeof(adap->name),
> + "AMDISP DesignWare I2C adapter");
scnprintf() is preferrable over snprintf(). Even if you don't use the
return value here, eventually somebody will want to get rid of snprintf()
entirely so lets try not add new ones.
> ACPI_COMPANION_SET(&adap->dev, ACPI_COMPANION(&pdev->dev));
> adap->dev.of_node = pdev->dev.of_node;
> /* use dynamically allocated adapter id */
>
--
i.
next prev parent reply other threads:[~2025-05-31 5:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 19:59 [PATCH 0/3] Fix build issue when CONFIG_MODULES is not set Pratap Nirujogi
2025-05-30 19:59 ` [PATCH 1/3] i2c: designware: Initialize adapter name only when " Pratap Nirujogi
2025-05-31 5:14 ` Ilpo Järvinen
2025-06-03 3:18 ` Nirujogi, Pratap
2025-05-30 19:59 ` [PATCH 2/3] i2c: amd-isp: Initialize unique adpater name Pratap Nirujogi
2025-05-31 5:06 ` Ilpo Järvinen [this message]
2025-06-03 3:15 ` Nirujogi, Pratap
2025-05-30 19:59 ` [PATCH 3/3] platform/x86: Use i2c adapter name to fix build errors Pratap Nirujogi
2025-05-31 5:11 ` Ilpo Järvinen
2025-06-03 3:35 ` Nirujogi, Pratap
2025-06-03 4:46 ` Mario Limonciello
2025-06-03 15:50 ` Nirujogi, Pratap
2025-06-03 7:15 ` Ilpo Järvinen
2025-06-03 15:50 ` 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=8670fa5f-5bf6-7dfe-1ec7-5cd1ec4472aa@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=benjamin.chan@amd.com \
--cc=bin.du@amd.com \
--cc=dantony@amd.com \
--cc=gjorgji.rosikopulos@amd.com \
--cc=hdegoede@redhat.com \
--cc=king.li@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pratap.nirujogi@amd.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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