From: David Miller <davem@davemloft.net>
To: xypron.glpk@gmx.de
Cc: ivecera@redhat.com, andrew@lunn.ch, f.fainelli@gmail.com,
simon@fire.lp0.eu, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
treding@nvidia.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] net: bcm63xx: avoid possible null pointer dereference
Date: Mon, 01 Aug 2016 13:44:09 -0700 (PDT) [thread overview]
Message-ID: <20160801.134409.1016429746416712661.davem@davemloft.net> (raw)
In-Reply-To: <1469953469-20782-1-git-send-email-xypron.glpk@gmx.de>
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
Date: Sun, 31 Jul 2016 10:24:29 +0200
> If dev_get_platdata has failed pd is null.
> Do not dereference a null pointer.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Applied.
prev parent reply other threads:[~2016-08-01 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 8:24 [PATCH 1/1] net: bcm63xx: avoid possible null pointer dereference Heinrich Schuchardt
2016-08-01 20:44 ` 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=20160801.134409.1016429746416712661.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=ivecera@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon@fire.lp0.eu \
--cc=treding@nvidia.com \
--cc=xypron.glpk@gmx.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).