From: Dexuan Cui <decui@microsoft.com>
To: Sasha Levin <sashal@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Stephen Hemminger <sthemmin@microsoft.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] PCI: hv: Add hv_pci_remove_slots() when we unload the driver
Date: Mon, 11 Feb 2019 18:09:08 +0000 [thread overview]
Message-ID: <PU1P153MB0169377DB326432229381E95BF640@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20190211172608.E873D2229F@mail.kernel.org>
> From: Sasha Levin <sashal@kernel.org>
> Sent: Monday, February 11, 2019 9:26 AM
> To: Sasha Levin <sashal@kernel.org>; Dexuan Cui <decui@microsoft.com>;
> Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: linux-kernel@vger.kernel.org; stable@vger.kernel.org; Stephen Hemminger
> <sthemmin@microsoft.com>; stable@vger.kernel.org
> Subject: Re: [PATCH] PCI: hv: Add hv_pci_remove_slots() when we unload the
> driver
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: a15f2c08c708 PCI: hv: support reporting serial number as slot
> information.
>
> The bot has tested the following trees: v4.20.7, v4.19.20, v4.14.98.
>
> v4.20.7: Build OK!
> v4.19.20: Build OK!
> v4.14.98: Failed to apply! Possible dependencies:
> Unable to calculate
> How should we proceed with this patch?
> Sasha
In v4.14.y, the file name is drivers/pci/host/pci-hyperv.c rather than
drivers/pci/controller/pci-hyperv.c. After I changed the folder name in the patch,
I could "git am" it cleanly on v4.14.98.
Thanks,
-- Dexuan
parent reply other threads:[~2019-02-11 18:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190211172608.E873D2229F@mail.kernel.org>]
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=PU1P153MB0169377DB326432229381E95BF640@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM \
--to=decui@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).