Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp4227926pxb; Mon, 8 Feb 2021 10:53:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJz8KomFCfW+0Ssoh0U9xNf9qhTrvnVO3fjhktiVkePZXvXxRGexsNRIaXjpyTXOlgf80zuZ X-Received: by 2002:a17:906:3757:: with SMTP id e23mr18613056ejc.93.1612810388198; Mon, 08 Feb 2021 10:53:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612810388; cv=none; d=google.com; s=arc-20160816; b=JuEJ7PVuqU2FFCHQ06zQj83CK8oULDXlqPIbcPEY7/6mtTcP3/saxnN1Q/1BdvRxHg eH5qzUvmo62LDhIfJdmCYxSqWPhWZ/ugVUx1moGAe4l4JZ4DZnw2e5qjkOQ0BqLIiut2 BEHYSdfItWAEOtpdFJHk0fggFkY3PgWCOlSOzY/BR4j7AnwCMfsnzyH4kuuLSQxfl0oh xsTAiNCSDbGcHvnK893gGItb3x4kwQ332MNPXldgSloYOgq1lX2y+DZHzGknRZUIMvDN Hi7i51Gt7i0/duNnHNHgv62E9pia+os7qJJUoMDTy7EC6hOg1ThdXzlEmLIu/MbCzONf pkCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id; bh=ZQS6omEukevL+zhSwICElyGgTqzeEaicIDJi8o71PA8=; b=zg74miqylwywSA6ABHSMH2F9TZa+D0O4W2pvCkqmoVrmnWvpm8v5mxbzmvKTX6rHA5 Kc+8tGNjBBWrHwuGp4mdXza6jhURfotxflHIf2l7zAxTvGaTBF+Tc97rcjdeK/sE+HLX jE12TYxmrq6AUp2Gi5h6f3VLuVBVJf0D7oYycgCQVMS+/efW7H9jQcjoded9EY8UGs+R +3Eud4r6p+3b98+oMVtkrv3yphtO6RuYYzBJ1Bvg1lZ/RWG1cAXqVkqk8htqOECwDl/R O+rPn8lhVYqi5mk8w3/GLxYBUp/CdUWz/2zWiZtdkk8iSFUJWtuxJDiZf9KOUwFiWtsv 8vcQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h18si1902912eds.493.2021.02.08.10.52.44; Mon, 08 Feb 2021 10:53:08 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235823AbhBHSwK (ORCPT + 99 others); Mon, 8 Feb 2021 13:52:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46670 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233586AbhBHQ6o (ORCPT ); Mon, 8 Feb 2021 11:58:44 -0500 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9CB77C061786; Mon, 8 Feb 2021 08:58:04 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: ezequiel) with ESMTPSA id E79481F412A7 Message-ID: <4af499f5931d6b04a42787ae17525c63247573e6.camel@collabora.com> Subject: Re: linux-next: build warning after merge of the v4l-dvb tree From: Ezequiel Garcia To: Sakari Ailus Cc: Stephen Rothwell , Mauro Carvalho Chehab , Linux Kernel Mailing List , Linux Next Mailing List Date: Mon, 08 Feb 2021 13:57:56 -0300 In-Reply-To: <20210208164618.GY32460@paasikivi.fi.intel.com> References: <20210208233716.16d962ad@canb.auug.org.au> <56cd99bbf526b43507579b5775bac5f885319866.camel@collabora.com> <20210208164618.GY32460@paasikivi.fi.intel.com> Organization: Collabora Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.2-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2021-02-08 at 18:46 +0200, Sakari Ailus wrote: > Hi Ezequiel, > > Thanks for addressing this. > > On Mon, Feb 08, 2021 at 01:42:21PM -0300, Ezequiel Garcia wrote: > > Hi Stephen, > > > > On Mon, 2021-02-08 at 23:37 +1100, Stephen Rothwell wrote: > > > Hi all, > > > > > > After merging the v4l-dvb tree, today's linux-next build (htmldocs) > > > produced this warning: > > > > > > include/media/v4l2-async.h:178: warning: expecting prototype for v4l2_async_notifier_add_fwnode_subdev(). Prototype was for > > > __v4l2_async_notifier_add_fwnode_subdev() instead > > > include/media/v4l2-async.h:207: warning: expecting prototype for v4l2_async_notifier_add_fwnode_remote_subdev(). Prototype was for > > > __v4l2_async_notifier_add_fwnode_remote_subdev() instead > > > include/media/v4l2-async.h:230: warning: expecting prototype for v4l2_async_notifier_add_i2c_subdev(). Prototype was for > > > __v4l2_async_notifier_add_i2c_subdev() instead > > > > > > Maybe introduced by commit > > > > > >   c1cc23625062 ("media: v4l2-async: Discourage use of v4l2_async_notifier_add_subdev") > > > > > > > Thanks for spotting this. Should be fixed by: > > > > diff --git a/include/media/v4l2-async.h b/include/media/v4l2-async.h > > index 6f22daa6f067..3785445282fc 100644 > > --- a/include/media/v4l2-async.h > > +++ b/include/media/v4l2-async.h > > @@ -157,7 +157,7 @@ int __v4l2_async_notifier_add_subdev(struct v4l2_async_notifier *notifier, > >                                    struct v4l2_async_subdev *asd); > >   > >  /** > > - * v4l2_async_notifier_add_fwnode_subdev - Allocate and add a fwnode async > > + * __v4l2_async_notifier_add_fwnode_subdev - Allocate and add a fwnode async > > The problem with the approach is that this no longer documents the API that > drivers are intended to use, but the intermediate one. I guess fixing > this properly could require changes to kerneldoc so I have no objections to > the approach. > Right, but do we have any other solution here? > >   *                             subdev to the notifier's master asd_list. > >   * > >   * @notifier: pointer to &struct v4l2_async_notifier > > @@ -181,7 +181,7 @@ __v4l2_async_notifier_add_fwnode_subdev(struct v4l2_async_notifier *notifier, > >                                                    sizeof(__type))) > >   > >  /** > > - * v4l2_async_notifier_add_fwnode_remote_subdev - Allocate and add a fwnode > > + * __v4l2_async_notifier_add_fwnode_remote_subdev - Allocate and add a fwnode > >   *                                               remote async subdev to the > >   *                                               notifier's master asd_list. > >   * > > @@ -210,7 +210,7 @@ __v4l2_async_notifier_add_fwnode_remote_subdev(struct v4l2_async_notifier *notif > >                                                           sizeof(__type))) > >   > >  /** > > - * v4l2_async_notifier_add_i2c_subdev - Allocate and add an i2c async > > + * __v4l2_async_notifier_add_i2c_subdev - Allocate and add an i2c async > >   *                             subdev to the notifier's master asd_list. > >   * > >   * @notifier: pointer to &struct v4l2_async_notifier > > @@ -228,7 +228,7 @@ struct v4l2_async_subdev * > >  __v4l2_async_notifier_add_i2c_subdev(struct v4l2_async_notifier *notifier, > >                                      int adapter_id, unsigned short address, > >                                      unsigned int asd_struct_size); > > -#define v4l2_async_notifier_add_i2c_subdev(__notifier, __adap, __addr, __type) \ > > +#define v4l2_async_notifier_i2c(__notifier, __adap, __addr, __type)    \ > > I guess this change was not intentional? > Indeed :) Thanks, Ezequiel