From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: "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,
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: Re: [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 14:28:33 +0530 [thread overview]
Message-ID: <CA+G9fYu__OOvk-ESXoOqbd-Lk+CmO8CSQ8chEFf3MyeTjKtp9g@mail.gmail.com> (raw)
In-Reply-To: <6249735f-e6b7-1331-eb2b-361bb17d6115@opensource.wdc.com>
> I just posted a fix. As I do not have the environment to compile test
> mips, could someone test please ? I will send the fix to Linus asap
> after confirmation that it is OK.
Please share your patch / patch link. I will test it with tuxmake.
you may also give a try with these easy steps.
# 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
- Naresh
next prev parent reply other threads:[~2022-01-21 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 8:02 [next] mips: cavium_octeon_defconfig: pata_octeon_cf.c:598:23: error: passing argument 1 of 'trace_ata_bmdma_stop' from incompatible pointer type Naresh Kamboju
2022-01-21 8:34 ` Damien Le Moal
2022-01-21 8:58 ` Naresh Kamboju [this message]
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+G9fYu__OOvk-ESXoOqbd-Lk+CmO8CSQ8chEFf3MyeTjKtp9g@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).