mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@kernel.org>
To: "Greg Ungerer" <gerg@linux-m68k.org>, "Daniel Palmer" <daniel@0x0f.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
	christoph.plattner@gmx.at, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] m68k: nommu: Fix behaviour of io macros on non-CF
Date: Fri, 17 Apr 2026 18:36:20 +0200	[thread overview]
Message-ID: <a93c448f-32fd-48aa-b4be-124278ca0a02@app.fastmail.com> (raw)
In-Reply-To: <e1871e42-6d1f-4753-a830-9c7dda99f75b@linux-m68k.org>

On Fri, Apr 17, 2026, at 16:11, Greg Ungerer wrote:
>
> I have some changes I am testing to do a blanket change of the arch 
> specific code to use newly create IO access functions too. Simple
> enough (like your example patch) but of course it does cause of
> bit of churn.

Sounds good, yes. The hardest part I think is going to be the
shared drivers that currently rely on the flipped meaning of
readl()/ioread32be() like the regmap. These may need to get an
atomic patch that flips around the users at the same time
as removing the flipped readl().

     Arnd

      reply	other threads:[~2026-04-17 16:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04  2:46 Daniel Palmer
2026-04-13 16:52 ` Arnd Bergmann
2026-04-14  7:14   ` Geert Uytterhoeven
2026-04-14 12:18 ` Greg Ungerer
2026-04-14 12:55   ` Daniel Palmer
2026-04-14 13:24     ` Arnd Bergmann
2026-04-15 13:52       ` Greg Ungerer
2026-04-15 14:54         ` Arnd Bergmann
2026-04-17 14:11           ` Greg Ungerer
2026-04-17 16:36             ` Arnd Bergmann [this message]

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=a93c448f-32fd-48aa-b4be-124278ca0a02@app.fastmail.com \
    --to=arnd@kernel.org \
    --cc=christoph.plattner@gmx.at \
    --cc=daniel@0x0f.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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

all inboxes | Powered by JetHome®