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=-7.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no 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 ECDE7C07E9B for ; Tue, 20 Jul 2021 12:24:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CF91B61164 for ; Tue, 20 Jul 2021 12:24:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237775AbhGTLoB (ORCPT ); Tue, 20 Jul 2021 07:44:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42032 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235590AbhGTLmf (ORCPT ); Tue, 20 Jul 2021 07:42:35 -0400 Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A9634C061762 for ; Tue, 20 Jul 2021 05:22:31 -0700 (PDT) Received: by mail-wr1-x434.google.com with SMTP id r11so25761353wro.9 for ; Tue, 20 Jul 2021 05:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisdown.name; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ksJ7uSYre48A5Z7zQktjRchxiOL4w4I/1HgeIzUItlA=; b=ndCld4jhIDxVjs7HgMEcmj8aOHrSU7apEUj9+c/96MWypPqQ4DLLaudBAdx8qDhjRU EnRWhNj1hjJNySeadR7468x5WNDTfkLGjY9fyOxDAwabhSDmI7GZT8RKj4HAqxOVy5eb V7JXw3ikiwb85gB7i2wWWB3wOVNTE/B7cWPDU= 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=ksJ7uSYre48A5Z7zQktjRchxiOL4w4I/1HgeIzUItlA=; b=I6mCeodj4WwHktkcer/awHGTiLxZOCjrK7fW8Sy0gbSeuEVofcJ2XrWC1FCkSJL7VX IakMv5Vyci2qheLkjmwDvFa2Ahs+13pQrWjRUR71Uu//YjENGMq9bg4IFXigZcabhLzX 0JGsyu8Ioj5zaxOBvHw9Y8EpOqKfQSx1zdtDWlQ9ahK6bnhXMXzsFiTrYqaVFI0R1OYY F4409Yh4/L9wmFGq9mm2AecSxwla3LUtNH7bKjvs0ch9gUMFRP8dHwKfUnSU+O/Fe37+ sbgkDEZcBAPGizt3aDgT7p4qJ+SSGTIKkWqgeRUtEtDLfJh3f8A5H490WmBnlObMgFCa HJew== X-Gm-Message-State: AOAM531hOxVsrYzgRmNKQzMZv7dvESZJftrV7zJdCZKV+TrhD08DjJEZ RkNWTGh27GFQRs/cW8T2C8/nJw== X-Google-Smtp-Source: ABdhPJw2SeFJ5qG/3zEIy1OkLFkh1ex3OXzZCiHOaa9CuK4hdVjKWkggxbglKSNW/nta4pdn7+Cu0A== X-Received: by 2002:a5d:504d:: with SMTP id h13mr35468419wrt.46.1626783750329; Tue, 20 Jul 2021 05:22:30 -0700 (PDT) Received: from localhost ([2620:10d:c093:400::5:d571]) by smtp.gmail.com with ESMTPSA id b6sm2296488wmj.34.2021.07.20.05.22.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Jul 2021 05:22:29 -0700 (PDT) Date: Tue, 20 Jul 2021 13:22:28 +0100 From: Chris Down To: Stephen Rothwell Cc: Jonathan Corbet , linux-doc@vger.kernel.org, Petr Mladek , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build warning after merge of the printk tree Message-ID: References: <20210720162423.75f61ce0@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6qWCzA76C1K43s0/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.1 (4b100969) (2021-06-12) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --6qWCzA76C1K43s0/ Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Chris Down writes: >+Cc: Jonathan Corbet , linux-doc@vger.kernel.org Well, let's actually Cc them this time... >Stephen Rothwell writes: >>After merging the printk tree, today's linux-next build (htmldocs) >>produced this warning: >> >>kernel/printk/printk.c:1: warning: 'printk' not found >> >>Introduced by commit >> >> 337015573718 ("printk: Userspace format indexing support") >> >>I presume that "printk" is referred to elsewhere in the documentation >>as being in this file. > >Hmm, this is an interesting one, because I think we still generally=20 >just want to refer to the API as being `printk()`. Changing it all=20 >over the place seems wrong. As you'd imagine, there are quite a few=20 >references to this name, so it requires a lot of noise all over the=20 >docs and inline comments. > >Jonathan and other docs folks, how can one tell Sphinx that when it=20 >sees printk() it's referring to a function-like macro, or otherwise=20 >squelch this reasonably? :-) --6qWCzA76C1K43s0/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEECEkprPvCOwsaJqhB340hthYRgHAFAmD2wARfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDA4 NDkyOUFDRkJDMjNCMEIxQTI2QTg0MURGOEQyMUI2MTYxMTgwNzAACgkQ340hthYR gHBJPg/9FofzESIRIFMJw31dlL3MkNdldr6Q3dhJOOcB5y9OazjDUv8wZjVaoyor feQz6IsjdtcWLYRzzq+42CsQEyLfRChPOBUKWJw9aQrlDlLv9bZfLGYaYlNNc77H naEq+gX4pNWepLcg5rFE8gVh9cQzlCYJHLIqHl/EJhN2Ql3yu34JowtTeOfbEBV8 s4LX55PvjHbjpODD40WtENJB9t9PsT038QkoJNtRSn5TIwtoh+pyYT+jhVDBX7OV lhQPz8g7XUB44JdVinjX1KTfzQ1hxhycXjnh8JDqkdeeQEA7yJeGfC4rUZJVqQBe CcQg7Z+NJZhvySqDULxk9nvaep3r6wT1EabO6DcXmOLUfVW2MNfwLuyvnBq6cUxL YOE2/Annbr+YudIamxW6xoz2SndnP5RpwAOy1odqpaVDEtWi0UuWY1RD8Jo+NRUn sieFrKlssa6khSnGhsTok8bUqut249XKYOmVxA/wAfY6pgrXqVwoEEygombE+GLQ 6xSn5otVN4u7KX266joNvuglAlrRBvnNiSA3u1JvlTBRkQBtSAvjfKwkEfcqGcTJ bpWJP3/1cx0qoXo75ldhAM1A+ItI8iQ6ndcWLwXFXqw1xCzm2rtCO1o3ovbAuFBz eqVd8AxOw12bSeEpZLjmtlIGNmW9G9hzq8xpsii4URyjMAu/k2Q= =52+O -----END PGP SIGNATURE----- --6qWCzA76C1K43s0/--