On 18 March 2018 at 01:38, Arvind Yadav wrote:
> Never directly free @dev after calling device_register(), even
> if it returned an error. Always use put_device() to give up the
> reference initialized.
>
> Signed-off-by: Arvind Yadav
> ---
>
On 18 March 2018 at 01:38, Arvind Yadav wrote:
> Never directly free @dev after calling device_register(), even
> if it returned an error. Always use put_device() to give up the
> reference initialized.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/hwtracing/coresight/coresight.c | 8
On 27 March 2018 at 10:28, arvindY wrote:
>
>
> On Tuesday 27 March 2018 09:37 PM, Mathieu Poirier wrote:
>>
>> On 26 March 2018 at 20:30, arvindY wrote:
>>>
>>>
>>> On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
On 27 March 2018 at 10:28, arvindY wrote:
>
>
> On Tuesday 27 March 2018 09:37 PM, Mathieu Poirier wrote:
>>
>> On 26 March 2018 at 20:30, arvindY wrote:
>>>
>>>
>>> On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
drivers/hwtracing/coresight/coresight.c
On 18 March 2018
On Tuesday 27 March 2018 09:37 PM, Mathieu Poirier wrote:
On 26 March 2018 at 20:30, arvindY wrote:
On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
drivers/hwtracing/coresight/coresight.c
On 18 March 2018 at 01:38, Arvind Yadav
On Tuesday 27 March 2018 09:37 PM, Mathieu Poirier wrote:
On 26 March 2018 at 20:30, arvindY wrote:
On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
drivers/hwtracing/coresight/coresight.c
On 18 March 2018 at 01:38, Arvind Yadav wrote:
Never directly free @dev after calling
On 26 March 2018 at 20:30, arvindY wrote:
>
>
> On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
>>
>> drivers/hwtracing/coresight/coresight.c
>> On 18 March 2018 at 01:38, Arvind Yadav wrote:
>>>
>>> Never directly free @dev after
On 26 March 2018 at 20:30, arvindY wrote:
>
>
> On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
>>
>> drivers/hwtracing/coresight/coresight.c
>> On 18 March 2018 at 01:38, Arvind Yadav wrote:
>>>
>>> Never directly free @dev after calling device_register(), even
>>> if it returned an
On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
drivers/hwtracing/coresight/coresight.c
On 18 March 2018 at 01:38, Arvind Yadav wrote:
Never directly free @dev after calling device_register(), even
if it returned an error. Always use put_device() to give
On Tuesday 27 March 2018 03:16 AM, Mathieu Poirier wrote:
drivers/hwtracing/coresight/coresight.c
On 18 March 2018 at 01:38, Arvind Yadav wrote:
Never directly free @dev after calling device_register(), even
if it returned an error. Always use put_device() to give up the
reference
drivers/hwtracing/coresight/coresight.c
On 18 March 2018 at 01:38, Arvind Yadav wrote:
> Never directly free @dev after calling device_register(), even
> if it returned an error. Always use put_device() to give up the
> reference initialized.
>
> Signed-off-by: Arvind
drivers/hwtracing/coresight/coresight.c
On 18 March 2018 at 01:38, Arvind Yadav wrote:
> Never directly free @dev after calling device_register(), even
> if it returned an error. Always use put_device() to give up the
> reference initialized.
>
> Signed-off-by: Arvind Yadav
> ---
>
Never directly free @dev after calling device_register(), even
if it returned an error. Always use put_device() to give up the
reference initialized.
Signed-off-by: Arvind Yadav
---
drivers/hwtracing/coresight/coresight.c | 8
1 file changed, 4 insertions(+),
Never directly free @dev after calling device_register(), even
if it returned an error. Always use put_device() to give up the
reference initialized.
Signed-off-by: Arvind Yadav
---
drivers/hwtracing/coresight/coresight.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
14 matches
Mail list logo