From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sh64: drop support for architecture
Date: Fri, 10 Apr 2015 23:13:10 +0200 [thread overview]
Message-ID: <55283CE6.2080707@mind.be> (raw)
In-Reply-To: <20150409192212.GB27057@waldemar-brodkorb.de>
On 09/04/15 21:22, Waldemar Brodkorb wrote:
> Hi Thomas,
> Thomas Petazzoni wrote,
>
>> Dear Waldemar Brodkorb,
>>
>> On Tue, 7 Apr 2015 22:31:01 +0200, Waldemar Brodkorb wrote:
>>> There seems to be no hardware or emulator available for this
>>> architecture. Someone from ST Microelectronics told me that
>>> sh64/sh5 projects are dropped over ten years ago.
>>> I found nothing about real hardware on the sites of Hitachi
>>> or Renesas.
>>> We should drop this.
>>> Support in uClibc-ng will be dropped in 1.1.
>>>
>>> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
>>
>> Following my and Peter comments, we'd prefer to see this feature to be
>> marked as deprecated. I've marked the patch as "Rejected" in patchwork.
>> Can you cook a patch simply marking sh64 as deprecated?
>
> Is there documentation how to do this?
Just add
depends on BR2_DEPRECATED_SINCE_2015_05
(check 'git log -p --grep deprecate' for examples)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2015-04-10 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 20:31 [Buildroot] [PATCH] sh64: drop support for architecture Waldemar Brodkorb
2015-04-07 21:30 ` Thomas Petazzoni
2015-04-07 21:35 ` Waldemar Brodkorb
2015-04-07 21:57 ` Peter Korsgaard
2015-04-08 20:53 ` Thomas Petazzoni
2015-04-09 19:22 ` Waldemar Brodkorb
2015-04-10 21:13 ` Arnout Vandecappelle [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=55283CE6.2080707@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.