All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Thompson <davthompson@nvidia.com>
To: <bryan.whitehead@microchip.com>, <UNGLinuxDriver@microchip.com>,
	<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	David Thompson <davthompson@nvidia.com>
Subject: [PATCH net-next v2 0/2] net: lan743x: cleanup netdev-based logging
Date: Wed, 27 May 2026 18:18:56 +0000	[thread overview]
Message-ID: <cover.1779903597.git.davthompson@nvidia.com> (raw)

This series improves netdev-based logging in the lan743x driver by
addressing the issue where several log entries at boot include the
warning "(unnamed net_device) (uninitialized)".

The first patch introduces a "message level" module parameter and uses
netif_msg_init(), allowing msg_enable to be configured at load time.

The second patch ensures that netdev-based logging is only used after
netdev registration has completed successfully.

v2:
- Added patch 1
- Changed target repo from "net" to "net-next" 

David Thompson (2):
  net: lan743x: add "message level" module parameter
  net: lan743x: avoid netdev-based logging before netdev registration

 drivers/net/ethernet/microchip/lan743x_main.c | 87 ++++++++++++-------
 1 file changed, 57 insertions(+), 30 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-05-27 18:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 18:18 David Thompson [this message]
2026-05-27 18:18 ` [PATCH net-next v2 1/2] net: lan743x: add "message level" module parameter David Thompson
2026-05-27 20:35   ` Jacob Keller
2026-05-28 14:32     ` David Thompson
2026-05-27 18:18 ` [PATCH net-next v2 2/2] net: lan743x: avoid netdev-based logging before netdev registration David Thompson
2026-05-27 20:32   ` Jacob Keller
2026-05-28 15:48     ` David Thompson

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=cover.1779903597.git.davthompson@nvidia.com \
    --to=davthompson@nvidia.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.