All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Herring <robherring2@gmail.com>
Cc: Frank Rowand <frowand.list@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the devicetree tree
Date: Mon, 20 Feb 2023 16:36:38 +1100	[thread overview]
Message-ID: <20230220163638.04e9d0c4@canb.auug.org.au> (raw)

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

Hi all,

After merging the devicetree tree, today's linux-next build (htmldocs)
produced this warning:

include/linux/of.h:115: warning: cannot understand function prototype: 'const struct kobj_type of_node_ktype; '

Introduced by commit

  39459ce717b8 ("of: dynamic: add lifecycle docbook info to node creation functions")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-02-20  5:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  5:36 Stephen Rothwell [this message]
2023-03-10  0:32 ` [PATCH] of: fix htmldocs build warning Stephen Rothwell
2023-03-10  4:52   ` Randy Dunlap
2023-03-22  3:21     ` Randy Dunlap
2023-03-22  7:00   ` [PATCH] of: fix htmldocs build warnings Stephen Rothwell
2023-03-22 18:50     ` Randy Dunlap
2023-07-02 22:51       ` Stephen Rothwell
2023-07-13  6:10     ` Stephen Rothwell
2023-07-24  3:55       ` Stephen Rothwell
2023-07-24 13:13         ` Rob Herring
  -- strict thread matches above, loose matches on Subject: below --
2021-10-26  2:44 linux-next: build warning after merge of the devicetree tree Stephen Rothwell
2021-08-24  3:18 Stephen Rothwell
2021-08-24 12:35 ` Rob Herring
2021-09-02 22:34   ` Stephen Rothwell
2021-09-03  0:38     ` Rob Herring
2021-09-03  0:38       ` Rob Herring
2018-05-09  6:04 Stephen Rothwell
2018-05-09 12:17 ` Rob Herring
2018-05-29  6:04   ` Stephen Rothwell
2018-03-06  1:05 Stephen Rothwell
2018-03-06  2:34 ` Rob Herring
2018-03-06  3:11   ` Stephen Rothwell
2018-03-06  1:03 Stephen Rothwell
2017-04-28  2:45 Stephen Rothwell
2017-05-03  5:44 ` Stephen Rothwell
2017-05-03 12:12   ` Rob Herring
2017-05-03 12:46     ` Stephen Rothwell
2010-10-21  2:37 Stephen Rothwell
2010-10-21  3:26 ` Grant Likely
2010-10-21  8:05   ` Ingo Molnar
2010-10-21 17:04     ` Grant Likely
2010-07-30  4:54 Stephen Rothwell
2010-07-30  6:10 ` Grant Likely

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=20230220163638.04e9d0c4@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robherring2@gmail.com \
    /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.