From: Guenter Roeck <linux@roeck-us.net>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org
Subject: Re: [PATCH 5.10 000/191] 5.10.201-rc1 review
Date: Fri, 17 Nov 2023 07:15:10 -0800 [thread overview]
Message-ID: <826b241f-3d93-4585-bd22-90cff75f7bb0@roeck-us.net> (raw)
In-Reply-To: <ZVbIoqXjfn7V1NtT@codewreck.org>
Hi,
On 11/16/23 17:57, Dominique Martinet wrote:
> Guenter Roeck wrote on Thu, Nov 16, 2023 at 05:13:39PM -0800:
>> Failed builds:
>> arm:allmodconfig
>> arm64:allmodconfig
>> i386:tools/perf
>> x86_64:tools/perf
>
>> This is with v5.10.200-192-g550b7e1fee20. I am a bit puzzled why others
>> don't seem to see those problems.
>
> The perf problem was reported by Florian Fainelli, but my current test
> build does not include userspace tools as we're not shipping them (and
> would rely on $distro packages when I need perf as a user rather than
> building it).
>
> Likewise, it looks like neither Linaro nor me build the qcom driver...
> I'm building kernels that have been trimmed down for our boards (with
> that exact config we're shipping and providing for our customers), and
> arm* drivers are especially fractured so it's a bit misleading to see
> "arm64 pass", that's just the tip of the actual setup tested.
>
>
> (Anyway, the main reason for me is mostly that $job is a small company
> that cannot afford extensive upstream testing, so I just don't have the
> time to do extended tests -- for the same reason we're only supporting
> the 5.10 tree so I'm focusing my limited time on just this branch, even
> if I'd love to do more.
> I'm just taking the stance that some test is better than no test and
> report back things we'd need to test before shipping customers a few
> weeks later anyway -- thank you for covering more!)
>
Just to clarify, I wasn't assuming or expecting that _everyone_ would report
those errors. I was just puzzled that I had not seen _any_ reports, especially
since arm:allmodconfig and arm64:allmodconfig both failed to build for me
(and I had somehow missed Florian's perf report).
Thanks,
Guenter
next prev parent reply other threads:[~2023-11-17 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 20:44 Greg Kroah-Hartman
2023-11-15 23:09 ` Florian Fainelli
2023-11-16 7:21 ` Dominique Martinet
2023-11-16 18:18 ` Naresh Kamboju
2023-11-17 1:13 ` Guenter Roeck
2023-11-17 1:57 ` Dominique Martinet
2023-11-17 15:15 ` Guenter Roeck [this message]
2023-11-17 7:41 ` Naresh Kamboju
2023-11-17 14:58 ` Guenter Roeck
2023-11-17 17:06 ` Florian Fainelli
2023-11-20 10:05 ` Greg Kroah-Hartman
2023-11-20 18:17 ` Guenter Roeck
2023-11-20 19:01 ` Holger Hoffstätte
2023-11-17 1:25 ` Guenter Roeck
2023-11-17 17:01 ` Pavel Machek
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=826b241f-3d93-4585-bd22-90cff75f7bb0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=asmadeus@codewreck.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®