linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the rcu tree
Date: Mon, 7 Dec 2020 10:48:51 -0700	[thread overview]
Message-ID: <20201207104851.20400bba@lwn.net> (raw)
In-Reply-To: <20201207164704.GH2657@paulmck-ThinkPad-P72>

On Mon, 7 Dec 2020 08:47:04 -0800
"Paul E. McKenney" <paulmck@kernel.org> wrote:

> I freely confess that I have absolutely no idea what it doesn't like.
> It is complaining about this header comment, correct?
> 
> /**
>  * kmem_last_alloc_stack - Get return address and stack for last allocation
>  * @object: object for which to find last-allocation return address.
>  * @stackp: %NULL or pointer to location to place return-address stack.
>  * @nstackp: maximum number of return addresses that may be stored.
>  *
>  * If the pointer references a slab-allocated object and if sufficient
>  * debugging is enabled, return the return address for the corresponding
>  * allocation.  If stackp is non-%NULL in %CONFIG_STACKTRACE kernels running
>  * the slub allocator, also copy the return-address stack into @stackp,
>  * limited by @nstackp.  Otherwise, return %NULL or an appropriate error
>  * code using %ERR_PTR().
>  *
>  * Return: return address from last allocation, %NULL or negative error code.
>  */

The problem is the %ERR_PTR().  I'm honestly not quite sure why, Sphinx is
being a little weird there.  But in any case the % notation is supposed to
mark a constant, which is not the case here.  I'd just take the % signs
out.

jon

  reply	other threads:[~2020-12-07 17:49 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07  8:20 linux-next: build warning after merge of the rcu tree Stephen Rothwell
2020-12-07 16:47 ` Paul E. McKenney
2020-12-07 17:48   ` Jonathan Corbet [this message]
2020-12-07 18:53     ` Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2024-08-09  4:21 Stephen Rothwell
2024-01-25  3:33 Stephen Rothwell
2024-01-25 13:18 ` Paul E. McKenney
2023-07-26  2:32 Stephen Rothwell
2023-07-26  3:33 ` Paul E. McKenney
2023-07-26  3:48   ` Paul E. McKenney
2023-07-26  6:37     ` Stephen Rothwell
2023-04-06  4:43 Stephen Rothwell
2023-04-06 14:15 ` Paul E. McKenney
2023-03-21  2:50 Stephen Rothwell
2023-03-21  3:01 ` Boqun Feng
2022-11-07  3:26 Stephen Rothwell
2022-11-07  5:02 ` Paul E. McKenney
2022-06-15  5:38 Stephen Rothwell
2022-06-15 13:55 ` Paul E. McKenney
2021-03-04  1:41 Stephen Rothwell
2021-03-04  1:48 ` Paul E. McKenney
2020-03-10  2:27 Stephen Rothwell
2020-03-10  2:49 ` Paul E. McKenney
2019-12-12  5:06 Stephen Rothwell
2019-12-12  6:02 ` Paul E. McKenney
2019-12-12  6:38   ` Eric Dumazet
2019-12-12  6:57     ` Eric Dumazet
2020-01-10 21:57       ` Paul E. McKenney
2020-01-15 16:42       ` Paul E. McKenney
2019-12-12 11:40   ` Stephen Rothwell
2019-12-13  1:31     ` Paul E. McKenney
2020-01-06 17:51 ` Olof Johansson
2020-01-06 18:10   ` Paul E. McKenney
2020-01-06 21:08     ` Olof Johansson
2020-01-06 21:43       ` Paul E. McKenney
2017-06-21  6:48 Stephen Rothwell
2017-06-21 13:30 ` Paul E. McKenney
2011-08-24  4:23 Stephen Rothwell
2011-08-24 12:27 ` Paul E. McKenney
2011-08-25  0:46   ` Arnaud Lacombe
2011-08-25  5:04     ` Paul E. McKenney
2011-03-25  5:05 Stephen Rothwell
2011-03-25 19:23 ` Paul E. McKenney
2010-09-06  2:14 Stephen Rothwell
2010-09-06  2:32 ` Neil Brown
2010-09-06  3:02   ` Stephen Rothwell
2010-09-06  5:37   ` Paul E. McKenney

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=20201207104851.20400bba@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).