public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [Discussion] Deprecating Raspberry Pi
Date: Mon, 11 Feb 2019 15:27:07 +0100	[thread overview]
Message-ID: <20190211142707.GD805@yssyq.m.ilbers.de> (raw)
In-Reply-To: <990d9077-d17f-1a73-4f84-fb8fd80af73f@siemens.com>

On Mon, Feb 11, 2019 at 03:11:27PM +0100, Claudius Heine wrote:
> Ok, since you are using it, and it currently does not boot AFAIK, does that
> mean it is not tested regularly? IMO to have upstream support for a board
> means that it should be tested in the CI or similar as well. Otherwise it
> can be supported outside of Isar.
> 
> If you are willing to maintain RPi1 support then I have nothing against
> leaving it in upstream Isar.

The last time I used it was in Oct. I agree that it should be tested regularly
if it is in Isar. Let me check what is wrong.

With kind regards,
Baurzhan.

  reply	other threads:[~2019-02-11 14:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 12:41 Claudius Heine
2019-02-11 12:48 ` Jan Kiszka
2019-02-11 13:30   ` Claudius Heine
2019-02-11 13:51 ` [PATCH] remove raspberry support claudius.heine.ext
2019-02-11 14:03   ` Jan Kiszka
2019-02-12  9:30     ` [PATCH v2] remove RaspberryPi support claudius.heine.ext
2019-02-12 11:39       ` Baurzhan Ismagulov
2019-02-12 12:41         ` Claudius Heine
2019-02-12 16:40           ` Baurzhan Ismagulov
2019-02-12 16:49             ` Claudius Heine
2019-02-17 10:16               ` Baurzhan Ismagulov
2019-02-11 14:03 ` [Discussion] Deprecating Raspberry Pi Baurzhan Ismagulov
2019-02-11 14:11   ` Claudius Heine
2019-02-11 14:27     ` Baurzhan Ismagulov [this message]
2019-02-11 15:17       ` Claudius Heine
2019-02-17 10:44 ` Baurzhan Ismagulov
2019-02-18  8:44   ` Claudius Heine

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=20190211142707.GD805@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.com \
    /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