From: santosh.shilimkar@ti•com (Santosh Shilimkar)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] clk: keystone: Couple of fixes for 3.14-rcx
Date: Wed, 19 Feb 2014 09:26:58 -0500 [thread overview]
Message-ID: <5304BF32.6060403@ti.com> (raw)
In-Reply-To: <20140219061959.22529.87876@quantum>
On Wednesday 19 February 2014 01:19 AM, Mike Turquette wrote:
> Quoting Santosh Shilimkar (2014-02-10 12:26:49)
>> Mike,
>>
>> Can you please look at these couple of keystone clock fixes ?
>> Without these, we have seen some random kernel crashes. I
>> have included the dts fix since both fixes are related. Do
>> let me know if you prefer dts patch to be sent it via arm-soc tree.
>
> No problem taking these in as fixes. They go in the next batch.
>
Thanks Mike !!
Regards,
Santosh
prev parent reply other threads:[~2014-02-19 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 20:26 [PATCH 0/2] clk: keystone: Couple of fixes for 3.14-rcx Santosh Shilimkar
2014-02-10 20:26 ` [PATCH 1/2] clk: keystone: gate: fix clk_init_data initialization Santosh Shilimkar
2014-02-10 20:26 ` [PATCH 2/2] ARM: keystone: dts: fix clkvcp3 control register address Santosh Shilimkar
2014-02-17 14:38 ` [PATCH 0/2] clk: keystone: Couple of fixes for 3.14-rcx Santosh Shilimkar
2014-02-19 6:19 ` Mike Turquette
2014-02-19 14:26 ` Santosh Shilimkar [this message]
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=5304BF32.6060403@ti.com \
--to=santosh.shilimkar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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