Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	Arnd Bergmann <arnd@kernel.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: fix PCI_IOBASE definition
Date: Wed, 19 Mar 2025 11:38:09 +0100	[thread overview]
Message-ID: <Z9qekYr_pYwI7dpf@alpha.franken.de> (raw)
In-Reply-To: <9066761b-e222-4855-b97f-17c36b1440e1@app.fastmail.com>

On Wed, Mar 19, 2025 at 11:07:46AM +0100, Arnd Bergmann wrote:
> On Wed, Mar 19, 2025, at 10:43, Sergio Paracuellos wrote:
> > Hi Arnd,
> >
> > On Tue, Mar 18, 2025 at 10:44 PM Arnd Bergmann <arnd@kernel.org> wrote:
> >
> > It looks like nothing got broken regarding PCI enumeration on boot
> > trace. I don't have real PCI cards with IO resources to test, but FWIW
> > the enumeration is the same as from my stable 6.12 kernel boot.
> >
> 
> Thanks a lot for testing!

are you taking it together with your other io,h cleanups ?

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2025-03-19 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 21:43 [PATCH] mips: fix PCI_IOBASE definition Arnd Bergmann
2025-03-19  9:43 ` Sergio Paracuellos
2025-03-19 10:07   ` Arnd Bergmann
2025-03-19 10:38     ` Thomas Bogendoerfer [this message]
2025-03-19 10:44       ` Arnd Bergmann

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=Z9qekYr_pYwI7dpf@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=sergio.paracuellos@gmail.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