Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752024AbdFQQUN (ORCPT ); Sat, 17 Jun 2017 12:20:13 -0400 Received: from ale.deltatee.com ([207.54.116.67]:37053 "EHLO ale.deltatee.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720AbdFQQUM (ORCPT ); Sat, 17 Jun 2017 12:20:12 -0400 To: Greg Kroah-Hartman References: <20170615203729.9009-1-logang@deltatee.com> <20170615203729.9009-5-logang@deltatee.com> <20170617051429.GF6040@kroah.com> Cc: linux-ntb@googlegroups.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Jon Mason , Dave Jiang , Allen Hubbe , Bjorn Helgaas , Kurt Schwemmer , Stephen Bates From: Logan Gunthorpe Message-ID: Date: Sat, 17 Jun 2017 10:20:00 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170617051429.GF6040@kroah.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 68.147.191.165 X-SA-Exim-Rcpt-To: sbates@raithlin.com, kurt.schwemmer@microsemi.com, bhelgaas@google.com, Allen.Hubbe@emc.com, dave.jiang@intel.com, jdmason@kudzu.us, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, linux-ntb@googlegroups.com, gregkh@linuxfoundation.org X-SA-Exim-Mail-From: logang@deltatee.com Subject: Re: [RFC PATCH 04/13] switchtec: add link event notifier block X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on ale.deltatee.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 659 Lines: 21 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