The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Rustam Adilov <adilov@disroot.org>,
	Birger Koblitz <mail@birger-koblitz.de>,
	Bert Vermeulen <bert@biot.com>, John Crispin <john@phrozen.org>,
	linux-kernel@vger.kernel.org
Cc: Rustam Adilov <adilov@disroot.org>,
	Carlo Szelinsky <github@szelinsky.de>,
	Markus Stockhausen <markus.stockhausen@gmx.de>
Subject: Re: [PATCH] irqchip/irq-realtek-rtl: change to __raw reads and writes
Date: Wed, 15 Jul 2026 09:10:12 +0200	[thread overview]
Message-ID: <874ii0pw2z.ffs@fw13> (raw)
In-Reply-To: <20260711082328.43535-1-adilov@disroot.org>

On Sat, Jul 11 2026 at 13:23, Rustam Adilov wrote:

> To make the interrupt driver operable with SWAP_IO_SPACE
> config enabled, replace all instances of readl/writel with
> their __raw variants. Otherwise readl/writel will do a byte
> swap which this driver does not intend to do.

Sorry, but this word salad does not qualify as a change log. See

  https://docs.kernel.org/process/maintainer-tip.html#changelog

First you want to explain what the context:

  When CONFIG_SWAP_IO_SPACE is enabled readl() and writel() imply a byte
  swap.

Then you want to explain why this is not correct for this
driver/hardware. Just saying 'does not intend to do' contains zero
information:

  This is incorrect for the RTL driver, because <Insert proper technical explanation>

Then you tell how you cure it:

  Fix this by converting the MMIO accesses to __raw_readl() and
  __raw_writel(), which do not byte swap the data.

Thanks,

        tglx

      reply	other threads:[~2026-07-15  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11  8:23 [PATCH] irqchip/irq-realtek-rtl: change to __raw reads and writes Rustam Adilov
2026-07-15  7:10 ` Thomas Gleixner [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=874ii0pw2z.ffs@fw13 \
    --to=tglx@kernel.org \
    --cc=adilov@disroot.org \
    --cc=bert@biot.com \
    --cc=github@szelinsky.de \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@birger-koblitz.de \
    --cc=markus.stockhausen@gmx.de \
    /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