mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sridhar Pitchai <Sridhar.Pitchai@microsoft.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Michael Kelley \(EOSG\)" <Michael.H.Kelley@microsoft.com>,
	Jake Oshins <jakeo@microsoft.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH v5] PCI: hv: Make sure the bus domain is really unique
Date: Sat, 31 Mar 2018 00:49:09 +0000	[thread overview]
Message-ID: <F31FD99A-2356-4659-BEC1-91CAE1920B90@microsoft.com> (raw)
In-Reply-To: <20180330212311.GB9322@bhelgaas-glaptop.roam.corp.google.com>

	>On 3/30/18, 2:23 PM, "Bjorn Helgaas" <helgaas@kernel.org> wrote:
	>   >On Fri, Mar 30, 2018 at 07:35:04PM +0000, Sridhar Pitchai wrote:
	>   >commit 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI
	>   >domain") need to be reverted. Also, we no longer need it as commit
	>   >4a1626dd233e ("netvsc: transparent VF management") remove the
	>   >need for it.
	>
	>Do you mean 0c195567a8f6 ("netvsc: transparent VF management")?
	>
	>I don't see a 4a1626dd233e commit in Linus' tree.
	>

That is right. sha should be 4a1626dd233e.

	>The connection between 0c195567a8f6 ("netvsc: transparent VF
	>management") and this Hyper-V domain ID issue is not clear to me at
	>all.  But obviously I'm not a networking or a Hyper-V person.
	>
	>A hint in the changelog about what that connection is would be nice.
	>
	>   >Revert commit 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI
	>   >domain") so we can reliably support multiple devices being assigned to
	>   >a guest.
	>   >
	>   >This revert should only be backported to kernels that contain commit
	>   >4a1626dd233e ("netvsc: transparent VF management").
	>   >
	>   >Fixes: 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI domain")
	>   >Signed-off-by: Sridhar Pitchai <sridhar.pitchai@microsoft.com>
	>   >Cc: stable@vger.kernel.org
	>
	>This backporting guidance is very confusing.
	>
	>4a9b0933bdfc ("PCI: hv: Use device serial number as PCI domain")
	>appeared in v4.11.
	>
	>0c195567a8f6 ("netvsc: transparent VF management") appeared in v4.14.
	>
	>The changelog and the "Fixes" tag both suggest that 4a9b0933bdfc was
	>flat-out buggy and should be reverted unconditionally.  That would
	>mean this patch should be applied to v4.11 and later stable kernels.
	>
	>But the changelog also says "only revert 4a9b0933bdfc if you have
	>0c195567a8f6".  That would mean this patch should only be applied to
	>v4.14 and later stable kernels.
	>
	>Which is it?  You can answer in this thread if you want, but Lorenzo
	>will ultimately be looking for a v6 patch with a corrected changelog.

It is the Case 1. We just need to revert 4a9b0933bdfc. I will remove the
reference to 0c195567a8f6 altogether in the commit message.

	>
	>I think Lorenzo is out this week, but I suspect he'll look at it next
	>week.
	>
	>Bjorn

I will send out the update patch version 6.

Thanks,
Sridhar Pitchai 

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

      reply	other threads:[~2018-03-31  0:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 17:34 Sridhar Pitchai
2018-03-30 19:35 ` Sridhar Pitchai
2018-03-30 21:23   ` Bjorn Helgaas
2018-03-31  0:49     ` Sridhar Pitchai [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=F31FD99A-2356-4659-BEC1-91CAE1920B90@microsoft.com \
    --to=sridhar.pitchai@microsoft.com \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=bhelgaas@google.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=helgaas@kernel.org \
    --cc=jakeo@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=sthemmin@microsoft.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

all inboxes | Powered by JetHome®