From: Mark Brown <broonie@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Guenter Roeck <linux@roeck-us.net>,
Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Stephen Hemminger <stephen@networkplumber.org>,
linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: arm64 allmodconfig failures in nft_reject_bridge.c
Date: Thu, 13 Nov 2014 12:51:28 +0000 [thread overview]
Message-ID: <20141113125128.GH3815@sirena.org.uk> (raw)
In-Reply-To: <20141113114357.GA7857@salvia>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
On Thu, Nov 13, 2014 at 12:43:57PM +0100, Pablo Neira Ayuso wrote:
> I can see this in David's tree:
> http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=c1207c049b204b0a96535dc5416aee331b51e0e1
> I think this was reported by when -rc4 was already out, so you'll see
> this by -rc5.
The fix predates -rc4 (sent on the 2nd, committed on the 3rd, -rc4 was
on the 9th), I'd been expecting to see it turn up there or shortly
after.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-13 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Xm8gR-0005nT-PY@debutante>
[not found] ` <20141106104616.GU8509@sirena.org.uk>
[not found] ` <20141112233738.GB3815@sirena.org.uk>
2014-11-13 11:33 ` arm64 allmodconfig failures in nft_reject_bridge.c Mark Brown
2014-11-13 11:43 ` Pablo Neira Ayuso
2014-11-13 12:51 ` Mark Brown [this message]
2014-11-13 19:35 ` David Miller
2014-11-13 19:47 ` Mark Brown
2014-11-13 20:23 ` David Miller
2014-11-13 23:51 ` 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=20141113125128.GH3815@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).