From: Simon Horman <horms@verge.net.au>
To: David Miller <davem@davemloft.net>
Cc: randy.dunlap@oracle.com, sfr@canb.auug.org.au,
netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for January 31 (ip_vs)
Date: Tue, 1 Feb 2011 11:03:07 +1100 [thread overview]
Message-ID: <20110201000302.GA9482@verge.net.au> (raw)
In-Reply-To: <20110131.150031.70194609.davem@davemloft.net>
On Mon, Jan 31, 2011 at 03:00:31PM -0800, David Miller wrote:
> From: Simon Horman <horms@verge.net.au>
> Date: Tue, 1 Feb 2011 09:57:28 +1100
>
> > On Tue, Feb 01, 2011 at 08:18:47AM +1100, Simon Horman wrote:
> >> On Mon, Jan 31, 2011 at 10:18:29AM -0800, Randy Dunlap wrote:
> >> > On Mon, 31 Jan 2011 17:41:13 +1100 Stephen Rothwell wrote:
> >> >
> >> > > Hi all,
> >> > >
> >> > > Changes since 20110121:
> >> > >
> >> > > The net tree lost its build failure.
> >> >
> >> >
> >> > When CONFIG_SYSCTL is not enabled:
> >> >
> >> > net/netfilter/ipvs/ip_vs_core.c:1891: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'unsigned int'
> >> > ERROR: "unregister_net_sysctl_table" [net/netfilter/ipvs/ip_vs.ko] undefined!
> >> > ERROR: "register_net_sysctl_table" [net/netfilter/ipvs/ip_vs.ko] undefined!
> >>
> >> Thanks, I'm looking into it.
> >
> > On a related note, does IPVS need to handle the case
> > where CONFIG_PROC_FS is not enabled?
>
> Yes.
Thanks.
I checked and it does seem to compile without CONFIG_PROC_FS
and now also without CONFIG_SYSCTL, I'll send a patch for that right
after I finish this email.
I think that in both cases there is dead code, I'll clean that up next.
prev parent reply other threads:[~2011-02-01 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 6:41 linux-next: Tree for January 31 Stephen Rothwell
2011-01-31 17:05 ` Konrad Rzeszutek Wilk
2011-01-31 18:25 ` Jeremy Fitzhardinge
2011-01-31 18:18 ` linux-next: Tree for January 31 (ip_vs) Randy Dunlap
2011-01-31 21:18 ` Simon Horman
2011-01-31 22:57 ` Simon Horman
2011-01-31 23:00 ` David Miller
2011-02-01 0:03 ` Simon Horman [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=20110201000302.GA9482@verge.net.au \
--to=horms@verge.net.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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.