From: Yury Norov <ynorov@caviumnetworks.com>
To: Iosif Harutyunov <iharutyunov@SonicWALL.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 01/17] arm64:ilp32: add documentation on the ILP32 ABI for ARM64
Date: Wed, 20 Apr 2016 06:27:16 +0300 [thread overview]
Message-ID: <20160420032716.GA5380@yury-N73SV> (raw)
In-Reply-To: <1AA17CE09ACFBD499BB5F503A7513F5B43A263EA@us0exc08.us.sonicwall.com>
On Wed, Nov 25, 2015 at 03:07:26AM +0000, Iosif Harutyunov wrote:
> Sonicwall is very interested in ILP32, is there a way we can get access to the SuSe builds?
>
> Iosif,_
>
Hi Iosif,
I just found your email in trash mailbox. Please add my email to CC
explicitly to avoid it. If you still interested in ILP32, find
RFC6 version here: http://www.spinics.net/lists/linux-s390/msg12272.html
There are also manuals for building glibc for it. I'm not sure
someone was building whole SUSE distro against ILP32, but I think
you can build kernel with my patches, and library, and do tests you
interested. Feel free to contact me in case of troubles.
Yury.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2016-04-20 3:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 3:07 [PATCH v6 01/17] arm64:ilp32: add documentation on the ILP32 ABI for ARM64 Iosif Harutyunov
2016-04-20 3:27 ` Yury Norov [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-02 23:30 [RFC PATCH v6 00/17] ILP32 " Yury Norov
2015-11-02 23:30 ` [PATCH v6 01/17] arm64:ilp32: add documentation on the ILP32 ABI " Yury Norov
2015-11-05 14:33 ` Arnd Bergmann
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=20160420032716.GA5380@yury-N73SV \
--to=ynorov@caviumnetworks.com \
--cc=iharutyunov@SonicWALL.com \
--cc=linux-kernel@vger.kernel.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