From: Jeff Dike <jdike@addtoit.com>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: blaisorblade@yahoo.it,
user-mode-linux devel
<user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] Re: UML-patches to prepare UML/s390
Date: Thu, 21 Apr 2005 21:32:46 -0400 [thread overview]
Message-ID: <20050422013246.GA19730@ccure.user-mode-linux.org> (raw)
In-Reply-To: <4253E3D6.2000809@fujitsu-siemens.com>
On Wed, Apr 06, 2005 at 03:27:50PM +0200, Bodo Stroesser wrote:
> Here are the patches (tarball attached), that I've applied to
> UML 2.6.11 + incrementals, before adding s390-files.
> These patches are tested a bit on x86, but not on x86_64.
The COMMAND_LINE_SIZE patch was required because this was conflicting with
the userspace s390 COMMAND_LINE_SIZE? I think this is true because in the
kernel, asm-s390/setup.h doesn't get pulled in.
This stems from the fact that my tree had add_arg in os-Linux/util.c, which
seems wrong. Blaisorblade had it moved to um_arch.c, which is right, and
where it is in my tree now. So, I think UML_COMMAND_LINE_SIZE is not needed,
and I've removed it.
Jeff
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-04-22 1:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 13:27 [uml-devel] UML-patches to prepare UML/s390 Bodo Stroesser
2005-04-06 20:35 ` [uml-devel] " Jeff Dike
2005-04-06 18:57 ` Bodo Stroesser
2005-04-06 19:17 ` Blaisorblade
2005-04-06 19:26 ` Bodo Stroesser
2005-04-06 19:50 ` Blaisorblade
2005-04-07 9:54 ` Bodo Stroesser
2005-04-06 18:59 ` Bodo Stroesser
2005-04-06 19:16 ` Bastian Blank
2005-04-06 19:28 ` Blaisorblade
2005-04-06 19:33 ` Bodo Stroesser
2005-04-06 20:02 ` Bastian Blank
2005-04-06 20:10 ` Blaisorblade
2005-04-07 9:39 ` Bodo Stroesser
2005-04-07 15:57 ` Bodo Stroesser
2005-04-08 1:22 ` [uml-devel] " Blaisorblade
[not found] ` <42562EC4.7040903@fujitsu-siemens.com>
2005-04-17 17:37 ` Blaisorblade
2005-04-18 10:54 ` Bodo Stroesser
2005-04-19 16:45 ` Blaisorblade
2005-04-26 11:31 ` Bodo Stroesser
2005-04-29 20:50 ` Blaisorblade
2005-04-22 1:32 ` Jeff Dike [this message]
2005-04-24 14:44 ` [uml-devel] " Blaisorblade
2005-04-24 16:51 ` Jeff Dike
2005-04-24 18:44 ` Blaisorblade
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=20050422013246.GA19730@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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