From: David Miller <davem@davemloft.net>
To: dan.carpenter@oracle.com
Cc: linux-net-drivers@solarflare.com, bhutchings@solarflare.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch v2] sfc: check for allocation failure
Date: Wed, 04 Sep 2013 13:08:13 -0400 (EDT) [thread overview]
Message-ID: <20130904.130813.810425005355634326.davem@davemloft.net> (raw)
In-Reply-To: <20130904150727.GA32327@elgon.mountain>
From: Dan Carpenter <dan.carpenter@oracle.com>
Date: Wed, 4 Sep 2013 18:07:27 +0300
> It upsets static analyzers when we don't check for allocation failure.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> v2: rebased on latest linux-next
Applied, thanks Dan.
prev parent reply other threads:[~2013-09-04 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 9:04 [patch] sfc: check for allocation failure Dan Carpenter
2013-09-02 17:00 ` Ben Hutchings
2013-09-04 2:49 ` David Miller
2013-09-04 14:41 ` Ben Hutchings
2013-09-04 15:07 ` [patch v2] " Dan Carpenter
2013-09-04 15:51 ` Ben Hutchings
2013-09-04 17:08 ` David Miller [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=20130904.130813.810425005355634326.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-net-drivers@solarflare.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 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).