From: Mark Brown <broonie@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: guillaume.tucker@collabora.com, hulkci@huawei.com,
tomeu.vizoso@collabora.com, 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 19:27:18 +0000 [thread overview]
Message-ID: <20191122192718.GH6849@sirena.org.uk> (raw)
In-Reply-To: <20191122.101147.1112820693050959325.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
On Fri, Nov 22, 2019 at 10:11:47AM -0800, David Miller wrote:
> 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.
Is there a writeup somewhere of how your trees are expected to work?
That might help testing people figure things out, what you're doing is a
bit unusual and people working on testing infrastructure are likely not
going to be as engaged with the process for specific trees as developers
are. I didn't spot anything in Docmentation/ and the wiki link in
MAINTAINERS seems broken but I might've been looking in the wrong places.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-11-22 19:27 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
2019-11-22 19:27 ` Mark Brown [this message]
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=20191122192718.GH6849@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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®