From: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
To: Daniel Palmer <daniel@thingy.jp>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev, kas@kernel.org, mingo@kernel.org,
seanjc@google.com, bp@alien8.de, linux-m68k@lists.linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: implement runtime consts
Date: Thu, 4 Dec 2025 10:57:55 +0100 [thread overview]
Message-ID: <aTFbI1RKsbEdR2Ph@yoseli-yocto.yoseli.org> (raw)
In-Reply-To: <CAFr9PXm_8Lyk5rPMWw+mAzu97RRfjLj8NLqz5K0Po4p9PM6FOw@mail.gmail.com>
On Wed, Dec 03, 2025 at 05:06:52PM +0900, Daniel Palmer wrote:
> Hi Geert,
>
> On Thu, 27 Nov 2025 at 19:22, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> >
> > Replacing the macros by static inline functions should fix that.
>
> Thanks. I've done that now. Any comments on the rest of this?
> I have a few things like implementing jump labels, a vDSO to get
> around the sys_get_thread_area() bottleneck to come after this.
Hi Daniel,
It would be great to have vDSO at least for sys_get_thread_area() ! I
implemented something, but if you already have it, please, submit a RFC
I will test on coldfire !
Thanks,
JM
> Cheers,
>
> Daniel
next prev parent reply other threads:[~2025-12-05 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 0:05 [PATCH] m68k: implement runtime consts Daniel Palmer
2025-11-27 1:59 ` kernel test robot
2025-11-27 10:13 ` Daniel Palmer
2025-11-27 10:22 ` Geert Uytterhoeven
2025-12-03 8:06 ` Daniel Palmer
2025-12-04 9:57 ` Jean-Michel Hautbois [this message]
2025-12-05 9:23 ` Daniel Palmer
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=aTFbI1RKsbEdR2Ph@yoseli-yocto.yoseli.org \
--to=jeanmichel.hautbois@yoseli.org \
--cc=bp@alien8.de \
--cc=daniel@thingy.jp \
--cc=geert@linux-m68k.org \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@google.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