From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Sep 20 (objtool: intel_idle)
Date: Wed, 20 Sep 2023 08:55:41 -0700 [thread overview]
Message-ID: <794a4609-af03-4f22-a3a0-9d8194d2e5fe@infradead.org> (raw)
In-Reply-To: <20230920133714.351f83f9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
On 9/19/23 20:37, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230919:
>
> The mm tree lost its boot warning.
>
> The drm-misc tree gained a conflict against Linus' tree.
>
> Non-merge commits (relative to Linus' tree): 6006
> 3996 files changed, 459968 insertions(+), 111742 deletions(-)
>
> ----------------------------------------------------------------------------
>
on x86_64:
vmlinux.o: warning: objtool: intel_idle_ibrs+0x9: call to sched_smt_active() leaves .noinstr.text section
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r7534.gz --]
[-- Type: application/gzip, Size: 31007 bytes --]
prev parent reply other threads:[~2023-09-20 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 3:37 linux-next: Tree for Sep 20 Stephen Rothwell
2023-09-20 5:32 ` linux-next: Tree for Sep 20 (drivers/net/ethernet/intel/idpf/idpf_txrx.o) Randy Dunlap
2023-09-20 15:52 ` linux-next: Tree for Sep 20 (ppc32: ADB_CUDA Kconfig warning) Randy Dunlap
2023-09-22 0:10 ` Michael Ellerman
2023-09-22 4:51 ` Randy Dunlap
2023-10-07 17:32 ` Randy Dunlap
2023-09-20 15:55 ` Randy Dunlap [this message]
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=794a4609-af03-4f22-a3a0-9d8194d2e5fe@infradead.org \
--to=rdunlap@infradead.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).