mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: "Łukasz Lebiedziński" <kernel@lvkasz.us>,
	"Yassine Oudjana" <y.oudjana@protonmail.com>,
	"MyungJoo Ham" <myungjoo.ham@samsung.com>,
	"Chanwoo Choi" <cw00.choi@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9] extcon: add support for Samsung S2M series PMIC extcon devices
Date: Wed, 17 Jun 2026 16:21:40 +0200	[thread overview]
Message-ID: <ajKtEn2jNxXfRj14@monoceros> (raw)
In-Reply-To: <20260616-s2mu005-pmic-v9-1-3f29fabda993@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

Hello,

On Tue, Jun 16, 2026 at 02:59:41PM +0530, Kaustabh Chakraborty wrote:
> +static const struct platform_device_id s2m_muic_id_table[] = {
> +	{ "s2mu005-muic", S2MU005 },

Please make this:

+	{ .name = "s2mu005-muic", .driver_data = S2MU005 },
	
> +	{ /* sentinel */ },

and drop the trailing , here ...

> +};
> +MODULE_DEVICE_TABLE(platform, s2m_muic_id_table);
> +
> +/*
> + * Device is instantiated through parent MFD device and device matching
> + * is done through platform_device_id.
> + *
> + * However if device's DT node contains proper clock compatible and
> + * driver is built as a module, then the *module* matching will be done
> + * through DT aliases. This requires of_device_id table. In the same
> + * time this will not change the actual *device* matching so do not add
> + * .of_match_table.
> + */
> +static const struct of_device_id s2m_muic_of_match_table[] = {
> +	{
> +		.compatible = "samsung,s2mu005-muic",
> +		.data = (void *)S2MU005,
> +	}, {
> +		/* sentinel */
> +	},

... and here.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-06-17 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  9:29 Kaustabh Chakraborty
2026-06-17 14:21 ` Uwe Kleine-König [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=ajKtEn2jNxXfRj14@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=cw00.choi@samsung.com \
    --cc=kauschluss@disroot.org \
    --cc=kernel@lvkasz.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=y.oudjana@protonmail.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

Powered by JetHome