From: Greg KH <gregkh@linuxfoundation.org>
To: Vinson Lee <vlee@twitter.com>
Cc: stable@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
mirq-linux@rere.qmqm.pl, jpirko@redhat.com, therbert@google.com,
netdev@vger.kernel.org
Subject: Re: [STABLE REQUEST] Merge to linux-3.4.y net: Downgrade CAP_SYS_MODULE deprecated message from error to warning.
Date: Thu, 14 Feb 2013 16:45:51 -0800 [thread overview]
Message-ID: <20130215004551.GA9060@kroah.com> (raw)
In-Reply-To: <CAKixpbhtD-mhAESjV3HOZRxYqvsWrjH0vTpDgKZuUismUvVa-g@mail.gmail.com>
On Thu, Feb 14, 2013 at 04:16:18PM -0800, Vinson Lee wrote:
> On Thu, Feb 14, 2013 at 3:37 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Thu, Feb 14, 2013 at 03:29:44PM -0800, Vinson Lee wrote:
> >> Hi.
> >>
> >> I would like to nominate commit
> >> 7cecb523adedcaf8acba5e14d47559d8bc3f40d7 for backport to stable
> >> branches 3.4 and earlier.
> >>
> >> commit 7cecb523adedcaf8acba5e14d47559d8bc3f40d7
> >> Author: Vinson Lee <vlee@twitter.com>
> >> Date: Wed Jun 27 14:32:07 2012 +0000
> >>
> >> net: Downgrade CAP_SYS_MODULE deprecated message from error to warning.
> >>
> >> Make logging level consistent with other deprecation messages in net
> >> subsystem.
> >>
> >> Signed-off-by: Vinson Lee <vlee@twitter.com>
> >> Cc: David Mackey <tdmackey@twitter.com>
> >> Signed-off-by: David S. Miller <davem@davemloft.net>
> >
> > I fail to see how this patch meets the rules described in
> > Documentation/stable_kernel_rules.txt. What am I missing?
> >
> > thanks,
> >
> > greg k-h
>
> I am logging different kernel log-level messages to different files
> and monitoring them here. I see this message most often in the errors
> pile. It's arguable that this is not a bug, but it is definitely
> bothering me here. Please consider for backport but I would understand
> if this request was turned down.
As it's not a "bug", and it's something trivial you can fix on your end
if it really annoys you (you should be fixing the root problem here, not
the kernel log message, right?), I'm not going to take it in the -stable
tree.
Unless the network maintainers want to override me, in which case, I'll
be glad to take it then :)
thanks,
greg k-h
prev parent reply other threads:[~2013-02-15 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 23:29 [STABLE REQUEST] Merge to linux-3.4.y net: Downgrade CAP_SYS_MODULE deprecated message from error to warning Vinson Lee
2013-02-14 23:37 ` Greg KH
2013-02-15 0:16 ` Vinson Lee
2013-02-15 0:45 ` Greg KH [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=20130215004551.GA9060@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jpirko@redhat.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=therbert@google.com \
--cc=vlee@twitter.com \
/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).