From: Ian Lance Taylor <iant@google.com>
To: Martin Guy <martinwguy@gmail.com>
Cc: "gcc\@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: merging the maverick FPU patches
Date: Sun, 25 Apr 2010 18:07:00 -0000 [thread overview]
Message-ID: <mcrbpd7queo.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <h2g56d259a01004250140tea5d4fb2y570b60f466134a79@mail.gmail.com> (Martin Guy's message of "Sun\, 25 Apr 2010 09\:40\:03 +0100")
Martin Guy <martinwguy@gmail.com> writes:
> now that stage3 is over I'm thinking of updating the
> MaverickCrunch FPU fixes (currently for 4.3) and merging them but
> would appreciate some guidance.
>
> There are 26 patches in all and I can't expect anyone to understand
> them because they require a good understanding of the FPU and its
> hardware bugs (and there are a lot of them!) :) What's the best path?
> Create a branch, work there and then merge when done?
>
> I have done the copyright assignment stuff but don't have an account
> on gcc.gnu.org. They all affect files under config/arm/ apart from one
> testsuite fix and the docs.
For a backend specific patch like this, I would recommend contacting
the ARM backend maintainers directly to ask how they would prefer to
proceed. They can be found in the top level MAINTAINERS file:
arm port Nick Clifton nickc@redhat.com
arm port Richard Earnshaw richard.earnshaw@arm.com
arm port Paul Brook paul@codesourcery.com
Ian
next prev parent reply other threads:[~2010-04-25 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 9:47 Martin Guy
2010-04-25 18:07 ` Ian Lance Taylor [this message]
2010-06-01 23:39 ` Martin Guy
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=mcrbpd7queo.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=martinwguy@gmail.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).