kselftest/next build: 4 builds: 2 failed, 2 passed, 2 errors, 4 warnings
(v6.8-rc1-57-g5d94da7ff00e)
Full Build Summary:
https://kernelci.org/build/kselftest/branch/next/kernel/v6.8-rc1-57-g5d94da7ff00e/
Tree: kselftest
Branch: next
Git Describe: v6.8-rc1-57-g5d94da7ff00e
Git Commit:
> +/* Pick any address that was not mapped into the guest to test MMIO */
> +#define TDX_MMIO_TEST_ADDR 0x2
Also need to test below MMIO addresses
(1) GPA with shared bit on.
(2) GPA in memslot
Hi Mina,
I recommend you cc linux-mm and Matthew Wilcox on these two patches also.
David
On 3/5/24 1:58 AM, Kees Cook wrote:
> On Mon, Mar 04, 2024 at 08:59:24PM +0500, Muhammad Usama Anjum wrote:
>> Conform the layout, informational and status messages to TAP. No
>> functional change is intended other than the layout of output messages.
>>
>> Signed-off-by: Muhammad Usama Anjum
>>
On Sat, Mar 02, 2024 at 03:31:07PM +0800, Binbin Wu wrote:
> On 12/13/2023 4:46 AM, Sagi Shahar wrote:
> > The test verifies that the guest runs TDVMCALL and the
> > guest vCPU enters to the halted state.
> >
> > Signed-off-by: Erdem Aktas
> > Signed-off-by: Sagi Shahar
> > Signed-off-by:
The test uses PERF_RECORD_SWITCH records to fill the ring buffer and
trigger the watermark wakeup, which in turn should trigger an IO
signal.
Signed-off-by: Kyle Huey
---
.../testing/selftests/perf_events/.gitignore | 1 +
tools/testing/selftests/perf_events/Makefile | 2 +-
The config fragment enlists all the config options needed for the test.
This config is merged into the kernel's config on which this test is
run.
Reviewed-by: T.J. Mercier
Signed-off-by: Muhammad Usama Anjum
---
Changes since v1:
- Add reviewed-by tag
---
Conform the layout, informational and status messages to TAP. No
functional change is intended other than the layout of output messages.
Reviewed-by: T.J. Mercier
Signed-off-by: Muhammad Usama Anjum
---
Changes since v4:
- close fds correctly with code changes added in v3
Chanages since v3:
-
On 3/5/24 12:08 AM, Nico Pache wrote:
> On Fri, Mar 1, 2024 at 2:35 AM Muhammad Usama Anjum
> wrote:
>>
>> On 3/1/24 12:33 PM, Nico Pache wrote:
>>> On systems that have large core counts and large page sizes, but limited
>>> memory, the userfaultfd test hugepage requirement is too large.
>>>
>>>
On 12/13/2023 4:46 AM, Sagi Shahar wrote:
From: Ackerley Tng
This tests the use of guest memory with explicit MapGPA calls.
Signed-off-by: Ackerley Tng
Signed-off-by: Ryan Afranji
Signed-off-by: Sagi Shahar
---
tools/testing/selftests/kvm/Makefile | 1 +
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Wed, 28 Feb 2024 17:37:01 +0530 you wrote:
> Changes :
> - "excercise" is corrected to "exercise" in
> drivers/net/mlxsw/spectrum-2/tc_flower.sh
> - "mutliple" is corrected to "multiple" in
>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Thu, 29 Feb 2024 11:38:25 -0300 you wrote:
> Add the dependsOn test check for all the mirred blockcast tests.
> It will prevent the issue reported by LKFT which happens when an older
> iproute2 is used to run the
ncdevmem is a devmem TCP netcat. It works similarly to netcat, but it
sends and receives data using the devmem TCP APIs. It uses udmabuf as
the dmabuf provider. It is compatible with a regular netcat running on
a peer, or a ncdevmem running on a peer.
In addition to normal netcat support,
Signed-off-by: Mina Almasry
---
v1 -> v2:
- Missing spdx (simon)
- add to index.rst (simon)
---
Documentation/networking/devmem.rst | 271
Documentation/networking/index.rst | 1 +
2 files changed, 272 insertions(+)
create mode 100644
Add an interface for the user to notify the kernel that it is done
reading the devmem dmabuf frags returned as cmsg. The kernel will
drop the reference on the frags to make them available for reuse.
Signed-off-by: Willem de Bruijn
Signed-off-by: Kaiyuan Zhang
Signed-off-by: Mina Almasry
---
In tcp_recvmsg_locked(), detect if the skb being received by the user
is a devmem skb. In this case - if the user provided the MSG_SOCK_DEVMEM
flag - pass it to tcp_recvmsg_devmem() for custom handling.
tcp_recvmsg_devmem() copies any data in the skb header to the linear
buffer, and returns a
For device memory TCP, we expect the skb headers to be available in host
memory for access, and we expect the skb frags to be in device memory
and unaccessible to the host. We expect there to be no mixing and
matching of device memory frags (unaccessible) with host memory frags
(accessible) in the
Make skb_frag_page() fail in the case where the frag is not backed
by a page, and fix its relevant callers to handle this case.
Signed-off-by: Mina Almasry
---
v6:
- Rebased on top of the merged netmem changes.
Changes in v1:
- Fix illegal_highdma() (Yunsheng).
- Rework napi_pp_put_page()
Implement a memory provider that allocates dmabuf devmem in the form of
net_iov.
The provider receives a reference to the struct netdev_dmabuf_binding
via the pool->mp_priv pointer. The driver needs to set this pointer for
the provider in the net_iov.
The provider obtains a reference on the
Abstrace the memory type from the page_pool so we can later add support
for new memory types. Convert the page_pool to use the new netmem type
abstraction, rather than use struct page directly.
As of this patch the netmem type is a no-op abstraction: it's always a
struct page underneath. All the
Convert netmem to be a union of struct page and struct netmem. Overload
the LSB of struct netmem* to indicate that it's a net_iov, otherwise
it's a page.
Currently these entries in struct page are rented by the page_pool and
used exclusively by the net stack:
struct {
unsigned long
Implement netdev devmem allocator. The allocator takes a given struct
netdev_dmabuf_binding as input and allocates net_iov from that
binding.
The allocation simply delegates to the binding's genpool for the
allocation logic and wraps the returned memory region in a net_iov
struct.
Signed-off-by:
Add a netdev_dmabuf_binding struct which represents the
dma-buf-to-netdevice binding. The netlink API will bind the dma-buf to
rx queues on the netdevice. On the binding, the dma_buf_attach
& dma_buf_map_attachment will occur. The entries in the sg_table from
mapping will be inserted into a
API takes the dma-buf fd as input, and binds it to the netdevice. The
user can specify the rx queues to bind the dma-buf to.
Suggested-by: Stanislav Fomichev
Signed-off-by: Mina Almasry
---
Changes in v1:
- Add rx-queue-type to distingish rx from tx (Jakub)
- Return dma-buf ID from netlink
The check is duplicated in 2 places, factor it out into a common helper.
Signed-off-by: Mina Almasry
---
net/core/page_pool.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/net/core/page_pool.c b/net/core/page_pool.c
index 8776fcad064a..fe9de4ecce94 100644
---
From: Jakub Kicinski
The page providers which try to reuse the same pages will
need to hold onto the ref, even if page gets released from
the pool - as in releasing the page from the pp just transfers
the "ownership" reference from pp to the provider, and provider
will wait for other references
This API enables the net stack to reset the queues used for devmem.
Signed-off-by: Mina Almasry
---
include/linux/netdevice.h | 24
1 file changed, 24 insertions(+)
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index c41019f34179..3105c586355d
RFC v6:
===
Major Changes:
--
This revision largely rebases on top of net-next and addresses the little
feedback RFCv5 received.
The series remains in RFC because the queue-API ndos defined in this
series are not yet implemented. I have a GVE implementation I carry out
of tree
> +void verify_guest_msr_writes(void)
> +{
> + struct kvm_vcpu *vcpu;
> + struct kvm_vm *vm;
> +
> + uint64_t data;
> + int ret;
> +
> + vm = td_create();
> + td_initialize(vm, VM_MEM_SRC_ANONYMOUS, 0);
> +
> + /*
> + * Set explicit MSR filter map to control access
On Mon, Mar 04, 2024 at 03:36:20PM -0800, Jakub Kicinski wrote:
> selftest harness uses various exit codes to signal test
> results. Avoid calling exit() directly, otherwise tests
> may get broken by harness refactoring (like the commit
> under Fixes). SKIP() will instruct the harness that the
>
With the removal of the ARCH_NR_GPIOS, the number of available GPIOs
is effectively unlimited, causing the gpio-mockup module load failure
test that overflowed the number of GPIOs to unexpectedly succeed, and
so fail.
The test is no longer relevant so remove it.
Promote the "no lines defined"
On Mon, 4 Mar 2024 15:14:04 -0800 Kees Cook wrote:
> > Ugh, I'm guessing vfork() "eats" the signal, IOW grandchild signals,
> > child exits? vfork() and signals.. I'd rather leave to Kees || Mickael.
>
> Oh no, that does seem bad. Since Mickaël is also seeing weird issues,
> can we drop the
selftest harness uses various exit codes to signal test
results. Avoid calling exit() directly, otherwise tests
may get broken by harness refactoring (like the commit
under Fixes). SKIP() will instruct the harness that the
test shouldn't run, it used to not be the case, but that
has been fixed. So
On Mon, Mar 04, 2024 at 03:04:11PM -0800, Jakub Kicinski wrote:
> On Mon, 4 Mar 2024 22:20:03 + Mark Brown wrote:
> > On Wed, Feb 28, 2024 at 04:59:07PM -0800, Jakub Kicinski wrote:
> >
> > > When running selftests for our subsystem in our CI we'd like all
> > > tests to pass. Currently some
On Mon, 4 Mar 2024 22:20:03 + Mark Brown wrote:
> On Wed, Feb 28, 2024 at 04:59:07PM -0800, Jakub Kicinski wrote:
>
> > When running selftests for our subsystem in our CI we'd like all
> > tests to pass. Currently some tests use SKIP for cases they
> > expect to fail, because the
On Wed, Feb 28, 2024 at 04:59:07PM -0800, Jakub Kicinski wrote:
> When running selftests for our subsystem in our CI we'd like all
> tests to pass. Currently some tests use SKIP for cases they
> expect to fail, because the kselftest_harness limits the return
> codes to pass/fail/skip. XFAIL which
Hi Linus,
Thank you for your reply and valuable inputs.
On 01/03/2024 17:10, Linus Torvalds wrote:
On Fri, 1 Mar 2024 at 02:27, Nikolai Kondrashov wrote:
I agree, it's hard to imagine even a simple majority agreeing on how GitLab CI
should be done. Still, we would like to help people, who
On Mon, Mar 04, 2024 at 08:59:24PM +0500, Muhammad Usama Anjum wrote:
> Conform the layout, informational and status messages to TAP. No
> functional change is intended other than the layout of output messages.
>
> Signed-off-by: Muhammad Usama Anjum
> ---
>
On Mon, Mar 04, 2024 at 08:59:23PM +0500, Muhammad Usama Anjum wrote:
> The following line is missing from the test's execution. Add it to make
> it fully TAP conformant:
> # Totals: pass:27 fail:0 xfail:0 xpass:0 skip:0 error:0
>
> Signed-off-by: Muhammad Usama Anjum
Thanks, looks good.
On 3/1/24 09:28, Miguel Ojeda wrote:
On Fri, Mar 1, 2024 at 4:22 PM Laura Nao wrote:
Adding --first-time (you meant --first-time, right?) definitely makes
sense, thanks for the pointer. I think having the modules being built-in
should be treated as a skip, same as when they are not there at
On Mon, Mar 4, 2024 at 9:09 AM Maxime Ripard wrote:
[ ...]
>
> And singling out DRM because it regularly allegedly breaks things on
> xtensa or m68k and claiming we're not taking CI seriously because of it
> is completely ridiculous. If the all the subsystems were taking CI as
> seriously as
On Mon, Mar 04, 2024 at 08:27:50PM +0100, Mickaël Salaün wrote:
> Testing the whole series, I found that some Landlock tests are flaky
> starting with this patch. I tried to not use the longjmp in the
> grandchild but it didn't change. I suspect missing volatiles but I
> didn't find the faulty
Testing the whole series, I found that some Landlock tests are flaky
starting with this patch. I tried to not use the longjmp in the
grandchild but it didn't change. I suspect missing volatiles but I
didn't find the faulty one(s) yet. :/
I'll continue investigating tomorrow but help would be
On Fri, Mar 1, 2024 at 2:35 AM Muhammad Usama Anjum
wrote:
>
> On 3/1/24 12:33 PM, Nico Pache wrote:
> > On systems that have large core counts and large page sizes, but limited
> > memory, the userfaultfd test hugepage requirement is too large.
> >
> > Exiting early due to missing one test's
; This works fine on Linux version 6.8.0-rc6
>>>>>>>
>>>>>>> Hi Aishwarya,
>>>>>>>
>>>>>>> Can you try the attached patch and see if it fixes the failure? I
>>>>>>> changed
>>>>&
20240228" at repo
>>>>>>>>> "https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git;.
>>>>>>>>>
>>>>>>>>> This works fine on Linux version 6.8.0-rc6
>>>>>>>>
>>&
; This works fine on Linux version 6.8.0-rc6
>>>>>>>
>>>>>>> Hi Aishwarya,
>>>>>>>
>>>>>>> Can you try the attached patch and see if it fixes the failure? I
>>>>>>> changed
>>>>&
Fixes clang warning: absolute value function 'abs' given an argument of
type 'long long' but has parameter of type 'int' which may cause
truncation of value.
Signed-off-by: Edward Liaw
---
tools/testing/selftests/timers/posix_timers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
No functional change.
Signed-off-by: Thomas Gleixner
[edliaw: Fix checkpatch recommendations]
Signed-off-by: Edward Liaw
---
tools/testing/selftests/timers/posix_timers.c | 161 +++---
1 file changed, 66 insertions(+), 95 deletions(-)
diff --git
The signal distribution test has a tendency to hang for a long time as the
signal delivery is not really evenly distributed.
Increasing the timer interval to 10ms makes this less likely. Add a timeout
to catch the case where it hangs and terminate the test gracefully.
While at it get rid of the
I'm sending some patches that were orignally in
https://lore.kernel.org/lkml/20230606132949.068951...@linutronix.de/
to prevent the timer_distribution test from hanging and also fix some
format inconsistencies.
Edward Liaw (3):
selftests/timers/posix_timers: Make signal distribution test less
On Fri, Mar 1, 2024 at 12:45 AM Muhammad Usama Anjum
wrote:
>
> Conform the layout, informational and status messages to TAP. No
> functional change is intended other than the layout of output messages.
>
> Signed-off-by: Muhammad Usama Anjum
> ---
> Chanages since v3:
> - abort test-case
On Mon, Mar 4, 2024 at 9:09 AM Maxime Ripard wrote:
> And singling out DRM because it regularly allegedly breaks things on
> xtensa or m68k and claiming we're not taking CI seriously because of it
> is completely ridiculous. If the all the subsystems were taking CI as
> seriously as DRM, we
On Mon, Mar 04, 2024 at 08:17:22AM -0800, Guenter Roeck wrote:
> On Mon, Mar 4, 2024 at 8:05 AM Maxime Ripard wrote:
> >
> > On Mon, Mar 04, 2024 at 07:46:34AM -0800, Guenter Roeck wrote:
> > > On Mon, Mar 4, 2024 at 1:24 AM Maxime Ripard wrote:
> > > [ ... ]
> > > >
> > > > If anything, it's
On Mon, Mar 4, 2024 at 8:05 AM Maxime Ripard wrote:
>
> On Mon, Mar 04, 2024 at 07:46:34AM -0800, Guenter Roeck wrote:
> > On Mon, Mar 4, 2024 at 1:24 AM Maxime Ripard wrote:
> > [ ... ]
> > >
> > > If anything, it's more of a side-effect to the push for COMPILE_TEST
> > > than anything.
> > >
>
On Mon, Mar 04, 2024 at 07:46:34AM -0800, Guenter Roeck wrote:
> On Mon, Mar 4, 2024 at 1:24 AM Maxime Ripard wrote:
> [ ... ]
> >
> > If anything, it's more of a side-effect to the push for COMPILE_TEST
> > than anything.
> >
>
> If the drm subsystem maintainers don't want people to build it
Conform the layout, informational and status messages to TAP. No
functional change is intended other than the layout of output messages.
While at it, do minor cleanups like move the declarations of the variables
on top of the function.
Signed-off-by: Muhammad Usama Anjum
---
Conform the layout, informational and status messages to TAP. No
functional change is intended other than the layout of output messages.
Signed-off-by: Muhammad Usama Anjum
---
tools/testing/selftests/exec/load_address.c | 34 +
1 file changed, 15 insertions(+), 19
The following line is missing from the test's execution. Add it to make
it fully TAP conformant:
# Totals: pass:27 fail:0 xfail:0 xpass:0 skip:0 error:0
Signed-off-by: Muhammad Usama Anjum
---
tools/testing/selftests/exec/binfmt_script.py | 10 +-
1 file changed, 9 insertions(+), 1
t fixes the failure? I changed
>>>>> the test to accept XFS dev as input, mount XFS on a temp folder under
>>>>> /tmp,
>>>>> and skip if no XFS is mounted.
>>>>
>>>> Please try this updated one. It allows you to specify a XFS dev
his works fine on Linux version 6.8.0-rc6
>>>>>>
>>>>>> Hi Aishwarya,
>>>>>>
>>>>>> Can you try the attached patch and see if it fixes the failure? I changed
>>>>>> the test to accept XFS dev as input, mount X
On Mon, Mar 4, 2024 at 1:24 AM Maxime Ripard wrote:
[ ... ]
>
> If anything, it's more of a side-effect to the push for COMPILE_TEST
> than anything.
>
If the drm subsystem maintainers don't want people to build it with
COMPILE_TEST while at the same time not limiting it to platforms where
it
e try this updated one. It allows you to specify a XFS device path
>>> in SPLIT_HUGE_PAGE_TEST_XFS_PATH env variable, which is passed to
>>> split_huge_page_test in run_vmtests.sh. It at least allow CI/CD to run
>>> the test without too much change.
>>
>> O
On 3/4/24 3:10 PM, patchwork-bot+netdev...@kernel.org wrote:
On Sun, 3 Mar 2024 16:32:23 +0800 you wrote:
Implemented XDP transmit hardware timestamp metadata for igc driver.
This patchset is tested with tools/testing/selftests/bpf/xdp_hw_metadata
on Intel ADL-S platform. Below are the test
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann :
On Sun, 3 Mar 2024 16:32:23 +0800 you wrote:
> Implemented XDP transmit hardware timestamp metadata for igc driver.
>
> This patchset is tested with tools/testing/selftests/bpf/xdp_hw_metadata
> on Intel ADL-S
On 12/13/2023 4:46 AM, Sagi Shahar wrote:
From: Ackerley Tng
Signed-off-by: Ackerley Tng
Signed-off-by: Ryan Afranji
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86_64/tdx/tdx.h| 21 +++
.../selftests/kvm/lib/x86_64/tdx/tdx.c| 19
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller :
On Fri, 01 Mar 2024 19:18:24 +0100 you wrote:
> This series from Geliang adds two new Netlink commands to the userspace
> PM:
>
> - one to dump all addresses of a specific MPTCP connection:
> - feature added in
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller :
On Fri, 01 Mar 2024 18:11:21 +0100 you wrote:
> Here are two patches fixing issues in MPTCP diag.sh kselftest:
>
> - Patch 1 makes sure the exit code is '1' in case of error, and not the
> test ID, not to return an
On Mon, Mar 04, 2024 at 12:12:47PM +0100, Geert Uytterhoeven wrote:
> Hi Maxime,
>
> On Mon, Mar 4, 2024 at 11:20 AM Maxime Ripard wrote:
> > On Mon, Mar 04, 2024 at 11:07:22AM +0100, Geert Uytterhoeven wrote:
> > > On Mon, Mar 4, 2024 at 10:15 AM Maxime Ripard wrote:
> > > > On Mon, Mar 04,
Hi Maxime,
On Mon, Mar 4, 2024 at 11:20 AM Maxime Ripard wrote:
> On Mon, Mar 04, 2024 at 11:07:22AM +0100, Geert Uytterhoeven wrote:
> > On Mon, Mar 4, 2024 at 10:15 AM Maxime Ripard wrote:
> > > On Mon, Mar 04, 2024 at 09:12:38AM +0100, Geert Uytterhoeven wrote:
> > > > On Sun, Mar 3, 2024 at
le-endian platforms with +200 GiB/s memory bandwidth):
> > >
> > > ---8<---
> > > Subject: kisskb: FAILED linux-next/m68k-allmodconfig/m68k-gcc8 Mon Mar
> > > 04, 06:35
> > > To: ge
h +200 GiB/s memory bandwidth):
> >
> > ---8<---
> > Subject: kisskb: FAILED linux-next/m68k-allmodconfig/m68k-gcc8 Mon Mar 04,
> > 06:35
> > To: ge...@linux-m68k.org
> > Date: Mon, 04 Mar 2024 08
On 12/13/2023 4:46 AM, Sagi Shahar wrote:
From: Ackerley Tng
vm_vaddr_alloc always allocates memory in memslot 0. This allows users
of this function to choose which memslot to allocate virtual memory
in.
Nit: The patch exposes vm_vaddr_alloc() instead of _vm_vaddr_alloc().
, mount XFS on a temp folder under /tmp,
>>> and skip if no XFS is mounted.
>>
>> Please try this updated one. It allows you to specify a XFS device path
>> in SPLIT_HUGE_PAGE_TEST_XFS_PATH env variable, which is passed to
>> split_huge_page_test in run_vmtests.sh. It at least al
On Mon, Mar 04, 2024 at 05:16:53PM +0800, Binbin Wu wrote:
>
>
> On 3/4/2024 10:19 AM, Yan Zhao wrote:
> > On Tue, Dec 12, 2023 at 12:46:25PM -0800, Sagi Shahar wrote:
> > > From: Erdem Aktas
> > >
> > > Verifies TDVMCALL READ and WRITE operations.
> > >
> > > Signed-off-by: Erdem Aktas
> >
On Sat, Mar 02, 2024 at 02:10:51PM -0800, Guenter Roeck wrote:
> On Thu, Feb 29, 2024 at 12:21 PM Linus Torvalds
> wrote:
> >
> > On Thu, 29 Feb 2024 at 01:23, Nikolai Kondrashov wrote:
> > >
> > > However, I think a better approach would be *not* to add the
> > > .gitlab-ci.yaml
> > > file in
On 3/4/2024 10:19 AM, Yan Zhao wrote:
On Tue, Dec 12, 2023 at 12:46:25PM -0800, Sagi Shahar wrote:
From: Erdem Aktas
Verifies TDVMCALL READ and WRITE operations.
Signed-off-by: Erdem Aktas
Signed-off-by: Sagi Shahar
Signed-off-by: Ackerley Tng
Signed-off-by: Ryan Afranji
---
config/m68k-gcc8 Mon Mar 04,
> 06:35
> To: ge...@linux-m68k.org
> Date: Mon, 04 Mar 2024 08:05:14 -0000
>
> FAILED linux-next/m68k-allmodconfig/m68k-gcc8 Mon Mar 04, 06:35
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/15135537/
>
> Commit: Add linux-next specific fi
On 02/03/2024 10:48 pm, Gustavo Padovan wrote:
On Friday, March 01, 2024 18:56 -03, Guillaume Tucker
wrote:
On 29/02/2024 17:28, Nicolas Dufresne wrote:
Hi,
Le jeudi 29 février 2024 à 16:16 +0200, Nikolai Kondrashov a écrit :
On 2/29/24 2:20 PM, Guillaume Tucker wrote:
Hello,
On
--
Subject: kisskb: FAILED linux-next/m68k-allmodconfig/m68k-gcc8 Mon Mar 04, 06:35
To: ge...@linux-m68k.org
Date: Mon, 04 Mar 2024 08:05:14 -
FAILED linux-next/m68k-allmodconfig/m68k-gcc8 Mon Mar 04, 06:35
htt
80 matches
Mail list logo
