From: Ingo Molnar <mingo@kernel.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Paul Menzel <pmenzel@molgen.mpg.de>,
x86@kernel.org
Subject: Re: [tip: core/urgent] compiler.h: Avoid the usage of __typeof_unqual__() when __GENKSYMS__ is defined
Date: Sun, 13 Apr 2025 21:20:00 +0200 [thread overview]
Message-ID: <Z_wOYOrVJJkUUUF9@gmail.com> (raw)
In-Reply-To: <CAFULd4b2afcu5PnxhqwwepwWMSA7mvYNyPnMtkCjjT84VG8VXA@mail.gmail.com>
* Uros Bizjak <ubizjak@gmail.com> wrote:
> > > If this commit is removed, [...]
> >
> > I did not remove commit ac053946f5c4, it's already upstream. Nor
> > did I advocate for it to be reverted - I'd like it to be fixed. So
> > you are barking up the wrong tree.
>
> If the intention is to pass my proposed workaround via Andrew's tree,
> then I'm happy to bark up the wrong tree, but from the referred
> message trail, I didn't get the clear decision about the patch, and
> neither am sure which patch "brown paper bag bug" refers to.
It's up to akpm (he merged your original patch that regressed), but I
think scripts/genksyms/ should be fixed instead of worked around -
which is why I zapped the workaround.
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-13 19:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 10:24 [PATCH] compiler.h: Avoid the usage of __typeof_unqual__() when __GENKSYMS__ is defined Uros Bizjak
2025-04-04 11:20 ` Paul Menzel
2025-04-04 12:55 ` Masahiro Yamada
2025-04-04 13:11 ` Uros Bizjak
2025-04-04 14:06 ` Masahiro Yamada
2025-04-04 14:37 ` Uros Bizjak
2025-04-04 19:13 ` Masahiro Yamada
2025-04-06 15:36 ` Uros Bizjak
2025-04-09 15:28 ` Borislav Petkov
2025-04-09 15:32 ` Uros Bizjak
2025-04-09 15:38 ` Borislav Petkov
2025-04-09 18:22 ` Uros Bizjak
2025-04-13 21:18 ` Uros Bizjak
2025-04-10 10:58 ` [tip: core/urgent] " tip-bot2 for Uros Bizjak
2025-04-11 21:08 ` Borislav Petkov
2025-04-12 8:20 ` Uros Bizjak
2025-04-12 8:55 ` Ingo Molnar
2025-04-13 8:27 ` Uros Bizjak
2025-04-13 8:55 ` Ingo Molnar
2025-04-13 11:05 ` Uros Bizjak
2025-04-13 18:56 ` Ingo Molnar
2025-04-13 19:14 ` Uros Bizjak
2025-04-13 19:20 ` Ingo Molnar [this message]
2025-04-13 19:28 ` Uros Bizjak
2025-04-13 19:43 ` Ingo Molnar
2025-04-15 1:20 ` Andrew Morton
2025-04-15 6:16 ` Uros Bizjak
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=Z_wOYOrVJJkUUUF9@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.