linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: samsung: fix several typos to fix boot on s3c2410
Date: Mon, 30 Jun 2014 16:07:24 +0200	[thread overview]
Message-ID: <53B16F1C.4040206@samsung.com> (raw)
In-Reply-To: <1519968.Vijxn8Mc9S@vasilykh-desktop-i5>

Hi Vasily,

On 30.06.2014 16:02, Vasily Khoruzhick wrote:
> On 30 June 2014 15:49:58 Tomasz Figa wrote:
>> On 23.06.2014 22:29, Vasily Khoruzhick wrote:
>>> There's a several typos in a driver: 2410 instead of S3C2410
>>> and wrong argument to ARRAY_SIZE(). They prevent s3c2410
>>> from properly booting.
>>>
>>> Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com>
>>> ---
>>>
>>>  drivers/clk/samsung/clk-s3c2410.c | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> Applied as a fix for 3.16.
> 
> Hi Tomasz,
> 
> I also have clk fixes for s3c24xx touchscreen, framebuffer, adc, usb and nand 
> drivers (to replace clk_enable with clk_prepare_enable and clk_disable with 
> clk_disable_unprepare),
> 
> Should they be merged through different trees or it's possible to merge them 
> through a single tree?

I'd say they should all go through respective subsystem trees, unless
they directly depend on patches I already applied, which is not the case
as far as I can see.

Best regards,
Tomasz

  reply	other threads:[~2014-06-30 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 20:29 [PATCH 1/2] clk: samsung: fix several typos to fix boot on s3c2410 Vasily Khoruzhick
2014-06-23 20:29 ` [PATCH 2/2] clk: samsung: add more aliases for s3c24xx Vasily Khoruzhick
2014-06-23 21:24   ` Heiko Stübner
2014-06-30 13:50   ` Tomasz Figa
2014-06-23 21:16 ` [PATCH 1/2] clk: samsung: fix several typos to fix boot on s3c2410 Heiko Stübner
2014-06-25 11:26 ` Tomasz Figa
2014-06-30 13:49 ` Tomasz Figa
2014-06-30 14:02   ` Vasily Khoruzhick
2014-06-30 14:07     ` Tomasz Figa [this message]
2014-06-30 14:16       ` Vasily Khoruzhick

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=53B16F1C.4040206@samsung.com \
    --to=t.figa@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).