linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "sashal@kernel.org" <sashal@kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"helgaas@kernel.org" <helgaas@kernel.org>
Subject: Re: [PATCH] PCI/VMD: Fix config addressing with bus offsets
Date: Mon, 10 Jun 2019 15:34:05 +0000	[thread overview]
Message-ID: <dbd8bf0da7fb6652d2393b2efc1f182f3d965c53.camel@intel.com> (raw)
In-Reply-To: <20190610151839.EC55620862@mail.kernel.org>

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

On Mon, 2019-06-10 at 15:18 +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 2a5a9c9a20f9 PCI: vmd: Add offset to bus numbers if necessary.
> 
> The bot has tested the following trees: v5.1.7, v4.19.48.
> 
> v5.1.7: Build OK!
> v4.19.48: Failed to apply! Possible dependencies:
>     0294951030eb ("PCI/VMD: Configure MPS settings before adding devices")
> 
> 
> How should we proceed with this patch?
> 
> --
> Thanks,
> Sasha

Thanks Sasha-bot,

I'll resend for kernels without 0294951030eb

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3278 bytes --]

  parent reply	other threads:[~2019-06-10 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 20:00 [PATCH] PCI/VMD: Fix config addressing with bus offsets Jon Derrick
     [not found] ` <20190610151839.EC55620862@mail.kernel.org>
2019-06-10 15:34   ` Derrick, Jonathan [this message]
2019-06-11 21:15 Jon Derrick
2019-06-21 14:28 ` Lorenzo Pieralisi
2019-06-24 18:12   ` Derrick, Jonathan
2019-07-22 16:02   ` Derrick, Jonathan
2019-07-23  9:32     ` Lorenzo Pieralisi
2019-07-23 15:12       ` Derrick, Jonathan
2019-07-24 11:11         ` Lorenzo Pieralisi
2019-07-24 17:47           ` Derrick, Jonathan

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=dbd8bf0da7fb6652d2393b2efc1f182f3d965c53.camel@intel.com \
    --to=jonathan.derrick@intel.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).