All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Russell King <linux@armlinux.org.uk>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: phy: use const char * const for phylink_an_mode_str
Date: Fri, 13 Nov 2026 14:54:36 +0100	[thread overview]
Message-ID: <6af7169f.a90a51d8.32ae4c.1a7e@mx.google.com> (raw)
In-Reply-To: <86b2767e-c2a6-4bc1-ab30-c69069edf253@lunn.ch>

On Fri, Nov 13, 2026 at 02:53:05PM +0100, Andrew Lunn wrote:
> On Thu, Nov 12, 2026 at 02:13:56PM +0100, Christian Marangi wrote:
> > The local string array should use const char * const as reported by
> > checkpatch.pl. Use the correct type as to mute checkpatch warning.
> > 
> > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> 
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> 

I notice a more suited title would be to use net: phylink: ...

It's ok if I send v2 and fix the title (and keep your tag?)

-- 
	Ansuel

  reply	other threads:[~2026-11-13 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 13:13 [PATCH net-next 1/2] net: phy: use const char * const for phylink_an_mode_str Christian Marangi
2026-11-12 13:13 ` [PATCH net-next 2/2] net: phy: fix trivial whitespace/format issue Christian Marangi
2026-11-13 13:57   ` Andrew Lunn
2026-11-13 13:53 ` [PATCH net-next 1/2] net: phy: use const char * const for phylink_an_mode_str Andrew Lunn
2026-11-13 13:54   ` Christian Marangi [this message]
2026-11-16 23:30 ` patchwork-bot+netdevbpf

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=6af7169f.a90a51d8.32ae4c.1a7e@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.