mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jan Remmet <J.Remmet@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] bootstate: add framework for redundant boot scenarios
Date: Fri, 27 Nov 2015 08:38:17 +0100	[thread overview]
Message-ID: <20151127073817.GN11966@pengutronix.de> (raw)
In-Reply-To: <20151126080445.GA3245@lws-weitzel2@phytec.de>

Hi Jan,

On Thu, Nov 26, 2015 at 09:04:46AM +0100, Jan Remmet wrote:
> On Wed, May 27, 2015 at 05:22:58PM +0200, Marc Kleine-Budde wrote:
> > There are several use cases where a redundant Linux system is needed. The
> > barebox,bootstate framework provides the building blocks to model different
> > use cases without the need to start from the scratch over and over again.
> Hello,
> is there any reason why this wasn't applied? I tested it and it works fine.
> There is also a watchdog handling now in commands/boot.c so we can rework the
> bootchooser.

I think the best reason is that we just haven't done it yet... I just
merged Marcs state framework enhancements series which contains some
dependencies for the bootchooser. With this I think it's just a matter
of resending the latest version of the bootchooser and doing a final
review. Marc will probably resend it soon ;)

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-11-27  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 15:22 Marc Kleine-Budde
2015-11-26  8:04 ` Jan Remmet
2015-11-27  7:38   ` Sascha Hauer [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=20151127073817.GN11966@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=J.Remmet@phytec.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox