Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,  LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] PCI: Unnecessary linesplit in __pci_setup_bridge()
Date: Mon, 19 May 2025 16:59:53 +0300 (EEST)	[thread overview]
Message-ID: <9dd35654-e6eb-a531-457c-93ddc5ff371d@linux.intel.com> (raw)
In-Reply-To: <20250516132016.GA2390647@rocinante>

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

On Fri, 16 May 2025, Krzysztof Wilczyński wrote:

> [...]
> > -	pci_info(bridge, "PCI bridge to %pR\n",
> > -		 &bus->busn_res);
> > +	pci_info(bridge, "PCI bridge to %pR\n", &bus->busn_res);
> 
> I don't know if there still exists such a thing as "trivial patches
> maintainer" any more, so I will pull this.
> 
> I gather, it must have bothered you a bit. That said, Ilpo... your
> expertise and time could have been spent differently. :)

It doesn't take long to do patches like this and I don't search for things 
like this intentionally nor focus on them. It's just that I do encounter 
these simple ones too while I'm spending my expertise differently :-). You 
can check my track record on discovering e.g. real concurrency issues 
recently so I hope you can give a bit slack on a few trivial patches here 
and there ;-).

-- 
 i.

  reply	other threads:[~2025-05-19 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 12:45 [PATCH 1/1] PCI: Unnecessary linesplit in __pci_setup_bridge() Ilpo Järvinen
2025-05-16 13:20 ` Krzysztof Wilczyński
2025-05-19 13:59   ` Ilpo Järvinen [this message]
2025-05-20 15:30     ` Krzysztof Wilczyński
2025-05-16 13:21 ` Krzysztof Wilczyński

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=9dd35654-e6eb-a531-457c-93ddc5ff371d@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --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