From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 3/4] iommu/of: Don't call iommu_ops->add_device directly Date: Fri, 11 Jan 2019 11:23:29 +0100 Message-ID: <20190111102328.hm6y4chellntpnhl@8bytes.org> References: <20181211150513.15161-1-joro@8bytes.org> <20181211150513.15161-4-joro@8bytes.org> <30d86186-e0a2-2be1-2295-20510fbd74ba@samsung.com> <20181219143451.GY16835@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Geert Uytterhoeven Cc: Marek Szyprowski , Linux IOMMU , Linux Kernel Mailing List , Joerg Roedel , Sudeep Holla , Robin Murphy , Krzysztof Kozlowski List-Id: iommu@lists.linux-foundation.org Hi Geert, On Thu, Dec 20, 2018 at 04:42:17PM +0100, Geert Uytterhoeven wrote: > > - return ops->add_device(dev); > > + if (ops) > > Is this sufficient? The old code checked for ops->add_device != NULL, > too. Robin brought up that all iommu-ops implementations support the add_device call-back, so we can remove that check and make the call-back mandatory for new implementations too. Regards, Joerg