Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Lukas Wunner <lukas@wunner.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] PCI/hotplug: Don't enable HPIE in poll mode
Date: Mon, 24 Mar 2025 11:41:26 -0500	[thread overview]
Message-ID: <20250324164126.GA1252202@bhelgaas> (raw)
In-Reply-To: <005837ad-e7dd-85c8-b0d3-ce5aa0257354@linux.intel.com>

On Mon, Mar 24, 2025 at 01:00:33PM +0200, Ilpo Järvinen wrote:
> On Fri, 21 Mar 2025, Bjorn Helgaas wrote:
> 
> > On Fri, Mar 21, 2025 at 07:07:47PM +0100, Lukas Wunner wrote:
> > > On Fri, Mar 21, 2025 at 12:09:19PM -0500, Bjorn Helgaas wrote:
> > > ...

> > > >   - It's annoying that pcie_enable_interrupt() and
> > > >     pcie_disable_interrupt() are global symbols, a consequence of
> > > >     pciehp being split across five files instead of being one, which
> > > >     is also a nuisance for code browsing.
> ...

> > > The only reason I've refrained from making major adjustments to this
> > > structure in the past was that it would make "git blame" a little more
> > > difficult and applying fixes to stable kernels would also become somewhat
> > > more painful as it would require backporting.
> > 
> > Yeah, that's the main reason I haven't tried to do anything either.
> > On the other hand, the browsing nuisance is an everyday thing forever
> > if we leave it as-is.
> 
> I get half mad every time I need to browse code under hotplug/. I even 
> started doing:
> 
>   cat ./pciehp*.[hc] | less -S 
> 
> ...to workaround the constant need to jump between those files. I 
> certainly would like to see the split gone especially between ctrl and 
> hpc.

I would definitely take patches to consolidate pciehp and maybe
acpiphp.

The other drivers are annoying, too, but I'm not sure it's worth the
trouble since they're rarely used and updated.

> Can't git blame be given -M -C to deal with this? Or are those truly lines 
> that were introduced by the consolidation commit?

I'm so git-illiterate that I habitually just search "git log -p".  
"git blame -M -C ..." would probably be much more effective.

Bjorn

      reply	other threads:[~2025-03-24 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 16:21 [PATCH v2 1/1] PCI/hotplug: Don't enable HPIE in poll mode Ilpo Järvinen
2025-03-21 17:09 ` Bjorn Helgaas
2025-03-21 18:07   ` Lukas Wunner
2025-03-21 20:51     ` Bjorn Helgaas
2025-03-24 11:00       ` Ilpo Järvinen
2025-03-24 16:41         ` Bjorn Helgaas [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=20250324164126.GA1252202@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.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