From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] simicsfs 1.18 does not build with kernel 4.12.2
Date: Wed, 30 Aug 2017 11:31:32 +0200 [thread overview]
Message-ID: <20170830113132.05c061ba@windsurf.lan> (raw)
In-Reply-To: <CAEUhbmWQN1nKa17ZpUqjVcX1S78Ap6QGUBkX+1vEBKXZ+7VWcw@mail.gmail.com>
Hello,
On Wed, 30 Aug 2017 17:25:51 +0800, Bin Meng wrote:
> >> However they are moving away from the simicsfs kernel module,
> >> replacing it with the user mode Simics Agent (Matic). They've seen
> >> that the kernel module has required too much maintenance work. For
> >> this reason they don't want to encourage use of it.
> >
> > So, we want to get rid of the simicsfs package in Buildroot ?
>
> I think so. Since they do not want new users of SimicsFS I don't think
> we want buildroot to automatically include it. Users should move to
> the Simics Agent instead. Otherwise they will be stuck supporting
> SimicsFS.
OK. Could you send a patch dropping the Buildroot package? Don't forget
to add the relevant logic in Config.in.legacy, and the entry in the
DEVELOPERS file.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-08-30 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 12:47 [Buildroot] simicsfs 1.18 does not build with kernel 4.12.2 Bin Meng
2017-08-24 17:33 ` Thomas Petazzoni
2017-08-24 17:50 ` Matthew Weber
2017-08-24 21:02 ` Thomas Petazzoni
2017-08-24 21:27 ` Matthew Weber
2017-08-25 1:47 ` Bin Meng
2017-08-29 14:26 ` Bin Meng
2017-08-29 15:37 ` Thomas Petazzoni
2017-08-30 9:25 ` Bin Meng
2017-08-30 9:31 ` Thomas Petazzoni [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=20170830113132.05c061ba@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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.