Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp4414724ybx; Mon, 4 Nov 2019 13:00:38 -0800 (PST) X-Google-Smtp-Source: APXvYqyeId9VGmqbTyddOHiUVHLxA/2WxiK7M5KhUj9GKWgu101Crjx8UxP+0L50UMmJLoAEKGI2 X-Received: by 2002:a50:b685:: with SMTP id d5mr32056093ede.276.1572901238263; Mon, 04 Nov 2019 13:00:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572901238; cv=none; d=google.com; s=arc-20160816; b=LJW/iE3rHFDYf8bxpP54+viTKeEjhz0QCkhycyOe9g+XtNa3xb9OgXYW0Cg+SZI65C 57LY4vJKxluTzpmKf1C0YETRm7xRw7nwaKQTxmPeyYHwH1iFGh2MnUYNz8SSbPOZW3U8 QhQWycDGf8Rlgorsztqy0XASgsToXpPvi1JTOpeNxW2t+j6AujwWyELp3BvcsJyEsf+I XiuyC4jiFHISykuY4WtSW4mPKNjDhEzCsnfAKZn00DCtmvd0FShtH+EiVQdwYG4mMwoM 8+BHs88l8RiEth6wzkihN4PYlkCpurp8KMELEn6knC/QgyhPz6Z3bbQNn4OCxv7Ufs+L MHTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=N+vMMxPE1zexTcBhTUQBjEnFM7QQdjaq1YW9R4l5ACA=; b=kJbZbSImZHaWAfZJzRgk6USvBG1Z2avDULfTeilqmpgbN+VIDs0ix9yIctxBUAAGDi d96U2iNRTP0aOSl0uE0jMdF+mCGoiF31dwdqTsQeHT/BScoatcTGRc8zMf/4itQiPzql wQ+oUmL4DbsV4WEBBi0X34OXk2I3w6E44AR3hjAYajIu+q1EpoU0yTdDy+eThRan+ZbH 7AVPmTAgflU282tafFQPkCPUNzBBnf+wf+PNjkNAQPaADGb3XBpg2C+t4SGLWwi0nKw3 j1zWbS6ZjkxkuRsGwJhLhFtpQEmnxqKU5z0hRs9t7MKj+tJmSJhzOaoTehCcbojykPiL jDxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=nvMSvlw7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o14si1496872ejr.14.2019.11.04.13.00.13; Mon, 04 Nov 2019 13:00:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=nvMSvlw7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729446AbfKDU7R (ORCPT + 99 others); Mon, 4 Nov 2019 15:59:17 -0500 Received: from mail-qk1-f195.google.com ([209.85.222.195]:35734 "EHLO mail-qk1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728519AbfKDU7R (ORCPT ); Mon, 4 Nov 2019 15:59:17 -0500 Received: by mail-qk1-f195.google.com with SMTP id i19so9940885qki.2 for ; Mon, 04 Nov 2019 12:59:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=N+vMMxPE1zexTcBhTUQBjEnFM7QQdjaq1YW9R4l5ACA=; b=nvMSvlw7biiZ1pfK6nWpGeRxjb/qLlEauXWsgVsLny68w5JLO2+t2ewQPQN3UIteT1 9AVnanYTlL/rrDlez5ywA1Kaa/mczmwuDWP12nBYhMuz7Nmm8w6lnnyd300GrRTqIAo1 7nDV1Iqkm3knt5ctGYIZhW9CAXLKCduL7zDzAZ7iF27wNUkRDUQpN5PLka1RQqkU7+sp T6p9nUtq3wLGv9ktG6iWDlFLOz+2/STeW7loSzMyFrYmNCxmyP+D5bE7mw10kLZ5shg+ 1SeWkIvK8IIyrBK6CSyqaSXqhcumwxZw764yIfljS491asYLDOKsdG5XP4jEnrf91XN7 aCEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=N+vMMxPE1zexTcBhTUQBjEnFM7QQdjaq1YW9R4l5ACA=; b=dIdQeTDzXdxUStrRbgVsw05kLuSPZe0j6+Z9DOGoAEws+YOyzF4Z/4X/KiizyLteQT peGkusPRFYM3mHIoGmV40nOLSW5wTCEnK5/ZF4ZCchzQcTau5qlqYs2tOW9ZfoQMImGq f2VBTpNiQ4XkzHW1RofniynZ3E35g5sU82rmdvg+BYkc49npQaOb/Ij26Pc/DgU9UDBl is34xnDVPZnzperRIaRph99Q9skxSA+H2pgdMqb82ZNOWYvB5jjaOiUtmyFqLIUT9l66 8nDrZi4pBVFM+LvRtem1jXK3t8dpWrrZBPHdPc1BW99QasrBa/sqd0ZhzIfE+z+kKYAK njqw== X-Gm-Message-State: APjAAAXy1sxTPlgvNoe4SkSaO9iRvBupfxLIgo7IUfCp71lMiuoVgiLu P3tmh6fulSKbSglvRfPvsRH3Gn+Z9vw= X-Received: by 2002:a05:620a:5e3:: with SMTP id z3mr1237806qkg.160.1572901155408; Mon, 04 Nov 2019 12:59:15 -0800 (PST) Received: from ziepe.ca (hlfxns017vw-142-162-113-180.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.162.113.180]) by smtp.gmail.com with ESMTPSA id q1sm6435433qti.46.2019.11.04.12.59.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 04 Nov 2019 12:59:14 -0800 (PST) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1iRjRS-0000aI-FF; Mon, 04 Nov 2019 16:59:14 -0400 Date: Mon, 4 Nov 2019 16:59:14 -0400 From: Jason Gunthorpe To: Greg Kroah-Hartman Cc: Leon Romanovsky , Doug Ledford , linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] IB: mlx5: no need to check return value of debugfs_create functions Message-ID: <20191104205914.GI30938@ziepe.ca> References: <20191104074141.GA1292396@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191104074141.GA1292396@kroah.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 04, 2019 at 08:41:41AM +0100, Greg Kroah-Hartman wrote: > When calling debugfs functions, there is no need to ever check the > return value. The function can work or not, but the code logic should > never do something different based on this. > > Cc: Leon Romanovsky > Cc: Doug Ledford > Cc: Jason Gunthorpe > Signed-off-by: Greg Kroah-Hartman > drivers/infiniband/hw/mlx5/main.c | 62 +++++++--------------------- > drivers/infiniband/hw/mlx5/mlx5_ib.h | 9 +--- > 2 files changed, 16 insertions(+), 55 deletions(-) > > Note, I kind of need to take this through my tree now as I broke the > build due to me changing the use of debugfs_create_atomic_t() in my > tree and not noticing this being used here. Sorry about that, any > objections? I think it is fine, I don't forsee conflicts here at this point. To be clear, the build is broken in your tree and in linux-next? > And 0-day seems really broken to have missed this for the past months, > ugh, I need to stop relying on it... Yes, I've noticed it missing a lot of stuff now too. Not sure why Jason