From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: <linux-m68k@vger.kernel.org>, <uclinux-dev@uclinux.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/1] m68k: merge m68k and m68knommu arch directories
Date: Thu, 24 Mar 2011 10:01:43 +1000 [thread overview]
Message-ID: <4D8A89E7.6060204@snapgear.com> (raw)
In-Reply-To: <AANLkTi=ohXGdwfAtWmDJKCq+cJtFqJdTCmPCxFOg6dY6@mail.gmail.com>
Hi Geert,
On 24/03/11 08:14, Geert Uytterhoeven wrote:
> On Wed, Mar 23, 2011 at 23:07, Geert Uytterhoeven<geert@linux-m68k.org> wrote:
>> On Tue, Mar 22, 2011 at 05:43, á<gerg@snapgear.com> wrote:
>>> The following patch merges the m68k and m68knommu arch directories.
>>> This patch has been trimmed for review purposes - the automated file
>>> moving and mergeing carried out by the script contained in this email
>>> has been removed. Only the manually required changes after running the
>>> script are shown as the patch. (So to end up with the final required
>>> change you need to run this script then apply the patch).
>>>
>>> This change is available as the only commit on the m68knommu git tree,
>>> for-linux branch:
>>>
>>> The following changes since commit a952baa034ae7c2e4a66932005cbc7ebbccfe28d:
>>> áLinus Torvalds (1):
>>> á á á áMerge branch 'for-linus' of git://git.kernel.org/.../dtor/input
>>>
>>> are available in the git repository at:
>>>
>>> ágit://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-linus
>>>
>>> Greg Ungerer (1):
>>> á á ám68k: merge m68k and m68knommu arch directories
>>>
>>>
>>> It is also on the for-next branch in that tree, so will get some testing
>>> in the next tree for the next few days.
>>
>> defconfig is now a nommu-config, and it fails?
>
> BTW, haven't tried it myself yet. I'm busy bisecting an issue with
> initrds, which
> got introduced between 2.6.37 and 2.6.38.
>
> Init fails with "init: cannot open inittab", followed by
> "Kernel panic - not syncing: Attempted to kill init!".
>
> As I can't get ramdisks to work on ARAnyM, I need to use real hardware, which
> suffers a lot from long reboot/copy kernel/test cycles...
As one data point (though not sure how useful this is to you... :-)
I can compile for an Atari target with the merge tree and load it
and run it on ARAnyM - using a ramdisk for root fs. Seems to work
ok.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2011-03-24 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 4:43 [PATCH 0/1] m68k: merge m68k and m68knommu arch directories gerg
2011-03-22 4:43 ` [PATCH 1/1] " gerg
2011-03-23 22:07 ` [PATCH 0/1] " Geert Uytterhoeven
2011-03-23 22:14 ` Geert Uytterhoeven
2011-03-24 0:01 ` Greg Ungerer [this message]
2011-03-24 8:04 ` Geert Uytterhoeven
2011-03-24 12:05 ` Greg Ungerer
2011-03-23 23:00 ` Greg Ungerer
2011-03-24 8:06 ` Geert Uytterhoeven
2011-03-24 11:54 ` Greg Ungerer
2011-03-25 12:00 ` Greg Ungerer
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=4D8A89E7.6060204@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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