From: "John W. Linville" <linville@tuxdriver.com>
To: Joe Perches <joe@perches.com>
Cc: netdev <netdev@vger.kernel.org>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
e1000-devel@lists.sourceforge.net, linux-usb@vger.kernel.org,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
wil6210@qca.qualcomm.com, brcm80211-dev-list@broadcom.com,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH] drivers: net: Remove remaining alloc/OOM messages
Date: Fri, 8 Feb 2013 11:19:19 -0500 [thread overview]
Message-ID: <20130208161918.GD2116@tuxdriver.com> (raw)
In-Reply-To: <1360273587.27863.15.camel@joe-AO722>
On Thu, Feb 07, 2013 at 01:46:27PM -0800, Joe Perches wrote:
> alloc failures already get standardized OOM
> messages and a dump_stack.
>
> For the affected mallocs around these OOM messages:
>
> Converted kmallocs with multiplies to kmalloc_array.
> Converted a kmalloc/memcpy to kmemdup.
> Removed now unused stack variables.
> Removed unnecessary parentheses.
> Neatened alignment.
>
> Signed-off-by: Joe Perches <joe@perches.com>
No objection...
Acked-by: John W. Linville <linville@tuxdriver.com>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-02-08 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 21:46 [PATCH] drivers: net: Remove remaining alloc/OOM messages Joe Perches
2013-02-07 22:07 ` Arend van Spriel
2013-02-07 23:29 ` Marc Kleine-Budde
2013-02-08 16:19 ` John W. Linville [this message]
2013-02-08 22:45 ` David Miller
2013-02-09 0:29 ` Other alloc/OOM message question Joe Perches
2013-02-09 0:46 ` Greg KH
[not found] ` <20130209004644.GC31290-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-02-09 21:45 ` [RFC PATCH] dma_alloc_consistent: Remove OOM messages after failure Joe Perches
2013-02-10 7:57 ` [PATCH] drivers: net: Remove remaining alloc/OOM messages Vladimir Kondratiev
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=20130208161918.GD2116@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=brcm80211-dev-list@broadcom.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=joe@perches.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wil6210@qca.qualcomm.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).