linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] PCI: Handle HAS_IOPORT dependencies
Date: Mon, 03 Jul 2023 20:02:40 +0200	[thread overview]
Message-ID: <9778740b9e07b9bb92b86bf13b8f6329485ae418.camel@linux.ibm.com> (raw)
In-Reply-To: <20230703174233.GA529479@bhelgaas>

On Mon, 2023-07-03 at 12:42 -0500, Bjorn Helgaas wrote:
> On Mon, Jul 03, 2023 at 03:52:53PM +0200, Niklas Schnelle wrote:
> > Hi Bjorn,
> > 
> > This is a follow up to my ongoing effort of making the inb()/outb() and
> > similar I/O port accessors compile-time optional. Previously I sent this as
> > a complete treewide series titled "treewide: Remove I/O port accessors for
> > HAS_IOPORT=n" with the latest being its 5th version[0]. Now about half of
> > the per-subsystem patches have been merged so I'm changing over to stand
> > alone subsystem patches. These series are stand alone and should be merged
> > via the relevant tree such that with all subsystems complete we can follow
> > this up with the last patch[1] that will make the I/O port accessors
> > compile-time optional.
> 
> Is the merge plan for each subsystem to merge this separately?  I
> acked these so they could be merged along with all the tree-wide
> changes.

Hi Björn,

Yeah this went back and forth a little, sorry about that. With the
Kconfig introduction of HAS_IOPORT merged about half of the original
patches have been merged via subsystem maintainers or are at least
sitting in linux-next already.  Arnd was anticipating that he'll pick
up some left overs but at the moment the simplest is for subsystems to
pick the patches up themselves ideally and if small enough for v6.5
still.

Thanks,
Niklas

> 
> > As for compile-time vs runtime see Linus' reply to my first attempt[2].
> > 
> > Other than rebasing on current master there are no changes to these
> > two patches for the PCI subsystem.
> > 
> > Thanks,
> > Niklas
> > 
> > [0] https://lore.kernel.org/all/20230516110038.2413224-1-schnelle@linux.ibm.com/
> > [1] https://lore.kernel.org/all/20230516110038.2413224-42-schnelle@linux.ibm.com/
> > [2] https://lore.kernel.org/lkml/CAHk-=wg80je=K7madF4e7WrRNp37e3qh6y10Svhdc7O8SZ_-8g@mail.gmail.com/
> > 
> > Niklas Schnelle (2):
> >   PCI: Make quirk using inw() depend on HAS_IOPORT
> >   PCI/sysfs: Make I/O resource depend on HAS_IOPORT
> > 
> >  drivers/pci/pci-sysfs.c | 4 ++++
> >  drivers/pci/quirks.c    | 2 ++
> >  2 files changed, 6 insertions(+)
> > 
> > 
> > base-commit: a901a3568fd26ca9c4a82d8bc5ed5b3ed844d451
> > -- 
> > 2.39.2
> > 


  reply	other threads:[~2023-07-03 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 13:52 [PATCH v6 0/2] PCI: Handle HAS_IOPORT dependencies Niklas Schnelle
2023-07-03 13:52 ` [PATCH v6 1/2] PCI: Make quirk using inw() depend on HAS_IOPORT Niklas Schnelle
2023-07-03 13:52 ` [PATCH v6 2/2] PCI/sysfs: Make I/O resource " Niklas Schnelle
2023-07-03 17:42 ` [PATCH v6 0/2] PCI: Handle HAS_IOPORT dependencies Bjorn Helgaas
2023-07-03 18:02   ` Niklas Schnelle [this message]
2023-07-18 21:12     ` Bjorn Helgaas
2023-07-18 21:58       ` Bjorn Helgaas

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=9778740b9e07b9bb92b86bf13b8f6329485ae418.camel@linux.ibm.com \
    --to=schnelle@linux.ibm.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).