public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Ungerer <gerg@uclinux.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [000/121] 3.2.51-rc1 review
Date: Sun, 20 Oct 2013 09:23:21 -0700	[thread overview]
Message-ID: <52640379.8070609@roeck-us.net> (raw)
In-Reply-To: <1382270174.2794.96.camel@deadeye.wl.decadent.org.uk>

On 10/20/2013 04:56 AM, Ben Hutchings wrote:
> On Sun, 2013-09-08 at 09:52 -0700, Guenter Roeck wrote:
>> On 09/08/2013 01:18 AM, Geert Uytterhoeven wrote:
>>> On Sun, Sep 8, 2013 at 9:10 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>>>> m68k-linux-ld: error: no memory region specified for loadable section
>>>> `.note.gnu.build-id'
>>>
>>> I can't seem to find an explicit fix for that since v3.2.
>>> Perhaps the fix is a side effect of f84f52a5c15db7d14a534815f27253b001735183
>>> ("m68knommu: clean up linker script").
>>>
>>
>> Kind of. Turns out it requires the following patches.
>>
>> 40c1b9cf (m68k: consolidate the vmlinux.lds linker scripts)
>> ed865e31 (m68k: use non-MMU linker script for ColdFire MMU builds)
>> f84f52a5 (m68knommu: clean up linker script)
>>
>> With those patches applied, all my m68k builds (mmu and nommu) pass with 3.2.
>
> I've queued these up for 3.2.  The first looks quite a big change in
> terms of lines, but most of that is just renaming a file so I think it's
> within the spirit of the stable rules.  The third is also pretty big as
> m68knommu seems so broken in 3.2 that I suppose it is OK.
>
> Ben.
>
Hi Ben,

is that in your patch list yet ? Just wondering, because the latest nommu build still failed.

Thanks,
Guenter

  reply	other threads:[~2013-10-20 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lsq.1378608720.401499712@decadent.org.uk>
     [not found] ` <522C22DB.9080008@roeck-us.net>
2013-09-08  8:18   ` [000/121] 3.2.51-rc1 review Geert Uytterhoeven
2013-09-08 16:52     ` Guenter Roeck
2013-10-20 11:56       ` Ben Hutchings
2013-10-20 16:23         ` Guenter Roeck [this message]
2013-10-20 18:05           ` Ben Hutchings
2013-10-20 19:28             ` Guenter Roeck
2013-09-09 13:16     ` Greg Ungerer
2013-09-09 13:26       ` Guenter Roeck

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=52640379.8070609@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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