From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP: clk-next-omap emergency fixes
Date: Sat, 18 Jan 2014 09:50:21 -0800 [thread overview]
Message-ID: <20140118175020.GF7235@atomide.com> (raw)
In-Reply-To: <20140117213729.4167.55693@quantum>
* Mike Turquette <mturquette@linaro.org> [140117 13:39]:
> 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.
Great, and just for reference if I did not do it yet for these:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2014-01-18 17:50 UTC|newest]
Thread overview: 7+ 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 ` [PATCH 1/3] ARM: DRA7XX/AM43XX: randconfig fixes 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 ` [PATCH 3/3] clk: ti: OMAP build fixes Tero Kristo
2014-01-17 21:37 ` [PATCH 0/3] ARM: OMAP: clk-next-omap emergency fixes Mike Turquette
2014-01-18 17:50 ` Tony Lindgren [this message]
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=20140118175020.GF7235@atomide.com \
--to=tony@atomide.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).