From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: David Miller <davem@davemloft.net>
Cc: hulkci@huawei.com, tomeu.vizoso@collabora.com,
broonie@kernel.org, khilman@baylibre.com, mgalka@collabora.com,
enric.balletbo@collabora.com, yuehaibing@huawei.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com
Subject: Re: net-next/master bisection: boot on beaglebone-black
Date: Fri, 22 Nov 2019 18:02:06 +0000 [thread overview]
Message-ID: <bfe5e987-e0b5-6c89-f193-6666be203532@collabora.com> (raw)
In-Reply-To: <20191122.093657.95680289541075120.davem@davemloft.net>
On 22/11/2019 17:36, David Miller wrote:
> From: "kernelci.org bot" <bot@kernelci.org>
> Date: Fri, 22 Nov 2019 04:16:01 -0800 (PST)
>
>> mdio_bus: Fix PTR_ERR applied after initialization to constant
>>
>> Fix coccinelle warning:
>>
>> ./drivers/net/phy/mdio_bus.c:67:5-12: ERROR: PTR_ERR applied after initialization to constant on line 62
>> ./drivers/net/phy/mdio_bus.c:68:5-12: ERROR: PTR_ERR applied after initialization to constant on line 62
>
> The kernelci.org bot has posted at least a half dozen of these bisection
> results for the same exact bug, which we've fixed two days ago....
>
> This is becomming more like spam and not very useful....
As far as I can tell, it's the first time someone replies to say
this issue is already fixed. Sorry if I've missed an email.
Also, it's apparently not fixed in the net-next tree which
explains why it was reported again. I guess we need to disable
bisections in net-next until it gets rebased and includes the
fix, and add a way to mark issues fixed somewhere else in
KernelCI to avoid this situation in the future.
Thanks,
Guillaume
next prev parent reply other threads:[~2019-11-22 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5dd7d181.1c69fb81.64fbc.cd8a@mx.google.com>
2019-11-22 17:36 ` David Miller
2019-11-22 18:02 ` Guillaume Tucker [this message]
2019-11-22 18:11 ` David Miller
2019-11-22 19:27 ` Mark Brown
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=bfe5e987-e0b5-6c89-f193-6666be203532@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=enric.balletbo@collabora.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=hulkci@huawei.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgalka@collabora.com \
--cc=netdev@vger.kernel.org \
--cc=tomeu.vizoso@collabora.com \
--cc=yuehaibing@huawei.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
all inboxes | Powered by JetHome®