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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AE77CC05027 for ; Fri, 17 Feb 2023 13:48:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229950AbjBQNsZ (ORCPT ); Fri, 17 Feb 2023 08:48:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229982AbjBQNsQ (ORCPT ); Fri, 17 Feb 2023 08:48:16 -0500 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F21E6ABF6; Fri, 17 Feb 2023 05:47:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1676641667; x=1708177667; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=YkkIrcqm6mJhImZ3KMLTfPPDD73LnOLWafj7JBsc3kI=; b=LwIlhWIk2Wc2XvMWWEcxvTNGMHmtEoBzVOSCU+G7WfoFOXtrWLK4v04i /+SBbc8RcW6Ef/ihb/Z4fH5Y8r45IY6sPTdYuq0jM7qFKPR1xNbpUkYzV zctmrG2Eo5f47YFFqBd/cn0weLeVX+EmOAkxd4ti12kpSWUux+2LUuYyn Ukc8UKaBk/SF7irG3zVTRpwibgYgHf/cX9PQ65uqoxMWP9DDyTMG36PgU BM3shHSZGPxr9cnCEvQA8w2HcdIZHJOYmY9o58Fo4EWp9TwDZ55ys4O84 N7eorrhhWrUWjMPvKiu+J4LRvDukOoUEnedDZq1gfRjlQsK8dOakQ7rTC A==; X-IronPort-AV: E=McAfee;i="6500,9779,10623"; a="359438416" X-IronPort-AV: E=Sophos;i="5.97,304,1669104000"; d="scan'208";a="359438416" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Feb 2023 05:47:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10623"; a="670547268" X-IronPort-AV: E=Sophos;i="5.97,304,1669104000"; d="scan'208";a="670547268" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga002.jf.intel.com with ESMTP; 17 Feb 2023 05:47:44 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1pT15S-008EKk-0e; Fri, 17 Feb 2023 15:47:42 +0200 Date: Fri, 17 Feb 2023 15:47:41 +0200 From: Andy Shevchenko To: Sakari Ailus , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Daniel Scally , Heikki Krogerus , Greg Kroah-Hartman , "Rafael J. Wysocki" , Daniel Kaehn Subject: Re: [PATCH v1 1/1] device property: Clarify description of returned value in some functions Message-ID: References: <20230217133344.79278-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230217133344.79278-1-andriy.shevchenko@linux.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 17, 2023 at 03:33:44PM +0200, Andy Shevchenko wrote: > Some of the functions do not provide Return: section on absence of which > kernel-doc complains. Besides that several functions return the fwnode > handle with incremented reference count. Add a respective note to make sure > that the caller decrements it when it's not needed anymore. > > While at it, unify the style of the Return: sections. > > Reported-by: Daniel Kaehn > Signed-off-by: Andy Shevchenko > Acked-by: Sakari Ailus > --- > > v2: rephrased the note, added tag, removed unrelated change > (all requested by Sakari) I just realized I have forgotten to bump the version. I will wait for other comments, and will issue a v3 if needed. -- With Best Regards, Andy Shevchenko