[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150323135235.GA7595@salvia>
Date: Mon, 23 Mar 2015 14:52:35 +0100
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Joe Perches <joe@...ches.com>, David Miller <davem@...emloft.net>,
netdev@...r.kernel.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, Patrick McHardy <kaber@...sh.net>
Subject: Re: [PATCH -next] netfilter: Use LOGLEVEL_<FOO> defines
On Tue, Mar 24, 2015 at 12:38:28AM +1100, Stephen Rothwell wrote:
> Hi Joe,
>
> On Mon, 23 Mar 2015 06:23:51 -0700 Joe Perches <joe@...ches.com> wrote:
> >
> > Use the #defines where appropriate.
> >
> > Signed-off-by: Joe Perches <joe@...ches.com>
> > ---
> > > > Perhaps all the .level = 4 uses should be LOGLEVEL_WARNING
> > > > and .level = 5 should be LOGLEVEL_NOTICE
> > >
> > > Yes, we can push a follow up patch to net-next changing all these
> > > spots in the netfilter tree. Would you send a patch for this?
> >
> > There are indirect includes of kern_levels.h but there are a
> > lot of indirect includes of kernel.h in netfilter
>
> I am not sure what you are getting at here. kernel.h does not include
> kern_levels.h (but printk.h does). I, for one, am always happier when
> necessary include files are explicitly included.
I would also prefer if you include the explicit header files in that
patch too. Could you send us a v2? Please, Cc:
netfilter-devel@...r.kernel.org
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists