public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Remove sh2, sh3, sh4 architecture?
Date: Sun, 18 Oct 2015 11:54:56 -0400	[thread overview]
Message-ID: <20151018155456.GY23893@bill-the-cat> (raw)
In-Reply-To: <CAK7LNAQLAZVD-vx2Q0nFLerxvxV59aL_vqgyevzWWD-eo0D8Kg@mail.gmail.com>

On Mon, Oct 19, 2015 at 12:30:43AM +0900, Masahiro Yamada wrote:
> 2015-10-18 21:19 GMT+09:00 Simon Glass <sjg@chromium.org>:
> > Hi,
> >
> > It looks like these have no maintainer and have not been converted to
> > generic board. Should we remove the 'sh' architecture?
> >
> > Regards,
> > Simon
> 
> 
> The maintainer, Nobuhiro, was at the U-Boot mini summit,
> but, indeed, no work for SH these days.
> 
> Since he left Renesas and went back to Hitachi,
> he is now a complete volunteer, I guess.
> 
> If the maintainer responsibility is painful for him,
> he can take a step back, but I hope he can continue contribution...
> Nobuhiro?

I'd hate to see SH2 leave since it's becoming the J-Core architecture..
Perhaps someone in the community would like to help out too?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151018/2b6680e8/attachment.sig>

  reply	other threads:[~2015-10-18 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18 12:19 [U-Boot] Remove sh2, sh3, sh4 architecture? Simon Glass
2015-10-18 15:30 ` Masahiro Yamada
2015-10-18 15:54   ` Tom Rini [this message]
2015-10-18 16:19     ` Masahiro Yamada
2016-05-14 23:19       ` Simon Glass
2016-05-16  6:18         ` Yoshinori Sato
2016-05-16 13:16           ` Simon Glass
2016-05-17  8:02             ` Yoshinori Sato
2016-05-17  9:24         ` Kieran Bingham

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=20151018155456.GY23893@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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