[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7f59aaf-f525-b03f-7492-9c372bc752b9@deltatee.com>
Date: Sat, 17 Jun 2017 10:20:00 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-ntb@...glegroups.com, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, Jon Mason <jdmason@...zu.us>,
Dave Jiang <dave.jiang@...el.com>,
Allen Hubbe <Allen.Hubbe@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Kurt Schwemmer <kurt.schwemmer@...rosemi.com>,
Stephen Bates <sbates@...thlin.com>
Subject: Re: [RFC PATCH 04/13] switchtec: add link event notifier block
On 16/06/17 11:14 PM, Greg Kroah-Hartman wrote:
> You do know about ftrace, right? It's good to drop debugging code like
> this for "final" versions.
I've never actually used it but maybe I should give it a try. I'll
remove these debug lines.
>> +
>> + blocking_notifier_call_chain(&stdev->link_notifier, 0, stdev);
>> +}
>
> Do you really need a notifier call chain? How many different things are
> going to "hook up" to this? I ask as they tend to get really messy over
> time while direct callbacks are easier to handle and manage.
Ok, understood. I only expect the one callback at this time so I'll
change it to a single function pointer.
Logan
Powered by blists - more mailing lists