From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, tkjos@google.com
Cc: Elliot Berman <quic_eberman@quicinc.com>
Subject: Re: UM-Linux compilation on Android Common Kernels
Date: Thu, 1 Sep 2022 14:03:38 +0100 [thread overview]
Message-ID: <YxCtqsY55Lwaj34H@sirena.org.uk> (raw)
In-Reply-To: <CAHRSSEy20Zc80XufjYN4XjXbba6BTMHd_9kFaNOnhiuj9yEDsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Wed, Aug 31, 2022 at 11:21:28AM -0700, Todd Kjos via groups.io wrote:
> On Wed, Aug 17, 2022 at 11:05 AM Todd Kjos <tkjos@google.com> wrote:
> > On Wed, Aug 17, 2022 at 10:51 AM Elliot Berman <quic_eberman@quicinc.com> wrote:
> >> Qualcomm recently caught some build errors in UM-Linux on Android Common
> >> Kernel. Todd suggested that these errors might be catchable by 0day. Can
> > I think in this context, I meant "catchable by kernelci".
> >> UM-Linux compilation be enabled for Android Common Kernels?
> >> ARCH=um SUBARCH=x86_64
> > I support this, can we add this test for android kernels? (could limit to 5.10 an higher).
This is definitely technically doable, especially the build side, but
there'd be some work required to enable actually running the kernels and
tests on them. We discussed this at the weekly meeting today, the main
issue would be finding someone who has the time to do the actual
w.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-01 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 17:51 UM-Linux compilation on Android Common Kernels Elliot Berman
2022-08-17 18:05 ` Todd Kjos
2022-08-31 18:21 ` Todd Kjos
2022-09-01 13:03 ` Mark Brown [this message]
2022-09-01 15:44 ` Todd Kjos
2022-09-05 11:59 ` Mark Brown
2022-09-14 20:36 ` Todd Kjos
2022-09-15 16:23 ` Guillaume Tucker
2022-09-15 16:25 ` Todd Kjos
2022-10-13 15:55 ` Todd Kjos
[not found] ` <CAHRSSEyrJeru4YKoAFUo2Ai1dmxQAxRTJ1gnAuY1OmxohF=5Gw@mail.gmail.com>
[not found] ` <CAHRSSEztTzwRThMc1OfpP33r-V8=bNNP3fc_LD9_6eY9Ztj6sA@mail.gmail.com>
2023-07-13 7:08 ` Guillaume Tucker
2024-03-01 18:15 ` Todd Kjos
[not found] ` <16a0b25c-c550-351d-8f76-4a31c9f509ec@collabora.com>
2024-03-01 18:30 ` Todd Kjos
[not found] ` <4c840d3a-65d4-8df3-9ef7-a9bb24dccabf@collabora.com>
2024-03-01 18:37 ` Todd Kjos
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=YxCtqsY55Lwaj34H@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernelci@groups.io \
--cc=quic_eberman@quicinc.com \
--cc=tkjos@google.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