All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] testing: add python-crossbar tests
Date: Sun, 21 Oct 2018 09:28:48 +0200	[thread overview]
Message-ID: <20181021092848.2c1abd44@windsurf.lan> (raw)
In-Reply-To: <5bcc083188f1f_56b83f8d16040a3c5959@ultri5.mail>

Hello,

On Sun, 21 Oct 2018 02:01:37 -0300, Ricardo Martincoski wrote:

> We could update the default kernel image used by the test infra (today 3.11.0),

We can definitely update that pre-built image if needed. There is no
special reason to have a 3.11 based image, except this being the kernel
version I had around at the time I started playing with the test
infrastructure.

> The most elegant solution IMO is to add haveged to the image built for this test
> case by the test infra. This is what people with a real target with low entropy
> probably would use, I guess. There is no need to update the kernel this way.

I also don't see any problem with adding haveged in the image.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-10-21  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 13:38 [Buildroot] [RFC] testing: add python-crossbar tests yegorslists at googlemail.com
2018-02-15 13:41 ` Yegor Yefremov
2018-02-16  1:16   ` Ricardo Martincoski
2018-09-17 13:55     ` Thomas Petazzoni
2018-09-18  2:31       ` Ricardo Martincoski
2018-09-18  6:20         ` Yegor Yefremov
2018-10-20 15:49           ` Asaf Kahlon
2018-10-21  5:01             ` Ricardo Martincoski
2018-10-21  7:28               ` Thomas Petazzoni [this message]
2018-02-22  1:53 ` Ricardo Martincoski

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=20181021092848.2c1abd44@windsurf.lan \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.