From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: phy: add GBit master / slave error detection
Date: Thu, 19 Jul 2018 16:46:37 +0200 [thread overview]
Message-ID: <20180719144637.GA9119@lunn.ch> (raw)
In-Reply-To: <8ccaeb57-3150-65ce-2310-3aac52f446c5@gmail.com>
> > AFAIR there was a patch a while ago from Mellanox guys that was possibly
> > extending the link notification with an error cause, this sounds like
> > something that could be useful to report to user space somehow to help
> > troubleshoot link down events.
> >
> Do you by chance have a reference to this patch? There's heavy development
> on the Mellanox drivers with a lot of patches.
Hi Heiner, Florian
A general mechanism has been added to allow error messages to be
reported via netlink sockets. I think wifi was the first to actually
make use of it, since i think Johannes Berg did the core work, but
other parts of the stack have also started using it.
Just picking a commit at random, maybe not the best of examples:
Fixes: 768075ebc238 ("nl80211: add a few extended error strings to key parsing")
Andrew
next prev parent reply other threads:[~2018-07-19 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 6:14 [PATCH net-next] net: phy: add GBit master / slave error detection Heiner Kallweit
2018-07-18 9:22 ` Florian Fainelli
2018-07-19 5:54 ` Heiner Kallweit
2018-07-19 14:46 ` Andrew Lunn [this message]
2018-07-19 21:11 ` Heiner Kallweit
2018-07-19 21:45 ` Andrew Lunn
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=20180719144637.GA9119@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--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 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.