From: nick clifton <nickc@redhat.com>
To: James Murray <jsm@jsm-net.demon.co.uk>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: 68hc11/12/s12x/xgate patch
Date: Tue, 15 May 2012 12:59:00 -0000 [thread overview]
Message-ID: <4FB2525C.1050309@redhat.com> (raw)
In-Reply-To: <1337003987.27195.60.camel@jsm2>
Hi James,
> just wondered if you had found time to review the patch I submitted.
> (Patch is in http://sourceware.org/ml/binutils/2012-03/msg00123.html )
Sorry it has taken me so long to review this patch, and thanks for the ping.
I have now gone over the patch. There were a few formatting issues, but
these were minor. The main thing (to me) is that it works and it does
not break any other ports. So I have checked it in.
This does mean that we now have two different ways of supporting the
XGATE processor. I feel that the best way to resolve this is to see how
these two ports fare in the long term. If one of them turns out to be
too buggy or unmaintained then it will be dropped.
Cheers
Nick
next prev parent reply other threads:[~2012-05-15 12:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 22:22 James Murray
2011-03-07 16:35 ` James Murray
2011-03-15 8:33 ` Nick Clifton
2011-03-15 15:08 ` James Murray
2011-12-20 22:20 ` James Murray
2011-12-20 22:29 ` Fred Cooke
2011-12-20 23:23 ` James Murray
2011-12-21 22:29 ` Fred Cooke
2011-12-22 16:52 ` Sean Keys
2011-12-22 17:37 ` James Murray
2012-01-05 22:03 ` James Murray
2012-01-05 23:11 ` Fred Cooke
2012-01-10 14:42 ` nick clifton
2012-01-10 15:45 ` James Murray
2012-01-12 19:39 ` 68hc11/12/s12x/xgate patch - style question James Murray
2012-01-12 20:14 ` Fred Cooke
2012-02-26 23:54 ` 68hc11/12/s12x/xgate patch James Murray
2012-03-12 15:07 ` James Murray
2012-03-12 15:26 ` Fred Cooke
2012-03-13 20:28 ` James Murray
2012-03-13 20:56 ` Fred Cooke
2012-04-02 12:37 ` James Murray
2012-04-23 17:05 ` James Murray
[not found] ` <1337003987.27195.60.camel@jsm2>
2012-05-15 12:59 ` nick clifton [this message]
2012-05-15 18:38 ` Fred Cooke
2012-05-15 20:26 ` James Murray
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=4FB2525C.1050309@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jsm@jsm-net.demon.co.uk \
/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).