All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Joel Stanley <joel@jms.id.au>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Removing Barreleye, Firestone, Garrison
Date: Tue, 30 Jan 2018 13:38:12 +1100	[thread overview]
Message-ID: <87a7ww136z.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACPK8XfKMTv+=LJbdoMDOOkQ4izwqq81=vHmM-Z8x6GZ6FyqGA@mail.gmail.com>

Joel Stanley <joel@jms.id.au> writes:
> I am working on ensuring the boards that we build for are working with
> the dev-4.13 kernel branch. Currently Barreleye, Firestone and
> Garrison systems fail as there has not been a device tree forward
> ported.
>
> Is there an interest in maintaining these platforms?
>
> If not, I will remove them from CI on Friday to unblock the kernel work.
>
> This does not stop someone re-enabling them in the near future should
> interest arise. However, I suggest we create a policy on removing
> abandoned machines when there is no one actively maintaining them, and
> we use this to delete machines once they reach the agreed criteria.

From a primarily consumer of OpenBMC perspective, I think it's okay to
remove them. Booting the host on Firestone/Garrison with OpenBMC has
always been somewhat sketchy.

-- 
Stewart Smith
OPAL Architect, IBM.

  reply	other threads:[~2018-01-30  2:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29  6:58 Removing Barreleye, Firestone, Garrison Joel Stanley
2018-01-30  2:38 ` Stewart Smith [this message]
2018-02-06  4:32   ` Joel Stanley

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=87a7ww136z.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.vnet.ibm.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.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 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.