public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-mips@vger.kernel.org,
	tsbogend@alpha.franken.de, john@phrozen.org,
	lorenzo.pieralisi@arm.com, bhelgaas@google.com, arnd@arndb.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] PCI: let 'pcibios_root_bridge_prepare()' access to 'bridge->windows'
Date: Wed, 1 Dec 2021 14:27:09 -0600	[thread overview]
Message-ID: <20211201202709.GA2839013@bhelgaas> (raw)
In-Reply-To: <20211115070809.15529-2-sergio.paracuellos@gmail.com>

On Mon, Nov 15, 2021 at 08:08:05AM +0100, Sergio Paracuellos wrote:
> When function 'pci_register_host_bridge()' is called, 'bridge->windows' are
> already available. However this windows are being moved temporarily from
> there. To let 'pcibios_root_bridge_prepare()' to have access to this windows
> move this windows movement after call this function. This is interesting for
> MIPS ralink mt7621 platform to be able to properly set I/O coherence units
> with this information and avoid custom MIPs code in generic PCIe controller
> drivers.

Oops, forgot to mention:

s/this windows/these windows/
s/MIPs/MIPS/

You can drop the single quote around function names, too; the "()" is
enough of a hint.

And s/PCI: let/PCI: Let/ in the subject.

  parent reply	other threads:[~2021-12-01 20:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  7:08 [PATCH 0/5] PCI: mt7621: remove specific MIPS code from driver Sergio Paracuellos
2021-11-15  7:08 ` [PATCH 1/5] PCI: let 'pcibios_root_bridge_prepare()' access to 'bridge->windows' Sergio Paracuellos
2021-11-19 23:20   ` Bjorn Helgaas
2021-12-01 20:24     ` Bjorn Helgaas
2021-12-01 20:50       ` Arnd Bergmann
2021-12-01 20:56       ` Sergio Paracuellos
2021-12-01 21:12         ` Bjorn Helgaas
2021-12-01 20:27   ` Bjorn Helgaas [this message]
2021-11-15  7:08 ` [PATCH 2/5] MIPS: ralink: implement 'pcibios_root_bridge_prepare()' Sergio Paracuellos
2021-11-15  7:08 ` [PATCH 3/5] PCI: mt7621: avoid custom MIPS code in driver code Sergio Paracuellos
2021-12-01 18:16   ` Bjorn Helgaas
2021-12-01 19:25     ` Sergio Paracuellos
2021-11-15  7:08 ` [PATCH 4/5] PCI: mt7621: Add missing 'MODULE_LICENSE()' definition Sergio Paracuellos
2021-11-15 12:44   ` Krzysztof Wilczyński
2021-11-15 13:00     ` Arnd Bergmann
2021-11-15 13:51       ` Sergio Paracuellos
2021-11-15 13:55         ` Arnd Bergmann
2021-11-15 21:50       ` Krzysztof Wilczyński
2021-11-15 21:52   ` Krzysztof Wilczyński
2021-11-15  7:08 ` [PATCH 5/5] PCI: mt7621: Kconfig: completely enable driver for 'COMPILE_TEST' Sergio Paracuellos
2021-12-01 20:12   ` Bjorn Helgaas
2021-12-01 20:33     ` Sergio Paracuellos
2021-11-17 12:41 ` [PATCH 0/5] PCI: mt7621: remove specific MIPS code from driver Thomas Bogendoerfer
2021-11-17 12:48   ` Sergio Paracuellos

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=20211201202709.GA2839013@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=sergio.paracuellos@gmail.com \
    --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