From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: Kernels 4.+ are breaking rsync?
Date: Fri, 04 Mar 2016 20:47:13 +0000 [thread overview]
Message-ID: <56D9F451.8080603@physik.fu-berlin.de> (raw)
In-Reply-To: <56C11585.3060503@triadic.us>
On 03/05/2016 05:24 AM, alexmcwhirter@triadic.us wrote:
> I do find it odd that the Debian port seems to be working fine. I'm
> going to give the latest kernel on a try on this box. Previously i had
> only tried up to the latest rendition of 4.1. If it's still broken I
> will boot up Debian and see what's going on. Hopefully it isn't hardware
> specific "This is a cheetah box IIRC"
It might be a toolchain issue.
Are you using the default compiler options or did you tune anything?
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-03-04 20:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 0:02 Kernels 4.+ are breaking rsync? Alex McWhirter
2016-02-21 18:52 ` Alex McWhirter
2016-02-21 20:13 ` Sam Ravnborg
2016-02-21 20:14 ` Sam Ravnborg
2016-02-28 17:41 ` Sam Ravnborg
2016-02-28 17:57 ` Al Viro
2016-03-03 6:29 ` Alex McWhirter
2016-03-03 6:31 ` Alex McWhirter
2016-03-03 6:50 ` John Paul Adrian Glaubitz
2016-03-03 6:50 ` Alex McWhirter
2016-03-03 6:57 ` John Paul Adrian Glaubitz
2016-03-03 7:03 ` Alex McWhirter
2016-03-03 7:43 ` John Paul Adrian Glaubitz
2016-03-04 20:47 ` John Paul Adrian Glaubitz [this message]
2016-03-04 21:41 ` John Paul Adrian Glaubitz
2016-03-08 3:28 ` Alex McWhirter
-- strict thread matches above, loose matches on Subject: below --
2016-03-04 20:24 alexmcwhirter
2016-03-04 21:21 ` alexmcwhirter
2016-03-09 22:10 ` alexmcwhirter
2016-03-16 17:10 ` alexmcwhirter
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=56D9F451.8080603@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.