linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Greg Ungerer <gerg@snapgear.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Ashok Kumar <ashoks@broadcom.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mips@linux-mips.org
Subject: linux-next: build failure after merge of the mips tree
Date: Mon,  7 Oct 2013 17:18:44 +0200	[thread overview]
Message-ID: <1381159127-11067-2-git-send-email-treding@nvidia.com> (raw)
In-Reply-To: <1381159127-11067-1-git-send-email-treding@nvidia.com>

Today's linux-next merge fails to build on various default configuration
builds. This seems to be caused by the following commit:

	5395d97 MIPS: Fix start of free memory when using initrd

Looking at the patchwork URLs in that commit message, Greg's original
patch seems to have been fine, but Ashok's patch uses the initrd_end
symbol outside of the section protected by an CONFIG_BLK_DEV_INITRD
#ifdef and therefore causes to fail during linking.

I've reverted the patch in today's linux-next tree.

Thierry

  reply	other threads:[~2013-10-07 15:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 15:18 linux-next: Tree for Oct 7 Thierry Reding
2013-10-07 15:18 ` Thierry Reding [this message]
2013-10-07 15:18 ` linux-next: manual merge of the drm-intel tree Thierry Reding
2013-10-07 15:18 ` linux-next: manual merge of the random tree Thierry Reding
2013-10-07 15:18 ` linux-next: manual merge of the wireless-next tree Thierry Reding
2013-10-07 15:48   ` Larry Finger
2013-10-07 15:56     ` Joe Perches
2013-10-07 16:09       ` Larry Finger
2013-10-07 16:17         ` Joe Perches
2013-10-07 17:16           ` Larry Finger
  -- strict thread matches above, loose matches on Subject: below --
2023-03-27  5:12 linux-next: build failure after merge of the mips tree Stephen Rothwell
2023-03-27  8:41 ` Thomas Bogendoerfer
2020-04-20 10:07 Stephen Rothwell
2020-04-20 11:33 ` Thomas Bogendoerfer
2013-02-17 23:43 Stephen Rothwell
2013-02-17 23:59 ` Hauke Mehrtens
2013-02-20  0:29 ` Stephen Rothwell
2011-11-10  1:22 Stephen Rothwell
2010-07-27  1:14 Stephen Rothwell

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=1381159127-11067-2-git-send-email-treding@nvidia.com \
    --to=thierry.reding@gmail.com \
    --cc=ashoks@broadcom.com \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.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).