From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paul Brook <paul@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, appplied] ARM Cortex-M4 CPU
Date: Fri, 11 Jun 2010 16:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1006111550380.13721@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201006111648.55504.paul@codesourcery.com>
On Fri, 11 Jun 2010, Paul Brook wrote:
> > > The attached patch adds nominal support for the ARM Cortex-M4 CPU core.
> > > All the interesting bits are already there, this just adds the cpu name.
> > >
> > > Tested on arm-none-eabi.
> > > Applied to SVN trunk.
> >
> > I don't see any sign of this actually having been committed.
>
> Bah! It has now.
Remember the patch tracker update now.... (I noticed the lack of a commit
when doing some patch tracker updates earlier.)
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2010-06-11 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 15:09 [PATCH, appplied] ARM Cortex-M3 CPU Paul Brook
2010-06-11 13:22 ` Joseph S. Myers
2010-06-11 16:00 ` [PATCH, appplied] ARM Cortex-M4 CPU Paul Brook
2010-06-11 16:05 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1006111550380.13721@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul@codesourcery.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).