From: Randy Dunlap <rdunlap@xenotime.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 9 (netfilter)
Date: Sat, 10 Mar 2012 08:45:22 -0800 [thread overview]
Message-ID: <4F5B8522.8050707@xenotime.net> (raw)
In-Reply-To: <20120310112154.GA22478@1984>
On 03/10/2012 03:21 AM, Pablo Neira Ayuso wrote:
> On Fri, Mar 09, 2012 at 12:30:42PM -0800, Randy Dunlap wrote:
>> On 03/09/2012 12:11 AM, Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> There will be no linux-next release on March 12 due to a public holiday.
>>>
>>> Changes since 20120308:
>>
>>
>> xt_LOG.c:(.text+0x789b1): undefined reference to `ip6t_ext_hdr'
>>
>> Full randconfig file is attached.
>
> The patch attached fixes this problem, thanks!
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
--
~Randy
next prev parent reply other threads:[~2012-03-10 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 8:11 linux-next: Tree for Mar 9 Stephen Rothwell
2012-03-09 19:31 ` [PATCH -next] regmap: add structs to fix build warnings when REGMAP is not enabled Randy Dunlap
2012-03-11 11:57 ` Mark Brown
2012-03-09 20:30 ` linux-next: Tree for Mar 9 (netfilter) Randy Dunlap
2012-03-10 11:21 ` Pablo Neira Ayuso
2012-03-10 16:45 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-11 12:37 Re[2]: " Hans Schillstrom
2012-03-11 15:52 ` Pablo Neira Ayuso
[not found] <giupeu1.0f6dad72b5ddb117e753f5f660263a5d@obelix.schillstrom.com>
[not found] ` <20120311165630.GA27265@1984>
2012-03-11 16:58 ` Pablo Neira Ayuso
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=4F5B8522.8050707@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.