From: Randy Dunlap <rdunlap@xenotime.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: David Miller <davem@davemloft.net>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 28 (nfnetlink)
Date: Thu, 29 Dec 2011 10:53:00 -0800 [thread overview]
Message-ID: <4EFCB70C.50409@xenotime.net> (raw)
In-Reply-To: <20111229010330.GA2663@1984>
On 12/28/2011 05:03 PM, Pablo Neira Ayuso wrote:
> On Wed, Dec 28, 2011 at 03:33:04PM -0500, David Miller wrote:
>> From: Randy Dunlap <rdunlap@xenotime.net>
>> Date: Wed, 28 Dec 2011 13:19:08 -0800
>>
>>> On 12/28/2011 01:18 AM, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> I got bored :-( I also hate tree wide, flag day changes :-(
>>>>
>>>> Changes since 20111222:
>>>
>>>
>>>
>>> warning: (NETFILTER_XT_MATCH_NFACCT) selects NETFILTER_NETLINK_ACCT which has unmet direct dependencies (NET && INET && NETFILTER && NETFILTER_ADVANCED)
>>>
>>> and then
>>>
>>> ERROR: "nfnetlink_subsys_unregister" [net/netfilter/nfnetlink_acct.ko] undefined!
>>> ERROR: "nfnetlink_subsys_register" [net/netfilter/nfnetlink_acct.ko] undefined!
>>>
>>>
>>> Full randconfig file is attached.
>>
>> Pablo please fix this, thanks.
>
> Please, apply the following patch.
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-12-29 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111228201806.d6de27fa2dbd9e3a3b7a2603@canb.auug.org.au>
2011-12-28 21:19 ` linux-next: Tree for Dec 28 (nfnetlink) Randy Dunlap
2011-12-28 20:33 ` David Miller
2011-12-29 1:03 ` Pablo Neira Ayuso
2011-12-29 18:53 ` Randy Dunlap [this message]
2011-12-29 19:39 ` David Miller
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=4EFCB70C.50409@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=davem@davemloft.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 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).