From: Alexander Sverdlin <alex@sverdlin.org>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH net-next 27/33] net: ethernet: ti: cpsw: Remove comma after sentinel-entry in match-table
Date: Fri, 04 Sep 2026 10:45:55 +0200 [thread overview]
Message-ID: <5913e1de4be69b0b14557e7ccb5577ffbd1a145d.camel@sverdlin.org> (raw)
In-Reply-To: <20260904043724.2955444-28-s-vadapalli@ti.com>
On Fri, 2026-09-04 at 10:06 +0530, Siddharth Vadapalli wrote:
> Since sentinel is the last entry and we do not expect further entries
> following it, remove the comma.
>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Reviewed-by: Alexander Sverdlin <alex@sverdlin.org>
> ---
> drivers/net/ethernet/ti/cpsw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c
> index aa3531e844e8..63b64faeaca0 100644
> --- a/drivers/net/ethernet/ti/cpsw.c
> +++ b/drivers/net/ethernet/ti/cpsw.c
> @@ -1529,7 +1529,7 @@ static const struct of_device_id cpsw_of_mtable[] = {
> { .compatible = "ti,am335x-cpsw"},
> { .compatible = "ti,am4372-cpsw"},
> { .compatible = "ti,dra7-cpsw"},
> - { /* sentinel */ },
> + { /* sentinel */ }
> };
> MODULE_DEVICE_TABLE(of, cpsw_of_mtable);
next prev parent reply other threads:[~2026-09-04 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260904043724.2955444-1-s-vadapalli@ti.com>
[not found] ` <20260904043724.2955444-29-s-vadapalli@ti.com>
2026-09-04 8:45 ` [PATCH net-next 28/33] net: ethernet: ti: cpsw_new: Remove comma after sentinel-entry in match-table Alexander Sverdlin
[not found] ` <20260904043724.2955444-28-s-vadapalli@ti.com>
2026-09-04 8:45 ` Alexander Sverdlin [this message]
[not found] ` <20260904043724.2955444-27-s-vadapalli@ti.com>
2026-09-04 8:46 ` [PATCH net-next 26/33] net: ti: am65-cpsw-nuss: " Alexander Sverdlin
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=5913e1de4be69b0b14557e7ccb5577ffbd1a145d.camel@sverdlin.org \
--to=alex@sverdlin.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s-vadapalli@ti.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