linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Rob Herring <robh@kernel.org>
Subject: Re: linux-next: build warning after merge of the mips tree
Date: Thu, 30 Jul 2020 09:04:40 +0800	[thread overview]
Message-ID: <f2a9f50d-5299-04f8-146b-e09df8943367@flygoat.com> (raw)
In-Reply-To: <20200729203142.18248463@canb.auug.org.au>



在 2020/7/29 下午6:31, Stephen Rothwell 写道:
> Hi all,
>
> After merging the mips tree, today's linux-next build (powerpc
> allnoconfig) produced this warning:
>
> drivers/of/address.c:104:21: warning: 'of_bus_pci_get_flags' defined but not used [-Wunused-function]
>    104 | static unsigned int of_bus_pci_get_flags(const __be32 *addr)
>        |                     ^~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
>    2f96593ecc37 ("of_address: Add bus type match for pci ranges parser")

Thanks for catching that!
Fix patch sent.

Btw: Neither James nor Ralf is still active at Linux-MIPS.

- Jiaxun

>

  reply	other threads:[~2020-07-30  1:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 10:31 linux-next: build warning after merge of the mips tree Stephen Rothwell
2020-07-30  1:04 ` Jiaxun Yang [this message]
2020-07-30  1:40   ` Stephen Rothwell
2020-07-30  1:56     ` Jiaxun Yang
2020-07-30 22:39       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2011-08-20 23:43 Stephen Rothwell
2011-08-22  0:48 ` Stephen Rothwell
2011-08-24 23:18   ` Stephen Rothwell

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=f2a9f50d-5299-04f8-146b-e09df8943367@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=jhogan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=robh@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tsbogend@alpha.franken.de \
    /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).