[Bridge] arm64 allmodconfig failures in nft_reject_bridge.c

Mark Brown broonie at kernel.org
Thu Nov 13 19:47:52 UTC 2014


On Thu, Nov 13, 2014 at 02:35:13PM -0500, David Miller wrote:

> I hold changes in my tree for a week or more, because I want them to
> "cook" there before they go to Linus.

Hrm.  Guess there must've been some other change in -next that pulled
the header in implicitly here :(

> So if it takes a week or two for a bug fix like this to propagate into
> Linus's tree, that's just what sometimes happens.

> In the mean time you can apply the fix locally if you absolutely have
> to have it right at this moment, that is the freedom that everyone
> has.

This can be a bit problematic for build (or widespread boot) breaks in
common configs since it takes out all the automated runtime testing that
people have running for the time the build break is in place.  In this
case it was just allmodconfig so it doesn't really get non-build testing
and makes little difference but for defconfigs it can be a more
substantial impact.  Applying fixes locally doesn't really work for this
case.

> FWIW, I plan to push my tree to Linus some time today, so this will be
> resolved in the next day or so.

Great, thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bridge/attachments/20141113/5dba4e2b/attachment.sig>


More information about the Bridge mailing list