linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: manual merge of the mvebu tree
Date: Wed, 23 Oct 2013 04:59:48 -0400	[thread overview]
Message-ID: <20131023085948.GC24520@titan.lakedaemon.net> (raw)
In-Reply-To: <1382454649-16442-5-git-send-email-treding@nvidia.com>

On Tue, Oct 22, 2013 at 05:10:49PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the mvebu tree got conflicts in
> 
> 	arch/arm/mach-kirkwood/board-dt.c
> 
> caused by commits a169e3a (ARM: kirkwood: remove custom .init_time hook)
> and 14867b4 (ARM: kirkwood: remove lagacy clk workarounds).
> 
> I fixed them up (see below). Please verify that the resolution looks good.

Looks good,

thx,

Jason.

  reply	other threads:[~2013-10-23  8:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 15:36 linux-next: Tree for Oct 21 Thierry Reding
2013-10-21 23:20 ` linux-next: Tree for Oct 21 (panel-simple.c) Randy Dunlap
2013-10-22  8:10   ` Thierry Reding
2013-10-22  0:58 ` linux-next: Tree for Oct 21 (sound/pci/hda/patch_hdmi.c) Randy Dunlap
2013-10-22  7:42   ` Takashi Iwai
2013-10-22 15:10 ` linux-next: manual merge of the net-next tree Thierry Reding
2013-10-22 15:10   ` linux-next: manual merge of the wireless-next tree Thierry Reding
2013-10-22 15:10   ` linux-next: manual merge of the drm tree Thierry Reding
2013-10-22 15:10   ` linux-next: manual merge of the arm-soc tree Thierry Reding
2013-10-23 12:19     ` Tony Lindgren
2013-10-22 15:10   ` linux-next: manual merge of the mvebu tree Thierry Reding
2013-10-23  8:59     ` Jason Cooper [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-09 14:14 linux-next: Tree for Oct 9 Thierry Reding
2013-10-09 14:14 ` linux-next: manual merge of the mvebu tree Thierry Reding
2013-10-09 14:21   ` Jason Cooper
2013-10-09 14:37   ` Jason Cooper
2013-10-10 10:57     ` Thierry Reding
2013-10-10 11:40       ` Jason Cooper

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=20131023085948.GC24520@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-next@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).