linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Guenter Roeck <linux@roeck-us.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Huacai Chen <chenhuacai@kernel.org>
Subject: Re: Linux 6.6-rc1
Date: Tue, 12 Sep 2023 20:25:06 +0200	[thread overview]
Message-ID: <c8529a48-c104-2653-40c5-f2f6396f0dfb@gmx.de> (raw)
In-Reply-To: <CAHk-=wh+rYcuh0zp3b3qFuhwykXK1u1HcpRPCpeZ5EUnUKjJew@mail.gmail.com>

On 9/12/23 20:17, Linus Torvalds wrote:
> On Tue, 12 Sept 2023 at 11:00, Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> loongarch:
>>
>> INFO: trying to register non-static key.
>>
>> Caused by commit 0a6b58c5cd0d ("lockdep: fix static memory detection even
>> more"). No fix available as far as I know.
>
> Isn't this
>
>     https://lore.kernel.org/lkml/ZPl+Y2vRYUnWtTQc@ls3530/
>
> the fix? You even replied to that saying it's fixed.

Yes, this should be the fix.

> Or are there two different issues here?
>
> Or is it just that it's not queued up anywhere?

It's not queued up yet, AFAIK.
I just returned from vacation and will send a proper patch in a few moments.
Nevertheless, it would be good to get feedback from loongarch people too.

Helge

  reply	other threads:[~2023-09-12 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 23:53 Linux 6.6-rc1 Linus Torvalds
2023-09-11  2:38 ` linux-next: stats (Was: Linux 6.6-rc1) Stephen Rothwell
2023-09-11  9:02   ` Geert Uytterhoeven
2023-09-11  8:38 ` Build regressions/improvements in v6.6-rc1 Geert Uytterhoeven
2023-09-11 23:08   ` Randy Dunlap
2023-09-12  6:49     ` Geert Uytterhoeven
2023-09-12  7:33       ` Randy Dunlap
2023-09-12  6:39   ` Geert Uytterhoeven
2023-09-12 17:59 ` Linux 6.6-rc1 Guenter Roeck
2023-09-12 18:17   ` Linus Torvalds
2023-09-12 18:25     ` Helge Deller [this message]
2023-09-12 18:33     ` Guenter Roeck

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=c8529a48-c104-2653-40c5-f2f6396f0dfb@gmx.de \
    --to=deller@gmx.de \
    --cc=chenhuacai@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).