From: Petr Vorel <pvorel@suse.cz>
To: Rob Landley <rob@landley.net>
Cc: Andrea Cervesato <andrea.cervesato@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Linux-sh list <linux-sh@vger.kernel.org>,
Christophe Lyon <christophe.lyon@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, Li Wang <liwang@redhat.com>,
linux-m68k@lists.linux-m68k.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Cyril Hrubis <chrubis@suse.cz>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
linux-riscv <linux-riscv@lists.infradead.org>,
buildroot@buildroot.org, Greg Ungerer <gerg@linux-m68k.org>,
ltp@lists.linux.it, automated-testing@lists.yoctoproject.org
Subject: [Buildroot] Call for nommu LTP maintainer [was: Re: [PATCH 00/36] Remove UCLINUX from LTP]
Date: Fri, 5 Jan 2024 14:11:35 +0100 [thread overview]
Message-ID: <20240105131135.GA1484621@pevik> (raw)
In-Reply-To: <5a1f1ff3-8a61-67cf-59a9-ce498738d912@landley.net>
Hi all,
[ Cc also automated-testing and buildroot ML
FYI thread started here:
https://lore.kernel.org/ltp/20240103015240.1065284-1-pvorel@suse.cz/ ]
> On 1/3/24 06:09, Cyril Hrubis wrote:
> > Hi!
> >> I am not sure I agree with this series.
> >> Removing support for UCLINUX from LTP is almost a guarantee for
> >> not noticing when more breakage is introduced.
> >> How exactly is UCLINUX broken in LTP?
> > As far as we know noone is using it and nobody is maintaing it for a
> > decade,
> Nobody is maintaining "uclinux" because that was a distro, but you can build
> nommu support in buildroot and such, and people do.
Right, there are nommu users. Will anybody join LTP development to maintain
nommu support in LTP? The needed work is to add this support to LTP new C API
[1] and use it in the relevant test. There is some implementation in the old
API, I have no idea how well it worked.
If nobody stands for maintaing nommu, we will have to delete it. There is nobody
from the current maintainers who is using LTP on nommu HW (that is the reason why
nommu support have not been implemented in the new API).
Kind regards,
Petr
> Rob
[1] https://github.com/linux-test-project/ltp/wiki/C-Test-API
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next parent reply other threads:[~2024-01-05 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240103015240.1065284-1-pvorel@suse.cz>
[not found] ` <CAMuHMdXGwyS-CL0vLdUP4Z4YEYhmcmDyC3YdGCnS=jFkqASqvw@mail.gmail.com>
[not found] ` <20240103114957.GD1073466@pevik>
[not found] ` <CAMuHMdX0s0gLRoPtjJmDnSmZ_MNY590dN+JxM1HKAL1g_bjX+w@mail.gmail.com>
[not found] ` <ZZVOhlGPg5KRyS-F@yuki>
[not found] ` <5a1f1ff3-8a61-67cf-59a9-ce498738d912@landley.net>
2024-01-05 13:11 ` Petr Vorel [this message]
2024-01-06 3:58 ` [Buildroot] Call for nommu LTP maintainer [was: Re: [PATCH 00/36] Remove UCLINUX from LTP] Rob Landley
2024-01-08 9:03 ` Petr Vorel
2024-01-09 20:24 ` Rob Landley
[not found] ` <461a6556-8f24-48f5-811a-498cb44f2d64@linux-m68k.org>
2024-01-10 5:47 ` Rob Landley
[not found] ` <20240110133358.GB1698252@pevik>
2024-01-10 18:23 ` Rob Landley
[not found] ` <ZZvJXTshFUYSaMVH@yuki>
[not found] ` <SA3PR13MB6372498CC6372F8B16237244FD6A2@SA3PR13MB6372.namprd13.prod.outlook.com>
2024-01-10 5:01 ` [Buildroot] [Automated-testing] " Rob Landley
[not found] ` <20240110141455.GC1698252@pevik>
2024-01-10 19:23 ` Rob Landley
2024-01-10 21:17 ` Niklas Cassel via buildroot
[not found] ` <7e348eb3-bd34-4c66-9ed6-b5108da80486@linux-m68k.org>
2024-01-11 9:21 ` Niklas Cassel via buildroot
2024-01-12 20:18 ` Rob Landley
[not found] ` <81c07a13-305a-404b-b14c-3aff8fde3f67@linux-m68k.org>
2024-01-12 20:16 ` Rob Landley
2024-01-15 13:41 ` Waldemar Brodkorb
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=20240105131135.GA1484621@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=buildroot@buildroot.org \
--cc=christophe.lyon@linaro.org \
--cc=chrubis@suse.cz \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=rdunlap@infradead.org \
--cc=rob@landley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox