From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] legacy: add entries for renamed/removed MIPS CPU cores
Date: Sun, 13 Nov 2016 17:55:13 +0100 [thread overview]
Message-ID: <20161113175513.3c763f0d@free-electrons.com> (raw)
In-Reply-To: <1479052521-27651-1-git-send-email-yann.morin.1998@free.fr>
Hello,
On Sun, 13 Nov 2016 16:55:21 +0100, Yann E. MORIN wrote:
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
This is not necessary, and has already been discussed by Arnout during
the review of Vicente patches. Those MIPS core options have been added
and renamed within the 2016.11 release cycle, so there is no point in
having legacy handling, since no Buildroot release ever had the old
name for these.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-13 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 15:55 [Buildroot] [PATCHv2] legacy: add entries for renamed/removed MIPS CPU cores Yann E. MORIN
2016-11-13 16:55 ` Thomas Petazzoni [this message]
2016-11-13 17:18 ` Yann E. MORIN
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=20161113175513.3c763f0d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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