linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Laura Abbott <labbott@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: ARM allnoconfig and arm_lowmem_init
Date: Thu, 4 Jun 2015 09:45:27 -0400	[thread overview]
Message-ID: <55705677.6060808@windriver.com> (raw)

Hi Laura,

The following linux-next build fails:

http://kisskb.ellerman.id.au/kisskb/buildresult/12436251/

I assumed it was fallout from my init changes, but a bisect led to:

make[1]: Leaving directory '/home/paul/git/no'
618ba914137d7452a103d6131034c11366961594 is the first bad commit
commit 618ba914137d7452a103d6131034c11366961594
Author: labbott <labbott@redhat.com>
Date:   Thu May 14 19:31:58 2015 +0100

    ARM: 8358/1: Don't use memblock limit for the lowmem bound

Just a heads-up; I have not investigated any further than that.

Thanks,
Paul.

             reply	other threads:[~2015-06-04 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 13:45 Paul Gortmaker [this message]
2015-06-04 14:15 ` ARM allnoconfig and arm_lowmem_init Russell King - ARM Linux
2015-06-04 17:35   ` Laura Abbott

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=55705677.6060808@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=labbott@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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).