Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Mateusz Jończyk" <mat.jonczyk@o2.pl>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Arnd Bergmann" <arnd@arndb.de>, "Baoquan He" <bhe@redhat.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] MIPS: pci-legacy: Override pci_address_to_pio
Date: Tue, 14 Jan 2025 18:51:02 +0000	[thread overview]
Message-ID: <28d6ed91-a5de-4a0d-8e76-9e79375a9db3@app.fastmail.com> (raw)
In-Reply-To: <6946ae6b-814c-4916-9428-e823c83aed3d@o2.pl>



在2025年1月14日一月 下午6:42,Mateusz Jończyk写道:
[...]
>
> Hello,
>
> Thank you for this patch, I'm testing it right now.
>
> Shouldn't this be #ifndef-ed CONFIG_MACH_LOONGSON64 and perhaps 
> CONFIG_RALINK?

Hi Mateusz,

Those platforms are not using PCI_DRIVERS_LEGACY, so won't be affected
by this patch.

PCI_DRIVERS_GENERIC systems are handling logic_pio properly, so no need
for this workaround.

Thanks
>
> Loongson64 explicitly calls logic_pio_register_range(), so seems not to 
> need this. Ralink also
> defined PCI_IOBASE a long time ago.
>
> Greetings,
>
> Mateusz

-- 
- Jiaxun

  reply	other threads:[~2025-01-14 18:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 18:11 [PATCH] MIPS: pci-legacy: Override pci_address_to_pio Jiaxun Yang
2025-01-14 18:42 ` Mateusz Jończyk
2025-01-14 18:51   ` Jiaxun Yang [this message]
2025-01-19 11:42   ` Mateusz Jończyk
2025-01-14 18:46 ` Greg KH
2025-01-14 18:55   ` Jiaxun Yang
2025-01-14 19:03 ` Arnd Bergmann
2025-01-14 19:20   ` Jiaxun Yang
2025-01-15  7:38     ` Arnd Bergmann
2025-01-15  8:57       ` Maciej W. Rozycki
2025-01-15  9:26       ` Jiaxun Yang
2025-01-20 19:41 ` Thomas Bogendoerfer

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=28d6ed91-a5de-4a0d-8e76-9e79375a9db3@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mat.jonczyk@o2.pl \
    --cc=stable@vger.kernel.org \
    --cc=tsbogend@alpha.franken.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