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: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the devicetree tree
Date: Tue, 6 Mar 2018 12:03:34 +1100	[thread overview]
Message-ID: <20180306120334.0411e8eb@canb.auug.org.au> (raw)

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

Hi Rob,

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

arch/powerpc/boot/fdt_ro.c: In function 'fdt_get_name':
arch/powerpc/boot/fdt_ro.c:253:10: warning: implicit declaration of function 'strrchr'; did you mean 'strchr'? [-Wimplicit-function-declaration]
   leaf = strrchr(nameptr, '/');
          ^~~~~~~
          strchr
arch/powerpc/boot/fdt_ro.c:253:8: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
   leaf = strrchr(nameptr, '/');
        ^

Introduced by commit

  c0e8e5234671 ("scripts/dtc: Update to upstream version v1.4.6-9-gaadd0b65c987")

I presume that commit

  d308701979aa ("powerpc: boot: add strrchr function")

was meant to address this, but it seems that it has no completely.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2018-03-06  1:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06  1:03 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-20  5:36 linux-next: build warning after merge of the devicetree tree Stephen Rothwell
2021-10-26  2:44 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
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=20180306120334.0411e8eb@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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.