From: David Miller <davem@davemloft.net>
To: hkallweit1@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: don't use netdev_[dbg, info, ..] before net_device is registered
Date: Mon, 16 Jan 2017 14:52:40 -0500 (EST) [thread overview]
Message-ID: <20170116.145240.496347319342609740.davem@davemloft.net> (raw)
In-Reply-To: <01b736a6-b9e9-05cf-0937-f6ac18ac8e3c@gmail.com>
From: Heiner Kallweit <hkallweit1@gmail.com>
Date: Sun, 15 Jan 2017 19:19:00 +0100
> Don't use netdev_info and friends before the net_device is registered.
> This avoids ugly messages like
> "meson8b-dwmac c9410000.ethernet (unnamed net_device) (uninitialized):
> Enable RX Mitigation via HW Watchdog Timer"
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Indeed, this is a side-effect of the MDIO vs. register_netdev race fix
that went in the other week.
Applied, thanks.
prev parent reply other threads:[~2017-01-16 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 18:19 [PATCH] net: stmmac: don't use netdev_[dbg, info, ..] before net_device is registered Heiner Kallweit
2017-01-16 19:52 ` David Miller [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=20170116.145240.496347319342609740.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).