All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriele Paoloni <gabriele.paoloni@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
	"helgaas@kernel.org" <helgaas@kernel.org>,
	Linuxarm <linuxarm@huawei.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"lukas@wunner.de" <lukas@wunner.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>
Subject: RE: [PATCH 2/2] PCI/portdrv: allocate MSI/MSIx vector for DPC RP service
Date: Tue, 16 May 2017 15:27:40 +0000	[thread overview]
Message-ID: <EE11001F9E5DDD47B7634E2F8A612F2E40A2E479@FRAEML521-MBX.china.huawei.com> (raw)
In-Reply-To: <20170516121112.GA16209@infradead.org>

Hi Christoph

> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@infradead.org]
> Sent: 16 May 2017 13:11
> To: Gabriele Paoloni
> Cc: bhelgaas@google.com; helgaas@kernel.org; Linuxarm; linux-
> pci@vger.kernel.org; lukas@wunner.de; linux-kernel@vger.kernel.org;
> mika.westerberg@linux.intel.com
> Subject: Re: [PATCH 2/2] PCI/portdrv: allocate MSI/MSIx vector for DPC
> RP service
> 
> > +		 * pci_irq_vector() below is able to handle entry
> differently
> > +		 * depending on MSI vs MSI-x case
> > +		 *

Ok I'll remove this in V2

> 
> No need to mention that for every users.
> 
> Except for that this looks fine:
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>

Many thanks
Gab

WARNING: multiple messages have this Message-ID (diff)
From: Gabriele Paoloni <gabriele.paoloni@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
	"helgaas@kernel.org" <helgaas@kernel.org>,
	Linuxarm <linuxarm@huawei.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"lukas@wunner.de" <lukas@wunner.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>
Subject: RE: [PATCH 2/2] PCI/portdrv: allocate MSI/MSIx vector for DPC RP service
Date: Tue, 16 May 2017 15:27:40 +0000	[thread overview]
Message-ID: <EE11001F9E5DDD47B7634E2F8A612F2E40A2E479@FRAEML521-MBX.china.huawei.com> (raw)
In-Reply-To: <20170516121112.GA16209@infradead.org>

Hi Christoph

> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@infradead.org]
> Sent: 16 May 2017 13:11
> To: Gabriele Paoloni
> Cc: bhelgaas@google.com; helgaas@kernel.org; Linuxarm; linux-
> pci@vger.kernel.org; lukas@wunner.de; linux-kernel@vger.kernel.org;
> mika.westerberg@linux.intel.com
> Subject: Re: [PATCH 2/2] PCI/portdrv: allocate MSI/MSIx vector for DPC
> RP service
>=20
> > +		 * pci_irq_vector() below is able to handle entry
> differently
> > +		 * depending on MSI vs MSI-x case
> > +		 *

Ok I'll remove this in V2

>=20
> No need to mention that for every users.
>=20
> Except for that this looks fine:
>=20
> Reviewed-by: Christoph Hellwig <hch@lst.de>

Many thanks
Gab

  reply	other threads:[~2017-05-16 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 10:25 [PATCH 0/2] PCI/portdrv: add MSI support for PCIe port services and DPC IRQ support Gabriele Paoloni
2017-05-16 10:25 ` [PATCH 1/2] PCI/portdrv: add support for different MSI interrupts for PCIe port services Gabriele Paoloni
2017-05-16 12:06   ` Christoph Hellwig
2017-05-16 15:02     ` Gabriele Paoloni
2017-05-16 10:25 ` [PATCH 2/2] PCI/portdrv: allocate MSI/MSIx vector for DPC RP service Gabriele Paoloni
2017-05-16 12:11   ` Christoph Hellwig
2017-05-16 15:27     ` Gabriele Paoloni [this message]
2017-05-16 15:27       ` Gabriele Paoloni

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=EE11001F9E5DDD47B7634E2F8A612F2E40A2E479@FRAEML521-MBX.china.huawei.com \
    --to=gabriele.paoloni@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=hch@infradead.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lukas@wunner.de \
    --cc=mika.westerberg@linux.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 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.