All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Linux Networking <netdev@vger.kernel.org>
Cc: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	Jiri Pirko <jiri@nvidia.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the net-next tree
Date: Mon, 18 Sep 2023 14:43:14 +0700	[thread overview]
Message-ID: <ZQf_kmZZYGFJFZMp@debian.me> (raw)
In-Reply-To: <20230918131521.155e9e63@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2874 bytes --]

On Mon, Sep 18, 2023 at 01:15:21PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the net-next tree, today's linux-next build (htmldocs)
> produced these warnings:
> 
> Documentation/driver-api/dpll.rst:427: ERROR: Error in "code-block" directive:
> maximum 1 argument(s) allowed, 18 supplied.
> 
> .. code-block:: c
>         static const struct dpll_device_ops dpll_ops = {
>                 .lock_status_get = ptp_ocp_dpll_lock_status_get,
>                 .mode_get = ptp_ocp_dpll_mode_get,
>                 .mode_supported = ptp_ocp_dpll_mode_supported,
>         };
> 
>         static const struct dpll_pin_ops dpll_pins_ops = {
>                 .frequency_get = ptp_ocp_dpll_frequency_get,
>                 .frequency_set = ptp_ocp_dpll_frequency_set,
>                 .direction_get = ptp_ocp_dpll_direction_get,
>                 .direction_set = ptp_ocp_dpll_direction_set,
>                 .state_on_dpll_get = ptp_ocp_dpll_state_get,
>         };
> Documentation/driver-api/dpll.rst:444: ERROR: Error in "code-block" directive:
> maximum 1 argument(s) allowed, 21 supplied.
> 
> .. code-block:: c
>         clkid = pci_get_dsn(pdev);
>         bp->dpll = dpll_device_get(clkid, 0, THIS_MODULE);
>         if (IS_ERR(bp->dpll)) {
>                 err = PTR_ERR(bp->dpll);
>                 dev_err(&pdev->dev, "dpll_device_alloc failed\n");
>                 goto out;
>         }
> 
>         err = dpll_device_register(bp->dpll, DPLL_TYPE_PPS, &dpll_ops, bp);
>         if (err)
>                 goto out;
> 
>         for (i = 0; i < OCP_SMA_NUM; i++) {
>                 bp->sma[i].dpll_pin = dpll_pin_get(clkid, i, THIS_MODULE, &bp->sma[i].dpll_prop);
>                 if (IS_ERR(bp->sma[i].dpll_pin)) {
>                         err = PTR_ERR(bp->dpll);
>                         goto out_dpll;
>                 }
> 
>                 err = dpll_pin_register(bp->dpll, bp->sma[i].dpll_pin, &dpll_pins_ops,
>                                         &bp->sma[i]);
>                 if (err) {
>                         dpll_pin_put(bp->sma[i].dpll_pin);
>                         goto out_dpll;
>                 }
>         }
> Documentation/driver-api/dpll.rst:474: ERROR: Error in "code-block" directive:
> maximum 1 argument(s) allowed, 12 supplied.
> 
> .. code-block:: c
>         while (i) {
>                 --i;
>                 dpll_pin_unregister(bp->dpll, bp->sma[i].dpll_pin, &dpll_pins_ops, &bp->sma[i]);
>                 dpll_pin_put(bp->sma[i].dpll_pin);
>         }
>         dpll_device_put(bp->dpll);
> 
> 
> Introduced by commit
> 
>   dbb291f19393 ("dpll: documentation on DPLL subsystem interface")
> 

Oops, I forgot to review dpll series. Will fix.

Thanks for the report!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-09-18  7:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  3:15 linux-next: build warnings after merge of the net-next tree Stephen Rothwell
2023-09-18  7:43 ` Bagas Sanjaya [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-11  8:31 Stephen Rothwell
2025-08-01  4:42 ` Stephen Rothwell
2025-08-11  9:53   ` Paolo Abeni
2025-08-12  4:36     ` Stephen Rothwell
2024-11-04  5:30 Stephen Rothwell
2023-12-04  4:47 Stephen Rothwell
2023-06-26  6:29 Stephen Rothwell
2023-09-05 22:55 ` Stephen Rothwell
2023-09-05 23:44   ` Jakub Kicinski
2023-06-13  6:31 Stephen Rothwell
2023-06-20 16:15 ` Jakub Kicinski
2023-06-20 23:12   ` Saeed Mahameed
2022-11-14  7:31 Stephen Rothwell
2022-11-14  8:00 ` Akira Yokosawa
2021-06-15 11:23 Stephen Rothwell
2021-06-15 11:12 Stephen Rothwell
2021-03-18  6:22 Stephen Rothwell
2021-02-18 20:52 Stephen Rothwell
2021-02-19  8:44 ` Stephen Rothwell
2021-02-19 14:57   ` Kalle Valo
2020-12-14  9:10 Stephen Rothwell
2020-12-21  1:28 ` Stephen Rothwell
2021-01-05  6:19   ` Stephen Rothwell
2019-11-05  1:45 Stephen Rothwell
2017-03-20  6:07 Stephen Rothwell
2017-01-18  0:37 Stephen Rothwell
2016-11-22  1:22 Stephen Rothwell
2016-11-22  1:28 ` Florian Fainelli
2016-11-22  8:23   ` Thomas Petazzoni
2015-06-20 13:12 Stephen Rothwell
2015-06-20 13:12 ` Stephen Rothwell
2015-06-20 17:40 ` Florian Westphal
2015-06-20 17:40   ` Florian Westphal
2015-06-20 18:31   ` Pablo Neira Ayuso
2015-06-20 18:31     ` Pablo Neira Ayuso
2015-05-14  7:12 Stephen Rothwell
2015-05-14  7:12 ` Stephen Rothwell
2015-05-14 14:47 ` Willem de Bruijn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZQf_kmZZYGFJFZMp@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=vadim.fedorenko@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.