All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Lukas Wunner" <lukas@wunner.de>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH RFC v2] platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe
Date: Thu, 14 Dec 2023 16:13:04 +0200	[thread overview]
Message-ID: <ZXsNcGnlTPwgQE-T@smile.fi.intel.com> (raw)
In-Reply-To: <eo7bnkdph6fwb74zn57r33a6unodkpagpk3dk5euz5cdc2mve4@557h3e3v5og7>

On Thu, Dec 14, 2023 at 12:55:36AM +0000, Shinichiro Kawasaki wrote:
> On Dec 13, 2023 / 16:05, Andy Shevchenko wrote:
> > On Tue, Dec 12, 2023 at 08:47:46PM +0900, Shin'ichiro Kawasaki wrote:

...

> > > +/* Cache BAR0 of P2SB device from function 0 ot 7 */
> > > +#define NR_P2SB_RES_CACHE 8
> > 
> > Here... (at least some better comment with TODO needs to be added,
> > and next patches can address that).
> > 
> > >  	struct resource *bar0 = &pdev->resource[0];
> > 
> > ...and here... (okay, not exactly here, but with the same idea,
> > to use pci_resource_n() macro)
> > 
> > > +	if (!PCI_FUNC(devfn_p2sb)) {
> > > +		slot_p2sb = PCI_SLOT(devfn_p2sb);
> > > +		for (fn = 1; fn < 8; fn++)
> > 
> > ...and here...
> > 
> > > +			p2sb_scan_and_cache(bus, PCI_DEVFN(slot_p2sb, fn));
> > > +	}
> > 
> > ...and so on I gave comments. Any reason why they left unaddressed?
> 
> Andy, thanks for the response, but I'm not sure about the comments you gave.
> I guess you responded to the RFC v1 patch but it somehow did not reach to me,
> probably. According to the lore archive, only Hans responded to the RFC v1 [1].
> If this guess is correct, could you resend your comments on the RFC v1?

Oh, my... It seems the message was never delivered and I haven't paid attention
on the bounces.

Give me time, I'll try to restore the review from my memory and will send
a new email.

> [1] https://lore.kernel.org/platform-driver-x86/20231201104759.949340-1-shinichiro.kawasaki@wdc.com/

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-12-14 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 11:47 [PATCH RFC v2] platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe Shin'ichiro Kawasaki
2023-12-13 14:05 ` Andy Shevchenko
2023-12-14  0:55   ` Shinichiro Kawasaki
2023-12-14 14:13     ` Andy Shevchenko [this message]
2023-12-13 19:41 ` Bjorn Helgaas
2023-12-15  7:34   ` Shinichiro Kawasaki
2023-12-14 16:38 ` Andy Shevchenko
2023-12-15  7:33   ` Shinichiro Kawasaki
2023-12-15 15:42     ` Andy Shevchenko
2023-12-15  7:52   ` Lukas Wunner
2023-12-15 15:37     ` Andy Shevchenko
2023-12-15 15:45       ` Lukas Wunner
2023-12-15 16:13         ` Andy Shevchenko

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=ZXsNcGnlTPwgQE-T@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.