On Tue, 2015-09-01 at 11:21 +0100, Colin King wrote:
> On the unlikely event that drv is null, the current code will
> perform a null pointer dereference with it when printing a dev_dbg
> message. Instead, the BUG_ON check on drv should be performed
> before we emit the dev_dbg message.
>
> Signe
Hi Colin,
On Tue, Sep 1, 2015 at 12:38 PM, Colin Ian King
wrote:
> On 01/09/15 11:35, Geert Uytterhoeven wrote:
>> On Tue, Sep 1, 2015 at 12:21 PM, Colin King wrote:
>>> On the unlikely event that drv is null, the current code will
>>> perform a null pointer dereference with it when printing a d
On 01/09/15 11:35, Geert Uytterhoeven wrote:
> Hi Colin,
>
> On Tue, Sep 1, 2015 at 12:21 PM, Colin King wrote:
>> On the unlikely event that drv is null, the current code will
>> perform a null pointer dereference with it when printing a dev_dbg
>> message. Instead, the BUG_ON check on drv shou
Hi Colin,
On Tue, Sep 1, 2015 at 12:21 PM, Colin King wrote:
> On the unlikely event that drv is null, the current code will
> perform a null pointer dereference with it when printing a dev_dbg
> message. Instead, the BUG_ON check on drv should be performed
> before we emit the dev_dbg message.
From: Colin Ian King
On the unlikely event that drv is null, the current code will
perform a null pointer dereference with it when printing a dev_dbg
message. Instead, the BUG_ON check on drv should be performed
before we emit the dev_dbg message.
Signed-off-by: Colin Ian King
---
drivers/ps3
