* Removing Barreleye, Firestone, Garrison
@ 2018-01-29 6:58 Joel Stanley
2018-01-30 2:38 ` Stewart Smith
0 siblings, 1 reply; 3+ messages in thread
From: Joel Stanley @ 2018-01-29 6:58 UTC (permalink / raw)
To: OpenBMC Maillist
Hello,
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.
Cheers,
Joel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Removing Barreleye, Firestone, Garrison
2018-01-29 6:58 Removing Barreleye, Firestone, Garrison Joel Stanley
@ 2018-01-30 2:38 ` Stewart Smith
2018-02-06 4:32 ` Joel Stanley
0 siblings, 1 reply; 3+ messages in thread
From: Stewart Smith @ 2018-01-30 2:38 UTC (permalink / raw)
To: Joel Stanley, OpenBMC Maillist
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Removing Barreleye, Firestone, Garrison
2018-01-30 2:38 ` Stewart Smith
@ 2018-02-06 4:32 ` Joel Stanley
0 siblings, 0 replies; 3+ messages in thread
From: Joel Stanley @ 2018-02-06 4:32 UTC (permalink / raw)
To: Stewart Smith; +Cc: OpenBMC Maillist
On Tue, Jan 30, 2018 at 1:08 PM, Stewart Smith
<stewart@linux.vnet.ibm.com> wrote:
> 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.
Thanks for the response Stewart.
I've removed these three machines from the CI.
Cheers,
Joel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-02-06 4:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-29 6:58 Removing Barreleye, Firestone, Garrison Joel Stanley
2018-01-30 2:38 ` Stewart Smith
2018-02-06 4:32 ` Joel Stanley
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.