From: Edward Cree <ecree@solarflare.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>, <kbuild-all@lists.01.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [renesas-drivers:master 69/80] drivers/net/ethernet/sfc/efx_common.c:1232:19: sparse: sparse: incompatible types for operation (==):
Date: Wed, 15 Jul 2020 10:04:41 +0100 [thread overview]
Message-ID: <4106f92f-d3c4-a997-12bf-33ac6fc01758@solarflare.com> (raw)
In-Reply-To: <CAMuHMdVDha=xAAHjKma4pm1bgNt=go0HgUMyCrc3H87cF0f5SA@mail.gmail.com>
On 15/07/2020 09:55, Geert Uytterhoeven wrote:
> Indeed, it should be fixed at the core, not in an integration testing tree.
> BTW, did it show up in linux-next, too, or have I done a bad merge conflict
> resolution?
Looking at linux-next, it appears tha|t efx_io_error_detected()||there
|| takes a pci_channel_state_t, so Bjorn's fix has already been applied
there, probably by way of merging pci/next (which applies a conjugate
fix to efx.c:||efx_io_error_detected()) and net-next (which moves the
function to efx_common.c).
For whatever reason renesas must've come up with a different merge
resolution, hence why they're seeing this.
-ed
|||||||||||||
next prev parent reply other threads:[~2020-07-15 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202007150206.kfukZxuy%lkp@intel.com>
2020-07-14 18:56 ` [renesas-drivers:master 69/80] drivers/net/ethernet/sfc/efx_common.c:1232:19: sparse: sparse: incompatible types for operation (==): Bjorn Helgaas
2020-07-15 8:47 ` Edward Cree
2020-07-15 8:55 ` Geert Uytterhoeven
2020-07-15 9:04 ` Edward Cree [this message]
2020-07-15 10:21 ` Luc Van Oostenryck
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=4106f92f-d3c4-a997-12bf-33ac6fc01758@solarflare.com \
--to=ecree@solarflare.com \
--cc=geert@linux-m68k.org \
--cc=helgaas@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=luc.vanoostenryck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox