From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4B77C4360C for ; Sun, 10 Jan 2021 15:09:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CFB7422ADF for ; Sun, 10 Jan 2021 15:09:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727021AbhAJPJL (ORCPT ); Sun, 10 Jan 2021 10:09:11 -0500 Received: from mail.kernel.org ([198.145.29.99]:38340 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726932AbhAJPJB (ORCPT ); Sun, 10 Jan 2021 10:09:01 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 5F77F22AAE; Sun, 10 Jan 2021 15:08:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1610291300; bh=34h9XEcoyG0a79tBf0gNmOm8EBxK+Yu03mrFZdXwVGY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=B4hhSjh128MIKlkunuIdFSNKBomwgy0FcJlokV4EXXM0xxgghL29dFCxohN7LMLvs NuxNE2VHx3orzO+YhnmpD2mTnv056UT3vjYAncfDa0J/lEB0sZUBW8/xc5qXLao0co mW8EBLOvq0JLKGUReJGSE6zkyYsdJNs6YxQErWuo= Date: Sun, 10 Jan 2021 16:09:34 +0100 From: Greg KH To: Daniel Scally Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-media@vger.kernel.org, devel@acpica.org, rjw@rjwysocki.net, lenb@kernel.org, mchehab@kernel.org, sergey.senozhatsky@gmail.com, yong.zhi@intel.com, sakari.ailus@linux.intel.com, bingbu.cao@intel.com, tian.shu.qiu@intel.com, robert.moore@intel.com, erik.kaneda@intel.com, pmladek@suse.com, rostedt@goodmis.org, andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk, laurent.pinchart+renesas@ideasonboard.com, jacopo+renesas@jmondi.org, kieran.bingham+renesas@ideasonboard.com, hverkuil-cisco@xs4all.nl, m.felsch@pengutronix.de, niklas.soderlund+renesas@ragnatech.se, prabhakar.mahadev-lad.rj@bp.renesas.com, slongerbeam@gmail.com, heikki.krogerus@linux.intel.com, Laurent Pinchart Subject: Re: [PATCH v5 03/15] device property: Return true in fwnode_device_is_available for NULL ops Message-ID: References: <20210107132838.396641-1-djrscally@gmail.com> <20210107132838.396641-4-djrscally@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210107132838.396641-4-djrscally@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 07, 2021 at 01:28:26PM +0000, Daniel Scally wrote: > Some types of fwnode_handle do not implement the device_is_available() > check, such as those created by software_nodes. There isn't really a > meaningful way to check for the availability of a device that doesn't > actually exist, so if the check isn't implemented just assume that the > "device" is present. > > Suggested-by: Laurent Pinchart > Reviewed-by: Laurent Pinchart > Reviewed-by: Andy Shevchenko > Acked-by: Sakari Ailus > Signed-off-by: Daniel Scally > --- > Changes in v5: > > - Changed the commit subject > Acked-by: Greg Kroah-Hartman