From: shuahkh@osg.samsung.com (Shuah Khan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] media: s5p-mfc fix memory leak in s5p_mfc_remove()
Date: Tue, 28 Jun 2016 09:55:29 -0600 [thread overview]
Message-ID: <57729DF1.20404@osg.samsung.com> (raw)
In-Reply-To: <57727E2C.9040102@osg.samsung.com>
On 06/28/2016 07:39 AM, Shuah Khan wrote:
> On 06/28/2016 03:57 AM, Kamil Debski wrote:
>> HI Shuah,
>>
>> Which branch do you base your patches on?
>>
>> I have trouble applying this path
>> (https://patchwork.linuxtv.org/patch/34577/) and
>> "s5p-mfc fix null pointer deference in clk_core_enable()"
>> (https://patchwork.linuxtv.org/patch/34751/)
>> onto current linuxtv/master.
>>
>> The top commit of linuxtv/master is :
>> "commit 0db5c79989de2c68d5abb7ba891bfdb3cd3b7e05
>> Author: Mauro Carvalho Chehab <mchehab@s-opensource.com>
>> Date: Thu Jun 16 08:04:40 2016 -0300
>>
>> [media] media-devnode.h: Fix documentation"
>>
>> Could you please rebase the two patches mentioned above to the
>> linuxtv/master?
>>
>> Best wishes,
>>
>
> I based them on linux_next. I will rebase both patches on linuxtv/master
> and resend.
>
Hi Kamil,
Do you need me to rebase this one:
https://patchwork.kernel.org/patch/9166119/
I will do that anyway and send three patches. I don't see the above
in linuxtv/master
thanks,
-- Shuah
next prev parent reply other threads:[~2016-06-28 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 19:45 [PATCH] media: s5p-mfc fix memory leak in s5p_mfc_remove() Shuah Khan
2016-06-28 9:57 ` Kamil Debski
2016-06-28 13:39 ` Shuah Khan
2016-06-28 15:55 ` Shuah Khan [this message]
2016-06-28 19:27 ` Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2016-06-09 1:35 Shuah Khan
2016-06-13 13:42 ` Javier Martinez Canillas
2016-06-13 15:38 ` Shuah Khan
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=57729DF1.20404@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).