From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Mike Turquette <mturquette@linaro.org>,
Tomasz Figa <tomasz.figa@gmail.com>
Subject: Re: [PATCH] clk: Correct handling of NULL clk in __clk_{get, put}
Date: Fri, 10 Jan 2014 11:04:57 +0100 [thread overview]
Message-ID: <52CFC5C9.4000006@samsung.com> (raw)
In-Reply-To: <CAK9yfHx+=X+DiLe_WsiDkYonKCssPTOGqR76=+7N6eyAHXyQGQ@mail.gmail.com>
On 08/01/14 05:44, Sachin Kamat wrote:
> Hi Sylwester,
>
> On 7 January 2014 17:33, Sylwester Nawrocki <s.nawrocki@samsung.com> wrote:
>> Ensure clk->kref is dereferenced only when clk is not NULL.
>>
>> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> ---
>> Hi Sachin,
>>
>> please try if this patch fixes the exyno5420 boot crash.
>
> Confirmed that this patch works fine on 5420 as well as already
> working 4210 and 5250 boards.
> Thanks for the quick fix.
>
> Tested-by: Sachin Kamat <sachin.kamat@linaro.org>
Thanks Sachin. Mike, it seems we need this patch on top of
my clk-unregister branch. Sorry for overlooking this issue.
Could you add the $subject patch to your clk-next tree ?
Regards,
Sylwester
next prev parent reply other threads:[~2014-01-10 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 12:03 [PATCH] clk: Correct handling of NULL clk in __clk_{get, put} Sylwester Nawrocki
2014-01-07 13:00 ` Lothar Waßmann
2014-01-07 13:14 ` Sylwester Nawrocki
2014-01-08 4:44 ` Sachin Kamat
2014-01-10 10:04 ` Sylwester Nawrocki [this message]
2014-01-30 4:50 ` Sachin Kamat
2014-02-10 15:02 ` Sylwester Nawrocki
2014-02-24 12:59 ` Tomasz Figa
2014-02-25 6:16 ` Mike Turquette
2014-02-25 17:34 ` Tomasz Figa
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=52CFC5C9.4000006@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sachin.kamat@linaro.org \
--cc=tomasz.figa@gmail.com \
/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