public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yury Norov <yury.norov@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Bitmap patches for v6.0-rc1
Date: Mon, 08 Aug 2022 16:10:01 +1000	[thread overview]
Message-ID: <874jyn9sg6.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CAHk-=whsgbpbVC_+V-dxuPbQCPV1eFQG00TrQvJcjYAXVHdswA@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Fri, Aug 5, 2022 at 11:11 PM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> This pull request has a conflict with the random tree in some powerpc
>> code.
>
> I noticed.

Thanks. Your resolution looks fine and builds for me.

> And I tried to do a cross-compile, but with my update to F36 the
> powerpc64 cross-tools seems to be very broken. I get lots of strange
> errors like
>
>     Cannot find symbol for section 11: .text.kgdb_arch_pc.
>
> and I have no idea why.  I used to have a working cross-build
> environment at one point, but now it just gives me lots of errors.

If you just build defconfig rather than allmodconfig it should build
cleanly.

That's the "recordmcount" issue that's been going on for the last ~year.
It's some bad interaction between recordmcount and weak symbols and
newer versions of binutils.

Naveen made an attempt to fix it, but the discussion with Steve fizzled
out inconclusively.

AIUI objtool doesn't have the same problem so hopefully we can switch to
objtool soon and avoid the issue.

cheers

  reply	other threads:[~2022-08-08  6:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  2:29 [GIT PULL] Bitmap patches for v6.0-rc1 Yury Norov
2022-08-06  6:11 ` Michael Ellerman
2022-08-08  0:49   ` Linus Torvalds
2022-08-08  6:10     ` Michael Ellerman [this message]
2022-08-08  0:12 ` Linus Torvalds
2022-08-12  6:15   ` Yury Norov
2022-08-08  0:48 ` pr-tracker-bot
2022-08-08  0:57   ` Linus Torvalds
2022-08-08  4:21     ` Stephen Rothwell

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=874jyn9sg6.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yury.norov@gmail.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