From: Rich Felker <dalias@libc.org>
To: Jaydeep Patil <Jaydeep.Patil@imgtec.com>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [MUSL] MIPS64 N32 port
Date: Tue, 5 Apr 2016 01:02:33 -0400 [thread overview]
Message-ID: <20160405050233.GK21636@brightrain.aerifal.cx> (raw)
In-Reply-To: <BD7773622145634B952E5B54ACA8E349AA24CE69@PUMAIL01.pu.imgtec.org>
On Tue, Apr 05, 2016 at 04:44:41AM +0000, Jaydeep Patil wrote:
> Hi Rich,
>
> Could you please find some time to review this?
I'm at ELC now and haven't yet had a good chance to look over it in
detail, but I just looked at it as a diff against the mips64 tree and
it looks mostly okay. There are a few things that changed from nsz's
bits cleanups, and the mips r6 patch I committed, that should also be
applied to n32. I can make those changes myself if you like but I
probably won't get to it until Friday or later (my flight gets back
Thursday night); if you'd rather submit an updated patch that's fine
too.
Rich
> >-----Original Message-----
> >From: Jaydeep Patil
> >Sent: 18 March 2016 AM 09:42
> >To: Rich Felker
> >Cc: musl@lists.openwall.com
> >Subject: RE: [musl] [MUSL] MIPS64 N32 port
> >
> >Thanks Rich.
> >
> >>-----Original Message-----
> >>From: Rich Felker [mailto:dalias@aerifal.cx] On Behalf Of Rich Felker
> >>Sent: 18 March 2016 AM 12:56
> >>To: Jaydeep Patil
> >>Cc: musl@lists.openwall.com
> >>Subject: Re: [musl] [MUSL] MIPS64 N32 port
> >>
> >>On Wed, Mar 16, 2016 at 11:56:32AM +0000, Jaydeep Patil wrote:
> >>> Hi Rich,
> >>>
> >>> Please refer to
> >>> https://github.com/JaydeepIMG/musl-1/tree/mipsn32port for MIPS64
> >N32
> >>> port. I have also attached the patch (ipsn32port.patch) for your
> >>> reference. Could you please review it?
> >>
> >>Thanks! I haven't gotten a chance to review it yet but I want you to
> >>know that I've seen it and will try to get to it in the next few days.
> >>
> >>If anyone else wants to take a look/try it and comment on it in the
> >>mean time, please go ahead; that will be helpful when I get to looking at it
> >myself too.
> >>
> >>Rich
next prev parent reply other threads:[~2016-04-05 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 11:56 Jaydeep Patil
2016-03-17 19:25 ` Rich Felker
2016-03-18 4:11 ` Jaydeep Patil
2016-04-05 4:44 ` Jaydeep Patil
2016-04-05 5:02 ` Rich Felker [this message]
2016-04-05 5:57 ` Jaydeep Patil
2016-04-10 0:48 ` Rich Felker
2016-04-11 3:40 ` Jaydeep Patil
2016-04-18 5:28 ` Rich Felker
2016-04-18 9:16 ` Jaydeep Patil
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=20160405050233.GK21636@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=Jaydeep.Patil@imgtec.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).