From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jim Quinlan <jim2101024@gmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
james.quinlan@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>,
"open list:BROADCOM BMIPS MIPS ARCHITECTURE"
<linux-mips@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] MIPS: bmips: Fix compiler warning observed on W=1 build
Date: Mon, 23 May 2022 18:28:45 +0200 [thread overview]
Message-ID: <20220523162845.GA10839@alpha.franken.de> (raw)
In-Reply-To: <20220523121639.16521-1-jim2101024@gmail.com>
On Mon, May 23, 2022 at 08:16:39AM -0400, Jim Quinlan wrote:
> The function arch_sync_dma_for_cpu_all() was used but was
> missing a prototype declaration.
>
> Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> arch/mips/bmips/dma.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/mips/bmips/dma.c b/arch/mips/bmips/dma.c
> index c535f9cb75ec..33788668cbdb 100644
> --- a/arch/mips/bmips/dma.c
> +++ b/arch/mips/bmips/dma.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0+
>
> #include <linux/types.h>
> +#include <linux/dma-map-ops.h>
> #include <asm/bmips.h>
> #include <asm/io.h>
>
>
> base-commit: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
> --
> 2.17.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-05-23 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 12:16 [PATCH v1] MIPS: bmips: Fix compiler warning observed on W=1 build Jim Quinlan
2022-05-23 15:40 ` Florian Fainelli
2022-05-23 16:28 ` Thomas Bogendoerfer [this message]
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=20220523162845.GA10839@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
/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).