From: Nathan Chancellor <nathan@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.10 000/263] 6.10.5-rc1 review
Date: Fri, 16 Aug 2024 15:13:08 -0700 [thread overview]
Message-ID: <20240816221308.GA3360409@thelio-3990X> (raw)
In-Reply-To: <b27c5434-f1b1-4697-985b-91bb3e9a22df@roeck-us.net>
On Fri, Aug 16, 2024 at 07:43:31AM -0700, Guenter Roeck wrote:
> On 8/16/24 01:38, Greg Kroah-Hartman wrote:
> > Odd that other allmodconfig builds passed :(
> >
>
> Yes, that is odd. Maybe they all build with clang nowadays ?
I doubt that is the factor because our CI sees it and we obviously only
use clang:
https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs/10424364978
Cheers,
Nathan
next prev parent reply other threads:[~2024-08-16 22:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 16:00 Greg Kroah-Hartman
2024-08-12 20:54 ` Pavel Machek
2024-08-13 7:09 ` Naresh Kamboju
2024-08-13 11:32 ` Peter Schneider
2024-08-13 12:23 ` Mark Brown
2024-08-13 16:16 ` Markus Reichelt
2024-08-13 17:33 ` Florian Fainelli
2024-08-13 18:41 ` Jon Hunter
2024-08-13 19:34 ` Ron Economos
2024-08-15 14:21 ` Guenter Roeck
2024-08-16 8:38 ` Greg Kroah-Hartman
2024-08-16 8:42 ` Greg Kroah-Hartman
2024-08-16 14:43 ` Guenter Roeck
2024-08-16 22:13 ` Nathan Chancellor [this message]
2024-08-12 16:48 Ronald Warsow
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=20240816221308.GA3360409@thelio-3990X \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.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=linux@roeck-us.net \
--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®