From: Aaron Brown <aaron.f.brown@intel.com>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, jeffrey.t.kirsher@intel.com,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next V2] intel: Remove unnecessary OOM messages
Date: Thu, 13 Feb 2014 16:03:36 -0800 [thread overview]
Message-ID: <1392336216.1831.16.camel@localhost> (raw)
In-Reply-To: <20140213.174723.1145739288167542959.davem@davemloft.net>
On Thu, 2014-02-13 at 17:47 -0500, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Tue, 11 Feb 2014 17:30:52 -0800
>
> > Don't emit these as there's a generic OOM with a dump_stack()
> > on allocation failures.
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
> > ---
> >
> > With patch attached this time...
>
> I expect the Intel folks to pick this up.
Yes indeed, I have already pulled it into our test queue. Thanks...
next prev parent reply other threads:[~2014-02-14 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 1:26 [PATCH net-next] intel: Remove unnecessary OOM messages Joe Perches
2014-02-12 1:30 ` [PATCH net-next V2] " Joe Perches
2014-02-13 22:47 ` David Miller
2014-02-14 0:03 ` Aaron Brown [this message]
2014-02-12 23:46 ` [PATCH net-next] " Aaron Brown
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=1392336216.1831.16.camel@localhost \
--to=aaron.f.brown@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
/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.