linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Sep 12 (bcachefs, objtool)
Date: Tue, 12 Sep 2023 16:36:55 -0700	[thread overview]
Message-ID: <d60dac60-1e38-4a8c-98ad-a769ab1dfccd@infradead.org> (raw)
In-Reply-To: <20230912152645.0868a96a@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 639 bytes --]



On 9/11/23 22:26, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20230911:
> 
> New tree: bcachefs
> 
> The bcachefs tree gained a semantic conflict against Linus' tree for
> which I applied a patch.
> 
> The wireless-next tree gaind a conflict against the wireless tree.
> 
> Non-merge commits (relative to Linus' tree): 4095
>  1552 files changed, 346893 insertions(+), 22945 deletions(-)
> 
> ----------------------------------------------------------------------------

on x86_64:

vmlinux.o: warning: objtool: bch2_dev_buckets_reserved.part.0() is missing an ELF size annotation


Full randconfig file is attached.

-- 
~Randy

[-- Attachment #2: config-r6878.gz --]
[-- Type: application/gzip, Size: 44641 bytes --]

  parent reply	other threads:[~2023-09-12 23:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  5:26 linux-next: Tree for Sep 12 Stephen Rothwell
2023-09-12 22:28 ` linux-next: Tree for Sep 12 (drivers/clk/imx/clk-imx8-acm.o) Randy Dunlap
2023-09-21  9:39   ` Abel Vesa
2023-09-12 22:50 ` linux-next: Tree for Sep 12 [drivers/pinctrl/nuvoton/pinctrl-npcm8xx.ko] Randy Dunlap
2023-09-12 23:36 ` Randy Dunlap [this message]
2023-09-13 21:08   ` linux-next: Tree for Sep 12 (bcachefs, objtool) Josh Poimboeuf
2023-09-13 21:39     ` Randy Dunlap
2023-09-13 23:06     ` Kent Overstreet
2023-09-14 13:41       ` Josh Poimboeuf
2023-09-14  1:01     ` Kees Cook
2023-09-14 13:51       ` Josh Poimboeuf
2023-09-14 16:51         ` Kees Cook
2023-09-14 19:15       ` Kent Overstreet
2023-09-14  1:17 ` linux-next: Tree for Sep 12 (bcachefs) Kees Cook
2023-09-14 19:38   ` Kent Overstreet
2023-09-14 20:13     ` Gustavo A. R. Silva
2023-09-15  0:20     ` Kees Cook
2023-09-19 21:23       ` Kent Overstreet
2023-09-20 15:21         ` Kees Cook

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=d60dac60-1e38-4a8c-98ad-a769ab1dfccd@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=jpoimboe@kernel.org \
    --cc=kent.overstreet@linux.dev \
    --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).