From: Mike Turquette <mturquette@linaro.org>
To: Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, tony@atomide.com, nm@ti.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: OMAP: clk-next-omap emergency fixes
Date: Fri, 17 Jan 2014 13:37:29 -0800 [thread overview]
Message-ID: <20140117213729.4167.55693@quantum> (raw)
In-Reply-To: <1389990340-23358-1-git-send-email-t-kristo@ti.com>
Quoting Tero Kristo (2014-01-17 12:25:37)
> Hi,
>
> Quick emergency band-aid for the build breakages introduced in clk-next
> by Mike. I didn't have time to test this out (Nishanth will provide some
> logs) and I will leave the decision whether/how to use these patches or not
> to Tony + Mike.
>
> I also pushed a test branch based on top of clk-next here:
> tree: https://github.com/t-kristo/linux-pm.git
> branch: clk-next-omap-fixes
Thanks Tero. I force updated the clk tree with the right branch, so
these should not be necessary now.
Regards,
Mike
>
> -Tero
>
WARNING: multiple messages have this Message-ID (diff)
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP: clk-next-omap emergency fixes
Date: Fri, 17 Jan 2014 13:37:29 -0800 [thread overview]
Message-ID: <20140117213729.4167.55693@quantum> (raw)
In-Reply-To: <1389990340-23358-1-git-send-email-t-kristo@ti.com>
Quoting Tero Kristo (2014-01-17 12:25:37)
> Hi,
>
> Quick emergency band-aid for the build breakages introduced in clk-next
> by Mike. I didn't have time to test this out (Nishanth will provide some
> logs) and I will leave the decision whether/how to use these patches or not
> to Tony + Mike.
>
> I also pushed a test branch based on top of clk-next here:
> tree: https://github.com/t-kristo/linux-pm.git
> branch: clk-next-omap-fixes
Thanks Tero. I force updated the clk tree with the right branch, so
these should not be necessary now.
Regards,
Mike
>
> -Tero
>
next prev parent reply other threads:[~2014-01-17 21:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 20:25 [PATCH 0/3] ARM: OMAP: clk-next-omap emergency fixes Tero Kristo
2014-01-17 20:25 ` Tero Kristo
2014-01-17 20:25 ` [PATCH 1/3] ARM: DRA7XX/AM43XX: randconfig fixes Tero Kristo
2014-01-17 20:25 ` Tero Kristo
2014-01-17 20:25 ` [PATCH 2/3] ARM: DRA7XX: Add support for DRA7XX only build Tero Kristo
2014-01-17 20:25 ` Tero Kristo
2014-01-17 20:25 ` [PATCH 3/3] clk: ti: OMAP build fixes Tero Kristo
2014-01-17 20:25 ` Tero Kristo
2014-01-17 21:37 ` Mike Turquette [this message]
2014-01-17 21:37 ` [PATCH 0/3] ARM: OMAP: clk-next-omap emergency fixes Mike Turquette
2014-01-18 17:50 ` Tony Lindgren
2014-01-18 17:50 ` Tony Lindgren
2014-01-20 7:43 ` Mike Turquette
2014-01-20 7:43 ` Mike Turquette
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=20140117213729.4167.55693@quantum \
--to=mturquette@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.