Netdev List
 help / color / mirror / Atom feed
From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Roger Quadros <rogerq@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	<linux-omap@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <s-vadapalli@ti.com>
Subject: Re: [PATCH] net: ethernet: ti: davinci_mdio: Drop commas after match table sentinels
Date: Fri, 4 Sep 2026 12:58:39 +0530	[thread overview]
Message-ID: <89471ba2-460d-4794-a5cf-07cbfaf8d3a0@ti.com> (raw)
In-Reply-To: <CAMuHMdWyj-x-tm4E+ZC8KMkzx48hpAxkrK==0hjXeG_HQYZDLQ@mail.gmail.com>

On 04/09/26 12:50, Geert Uytterhoeven wrote:
> On Fri, 4 Sept 2026 at 06:44, Siddharth Vadapalli <s-vadapalli@ti.com> wrote:
>> On 03/09/26 18:00, Siddharth Vadapalli wrote:
>>> On 03/09/26 17:36, Geert Uytterhoeven wrote:
>>>> It does not make sense to have a comma after a sentinel, as any new
>>>> elements must be added before the sentinel.
>>>
>>> While I agree with it, this seems to require a 'cleanup-series' rather than
>>> an individual patch, given the following statistics:
>>>
>>> As of [0], running
>>>       git grep "sentinel.*}" drivers/net/ | wc -l
>>> gives
>>>       84
>>> and looking for the ones that terminate in a comma by running
>>>       git grep "sentinel.*}," drivers/net/ | wc -l
>>> gives
>>>       38
>>>
>>> So there are '37' other instances (apart from davinci_mdio.c) in
>>> drivers/net alone that require a cleanup.
> 
> [...]
> 
>>> Since this isn't a functional change, I am not sure why a specific change
>>> is required in davinci_mdio.c, unless you plan to cleanup the remaining
>>> '395' occurrences in the remaining code as well. I am not against the
>>> patch, but the reason for picking just davinci_mdio.c for cleanup isn't
>>> clear to me based on the commit message.
> 
> I know. Over the past few years, I fixed several of them I encountered,
> but never got to fixing all of them. After rc1, I flushed a few patches
> that could be sent independently, so there it was!

Thank you for providing the context for the current patch.

> 
>> I have posted the following series to cleanup all networking drivers
>> (excluding davinci_mdio.c since that is done by your patch) at:
>> https://lore.kernel.org/r/20260904043724.2955444-1-s-vadapalli@ti.com/
> 
> Happy to see my single patch triggered your great response!
> Thanks!

:)

Regards,
Siddharth.

  reply	other threads:[~2026-09-04  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 12:06 [PATCH] net: ethernet: ti: davinci_mdio: Drop commas after match table sentinels Geert Uytterhoeven
2026-09-03 12:30 ` Siddharth Vadapalli
2026-09-04  4:47   ` Siddharth Vadapalli
2026-09-04  7:20     ` Geert Uytterhoeven
2026-09-04  7:28       ` Siddharth Vadapalli [this message]
2026-09-03 14:38 ` Andrew Lunn
2026-09-03 15:00   ` Geert Uytterhoeven

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=89471ba2-460d-4794-a5cf-07cbfaf8d3a0@ti.com \
    --to=s-vadapalli@ti.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geert@linux-m68k.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rogerq@kernel.org \
    /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