mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: guillaume.tucker@collabora.com
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 10:11:47 -0800 (PST)	[thread overview]
Message-ID: <20191122.101147.1112820693050959325.davem@davemloft.net> (raw)
In-Reply-To: <bfe5e987-e0b5-6c89-f193-6666be203532@collabora.com>

From: Guillaume Tucker <guillaume.tucker@collabora.com>
Date: Fri, 22 Nov 2019 18:02:06 +0000

> 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.

I saw the first one and just ignored it hoping that since I had
the fix in 'net' these emails would simply stop.

> 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.

If you're not combining the net and the net-next tree, as Stephen
Rothwell's tree is doing, then you're going to run into this problem
every single day and spam us with these messages.

What is being done right now doesn't work.  You can't just wait for
net integration into net-next, that doesn't cut it.

  reply	other threads:[~2019-11-22 18:11 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
2019-11-22 18:11     ` David Miller [this message]
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=20191122.101147.1112820693050959325.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=enric.balletbo@collabora.com \
    --cc=f.fainelli@gmail.com \
    --cc=guillaume.tucker@collabora.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®