From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: update phylink/sfp keyword matching
Date: Wed, 5 Aug 2020 23:12:16 +0100 [thread overview]
Message-ID: <20200805221216.GA1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <912b806b7943a227e3c79ed747b2242b87a3fd50.camel@perches.com>
On Wed, Aug 05, 2020 at 03:09:34PM -0700, Joe Perches wrote:
> On Wed, 2020-08-05 at 23:02 +0100, Russell King - ARM Linux admin wrote:
> > On Wed, Aug 05, 2020 at 11:54:25AM -0700, Joe Perches wrote:
> > > On Wed, 2020-08-05 at 19:22 +0100, Russell King - ARM Linux admin wrote:
> > > > On Wed, Aug 05, 2020 at 11:11:28AM -0700, Linus Torvalds wrote:
> > > > > On Wed, Aug 5, 2020 at 7:34 AM Russell King <rmk+kernel@armlinux.org.uk> wrote:
> > > > > > Is this something you're willing to merge directly please?
> > > > >
> > > > > Done.
> > > > >
> > > > > That said:
> > > > >
> > > > > > -K: phylink
> > > > > > +K: phylink\.h|struct\s+phylink|\.phylink|>phylink_|phylink_(autoneg|clear|connect|create|destroy|disconnect|ethtool|helper|mac|mii|of|set|start|stop|test|validate)
> > > > >
> > > > > That's a very awkward pattern. I wonder if there could be better ways
> > > > > to express this (ie "only apply this pattern to these files" kind of
> > > > > thing)
> > > >
> > > > Yes, it's extremely awkward - I spent much of the morning with perl
> > > > testing it out on the drivers/ subtree.
> > >
> > > And perhaps easier to read would be to use multiple K: lines.
> > > (?: used to avoid unnecessary capture groups)
> > >
> > > K: phylink\.h|struct\s+phylink
> > > K: (?:\.|\-\>)phylink_
> >
> > That one is definitely incorrect. It is not .phylink_ or ->phylink_,
> > it was .phylink (without _) or >phylink_
>
> Hi Russell.
>
> I don't see the difference.
>
> All uses of .phylink are followed with _
> as far as I can tell.
>
> $ git grep -Poh "\.phylink\S*"|sort|uniq -c
> 1 .phylink_fixed_state
> 2 .phylink_mac_an_restart
> 9 .phylink_mac_config
> 1 .phylink_mac_config.
> 11 .phylink_mac_link_down
> 6 .phylink_mac_link_state
> 9 .phylink_mac_link_up
> 38 .phylink_validate
Yes, you're right, but as I explained, I got something that works for
me, and I wasn't going to put more effort in.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2020-08-05 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 14:34 [PATCH] MAINTAINERS: update phylink/sfp keyword matching Russell King
2020-08-05 18:11 ` Linus Torvalds
2020-08-05 18:22 ` Russell King - ARM Linux admin
2020-08-05 18:47 ` Joe Perches
2020-08-05 21:24 ` Andrew Lunn
2020-08-05 22:09 ` Russell King - ARM Linux admin
2020-08-05 23:07 ` Joe Perches
2020-08-05 18:54 ` Joe Perches
2020-08-05 22:02 ` Russell King - ARM Linux admin
2020-08-05 22:09 ` Joe Perches
2020-08-05 22:12 ` Russell King - ARM Linux admin [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=20200805221216.GA1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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.