[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFo99gbSLRaV+f=53b+ph+P=TH1faDZ0PATENVDtv_v+6mA+Xw@mail.gmail.com>
Date: Fri, 16 May 2014 00:14:31 +0200
From: Rickard Strandqvist <rickard_strandqvist@...ctrumdigital.se>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Omar Ramirez Luna <omar.ramirez@...itl.com>,
Masood Mehmood <ody.guru@...il.com>,
Dan Carpenter <dan.carpenter@...cle.com>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix for possible null pointer dereference in node.c
Hi all, and Greg!
Good idea!
I will do it in all the other mail.
Best regards
Rickard Strandqvist
2014-05-16 0:08 GMT+02:00 Greg Kroah-Hartman <gregkh@...uxfoundation.org>:
> On Thu, May 15, 2014 at 11:53:53PM +0200, Rickard Strandqvist wrote:
>> There is otherwise a risk of a possible null pointer dereference.
>>
>> Was largely found by using a static code analysis program called cppcheck.
>>
>> Signed-off-by: Rickard Strandqvist <rickard_strandqvist@...ctrumdigital.se>
>> ---
>> drivers/staging/tidspbridge/rmgr/node.c | 4 ++--
>> 1 fil ändrad, 2 tillägg(+), 2 borttagningar(-)
>
> Please work a bit on your Subject lines to make it easier to figure out
> where the patches belong.
>
> For this one, it should be:
> Subject: staging: tidspridge: fix for possible null pointer dereference in node.c
> or:
> Subject: staging: tidspridge: node.c: fix for possible null pointer dereference
>
> That way people can figure out _what_ node.c file you are referring to
> and to see if they care about it or not :)
>
> thanks,
>
> greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists