From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: SILO Issues on an E4900
Date: Thu, 24 Nov 2016 16:22:48 +0000 [thread overview]
Message-ID: <41d5e58d-c73b-9995-b97f-02b14e20b91b@physik.fu-berlin.de> (raw)
In-Reply-To: <62477e32a682342782e652fcfdbf9fb5@triadic.us>
On 11/24/2016 05:10 PM, David Miller wrote:
> From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> Date: Thu, 24 Nov 2016 11:00:29 +0100
>
>> For SILO, Oracle has created several patches which port SILO to 64-bit (I extracted
>> that patch and applied it to the Debian package) and other packages which improve
>> SILO on modern sun4v machines.
>
> All of the changes which were submitted to this list I reviewed and
> either they were poorly formed or did not apply cleanly at all.
That doesn't sound too good :(.
> Everything fell to /dev/null and the developers made no effort
> whatsoever to address the feedback and make the patches actually apply
> to the SILO git tree properly.
>
> The patches were not only poorly formed, or not able to apply to the
> GIT tree, they were also extremely poorly documented with either a
> very terse and vague commit message provided or none at all. When
> I would ask why a change was doing X or Y, I received no response
> at all.
Hmm. I have this small patch which enables 64-bit support. It's rather
clean and I'll try to submit it later today to get at least some
improvements.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2016-11-24 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 0:02 SILO Issues on an E4900 alexmcwhirter
2016-11-24 9:35 ` Louis Liu
2016-11-24 10:00 ` John Paul Adrian Glaubitz
2016-11-24 16:10 ` David Miller
2016-11-24 16:22 ` John Paul Adrian Glaubitz [this message]
2016-11-24 21:26 ` vincent
2016-11-24 22:04 ` Mark Cave-Ayland
2016-11-25 8:14 ` Louis Liu
2016-11-25 20:30 ` Louis Liu
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=41d5e58d-c73b-9995-b97f-02b14e20b91b@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.