From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: netdev@vger.kernel.org, Simon Horman <horms@verge.net.au>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] net: sh_eth: avoid NULL pointer dereference in ring setup
Date: Wed, 2 Mar 2016 20:47:34 +0300 [thread overview]
Message-ID: <56D72736.1090502@cogentembedded.com> (raw)
In-Reply-To: <20160302171114.GB5439@katana>
On 03/02/2016 08:11 PM, Wolfram Sang wrote:
>>> Reported-by: coverity (CID 1056464)
>>> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>
>> Will you respin or should I?
>
> Please go ahead. You have more knowledge about this driver, so you will
> be faster.
Not necessarily -- I have other bug to chase right now. :-)
> Reported-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Thanks for reporting, anyway.
MBR, Sergei
prev parent reply other threads:[~2016-03-02 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 15:26 [PATCH] net: sh_eth: avoid NULL pointer dereference in ring setup Wolfram Sang
2016-03-02 16:47 ` Sergei Shtylyov
2016-03-02 17:11 ` Wolfram Sang
2016-03-02 17:47 ` Sergei Shtylyov [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=56D72736.1090502@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).