All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur Crepin Leblond <arthur@marmottus.net>
To: netdev-bot+sashiko@kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, arnd@arndb.de,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v9 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema
Date: Wed, 23 Sep 2026 11:12:21 +0200	[thread overview]
Message-ID: <20260923091221.GA90128@marmottus.net> (raw)
In-Reply-To: <179009180465.2160803.12754142201441824675@kernel.org>

On Tue, Sep 22, 2026 at 03:43:24PM +0000, netdev-bot+sashiko@kernel.org wrote:
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index cae5962045dd..e6a5a4e245a0 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -29439,6 +29439,12 @@ M:	Miloslav Trmac <mitr@volny.cz>
>>  S:	Maintained
>>  F:	drivers/input/misc/wistron_btns.c
>>
>> +WIZNET W5100 ETHERNET DRIVER
>> +M:	Arthur Crepin Leblond <arthur@marmottus.net>
>> +L:	netdev@vger.kernel.org
>> +S:	Maintained
>> +F:	Documentation/devicetree/bindings/net/wiznet,w5100.yaml
>
>[Severity: Low]
>Could the commit message mention this new MAINTAINERS section?  The
>preserved log text only describes the .txt to YAML conversion and the
>edge-falling to level-low trigger change; the new maintainership claim is
>mentioned only in the changelog below the --- separator, which does not end
>up in git history.
>
>The section is named as a driver entry, but its only F: line matches the
>binding file, so at this commit scripts/get_maintainer.pl will not route
>drivers/net/ethernet/wiznet/ changes here.  That part is addressed later in
>the same series: the commit "w5100: detect carrier state using link status
>bit and optional interrupt" adds F: drivers/net/ethernet/wiznet/ to this
>section, so the mismatch exists only between this patch and that one.
>

I'll update the commit and the MAINTAINERS file.

Arthur

  reply	other threads:[~2026-09-23  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 15:13 [PATCH net-next v9 0/3] w5100: restore GPIO-based link detection Arthur Crepin Leblond
2026-09-18 15:13 ` [PATCH net-next v9 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema Arthur Crepin Leblond
2026-09-22 15:43   ` netdev-bot+sashiko
2026-09-23  9:12     ` Arthur Crepin Leblond [this message]
2026-09-18 15:13 ` [PATCH net-next v9 2/3] dt-bindings: net: wiznet,w5100: add link status interrupt Arthur Crepin Leblond
2026-09-18 15:13 ` [PATCH net-next v9 3/3] w5100: detect carrier state using link status bit and optional interrupt Arthur Crepin Leblond
2026-09-19 15:14   ` sashiko-bot
2026-09-21  9:04     ` Arthur Crepin Leblond
2026-09-21 10:42       ` Arthur Crepin Leblond
2026-09-22 15:43   ` netdev-bot+sashiko
2026-09-23  9:36     ` Arthur Crepin Leblond

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=20260923091221.GA90128@marmottus.net \
    --to=arthur@marmottus.net \
    --cc=andrew+netdev@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.