[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190423103715.044aab13@x1.home>
Date: Tue, 23 Apr 2019 10:37:15 -0600
From: Alex Williamson <alex.williamson@...hat.com>
To: Alex G <mr.nuke.me@...il.com>
Cc: bhelgaas@...gle.com, helgaas@...nel.org, linux-pci@...r.kernel.org,
austin_bolen@...l.com, alex_gagniuc@...lteam.com,
keith.busch@...el.com, Shyam_Iyer@...l.com, lukas@...ner.de,
okaya@...nel.org, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PCI/LINK: Account for BW notification in vector
calculation
On Tue, 23 Apr 2019 11:27:39 -0500
Alex G <mr.nuke.me@...il.com> wrote:
> On 4/23/19 11:22 AM, Alex Williamson wrote:
> > Nor should pci-core decide what link speed changes are intended or
> > errors. Minimally we should be enabling drivers to receive this
> > feedback. Thanks,
>
> Not errors. pci core reports that a link speed change event has occured.
> Period.
And it shows up in dmesg, and what do users (and developers) think when
things are repeatedly reported in dmesg? Whether this is "information"
or "error", it's spamming dmesg, irrelevant, and confusing. Thanks,
Alex
Powered by blists - more mailing lists