From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: "open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)"
<linux-ide@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mips@vger.kernel.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Zeal Robot <zealci@zte.com.cn>,
Minghao Chi <chi.minghao@zte.com.cn>,
CGEL ZTE <cgel.zte@gmail.com>
Subject: [next] mips: cavium_octeon_defconfig: pata_octeon_cf.c:598:23: error: passing argument 1 of 'trace_ata_bmdma_stop' from incompatible pointer type
Date: Fri, 21 Jan 2022 13:32:19 +0530 [thread overview]
Message-ID: <CA+G9fYtq0wzSeG8YG-a+=KrbdWqHJMXk1hvq0FKeAvj9sZAK2g@mail.gmail.com> (raw)
Linux next-20220106..next-20220121 mips build failing with gcc-10.
drivers/ata/pata_octeon_cf.c: In function 'octeon_cf_dma_finished':
drivers/ata/pata_octeon_cf.c:598:23: error: passing argument 1 of
'trace_ata_bmdma_stop' from incompatible pointer type
[-Werror=incompatible-pointer-types]
598 | trace_ata_bmdma_stop(qc, &qc->tf, qc->tag);
| ^~
| |
| struct ata_queued_cmd *
In file included from include/trace/events/libata.h:10,
from drivers/ata/pata_octeon_cf.c:22:
include/trace/events/libata.h:414:33: note: expected 'struct ata_port
*' but argument is of type 'struct ata_queued_cmd *'
414 | TP_PROTO(struct ata_port *ap, const struct ata_taskfile
*tf, unsigned int tag),
| ~~~~~~~~~~~~~~~~~^~
include/linux/tracepoint.h:342:34: note: in definition of macro
'__DECLARE_TRACE'
342 | static inline void trace_##name(proto) \
| ^~~~~
include/linux/tracepoint.h:419:24: note: in expansion of macro 'PARAMS'
419 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
| ^~~~~~
include/linux/tracepoint.h:542:2: note: in expansion of macro 'DECLARE_TRACE'
542 | DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
| ^~~~~~~~~~~~~
include/linux/tracepoint.h:542:22: note: in expansion of macro 'PARAMS'
542 | DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
| ^~~~~~
include/trace/events/libata.h:413:1: note: in expansion of macro 'DEFINE_EVENT'
413 | DEFINE_EVENT(ata_exec_command_template, ata_bmdma_stop,
| ^~~~~~~~~~~~
include/trace/events/libata.h:414:7: note: in expansion of macro 'TP_PROTO'
414 | TP_PROTO(struct ata_port *ap, const struct ata_taskfile
*tf, unsigned int tag),
| ^~~~~~~~
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:289: drivers/ata/pata_octeon_cf.o] Error 1
make[3]: Target '__build' not remade because of errors.
make[2]: *** [scripts/Makefile.build:572: drivers/ata] Error 2
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
metadata:
git branch: master
git repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git describe: next-20220121
kernel-config: https://builds.tuxbuild.com/23zIBGjQZgIYW8OnGcYjwWlj40X/config
build: https://builds.tuxbuild.com/23zIBGjQZgIYW8OnGcYjwWlj40X/
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
#
# See https://docs.tuxmake.org/ for complete documentation.
# Original tuxmake command with fragments listed below.
tuxmake --runtime podman --target-arch mips --toolchain gcc-10
--kconfig cavium_octeon_defconfig
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2022-01-21 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 8:02 Naresh Kamboju [this message]
2022-01-21 8:34 ` [next] mips: cavium_octeon_defconfig: pata_octeon_cf.c:598:23: error: passing argument 1 of 'trace_ata_bmdma_stop' from incompatible pointer type Damien Le Moal
2022-01-21 8:58 ` Naresh Kamboju
2022-01-21 9:17 ` Damien Le Moal
2022-01-21 9:38 ` Naresh Kamboju
2022-01-21 9:27 ` Damien Le Moal
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='CA+G9fYtq0wzSeG8YG-a+=KrbdWqHJMXk1hvq0FKeAvj9sZAK2g@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=tsbogend@alpha.franken.de \
--cc=zealci@zte.com.cn \
/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).