From: Chung-Lin Tang <cltang@codesourcery.com>
To: Yi-Hsiu Hsu <ahsu@marvell.com>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, ARM] New CPU support for Marvell PJ4 cores
Date: Tue, 26 Jun 2012 05:51:00 -0000 [thread overview]
Message-ID: <4FE93674.5070409@codesourcery.com> (raw)
In-Reply-To: <689C75E0D210324F8BE88961219F681624B5C54D1C@SC-VEXCH2.marvell.com>
On 2012/6/26 09:37 AM, Yi-Hsiu Hsu wrote:
> Updated changelog.
>
> * config/arm/marvell-pj4.md: New marvell-pj4 pipeline description.
> * config/arm/arm.c (arm_issue_rate): Add marvell_pj4.
> * config/arm/arm.md (tune_marvell): Add marvell_pj4.
> * config/arm/arm-cores.def: Add core marvell-pj4.
> * config/arm/arm-tune.md: Regenerated.
> * config/arm/arm-tables.opt: Regenerated.
> * config/arm/bpabi.h (BE8_LINK_SPEC): Add marvell_pj4.
> * doc/invoke.texi: Added entry for marvell-pj4.
Another nit, I think the tune_marvell attribute now looks a bit
unneeded. You can just fold it into the "tune" clause of "generic_sched".
Thanks,
Chung-Lin
next prev parent reply other threads:[~2012-06-26 4:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 9:09 Yi-Hsiu Hsu
2012-06-13 18:33 ` Ramana Radhakrishnan
2012-06-14 7:47 ` Chung-Lin Tang
2012-06-20 3:52 ` Yi-Hsiu Hsu
2012-06-25 20:03 ` Ramana Radhakrishnan
2012-06-26 2:14 ` Yi-Hsiu Hsu
2012-06-26 5:51 ` Chung-Lin Tang [this message]
2012-06-26 7:46 ` Yi-Hsiu Hsu
2012-09-07 6:31 ` PING: " Yi-Hsiu Hsu
2012-11-30 4:44 ` Yi-Hsiu Hsu
2013-01-18 14:28 ` Ramana Radhakrishnan
2013-01-20 20:36 ` Matthias Klose
2013-01-21 6:15 ` Bin.Cheng
2013-01-21 10:00 ` Ramana Radhakrishnan
2013-01-21 8:52 ` Yi-Hsiu Hsu
2013-01-21 10:56 ` Ramana Radhakrishnan
2013-01-22 0:44 ` Yi-Hsiu Hsu
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=4FE93674.5070409@codesourcery.com \
--to=cltang@codesourcery.com \
--cc=ahsu@marvell.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramana.radhakrishnan@linaro.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 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).