public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Tommi Airikka <tommi@airikka.net>, <linux-kernel@vger.kernel.org>,
	<xen-devel@lists.xenproject.org>, <david.vrabel@citrix.com>,
	<boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH] Fixes to Xen pcifront and pciback (v1)
Date: Mon, 15 Feb 2016 14:35:56 +0000	[thread overview]
Message-ID: <56C1E24C.5040704@citrix.com> (raw)
In-Reply-To: <1455225026-25792-1-git-send-email-konrad.wilk@oracle.com>

On 11/02/16 21:10, Konrad Rzeszutek Wilk wrote:
> Hey,
> 
> These are patches that were developed for the Debian bug
> 810379 which san Tommi had openned.
> 
> The issue around from the two XSA fixes - which introduced
> this regression.

Applied to for-linus-4.6, thanks.

I rewrote some of the commit messages for clarity.  Please only put
relevant information in them and for regression fixes, make sure it's
clear what functionality regressed.

e.g. #1 now reads:

    Commit 408fb0e5aa7fda0059db282ff58c3b2a4278baa0 (xen/pciback: Don't
    allow MSI-X ops if PCI_COMMAND_MEMORY is not set) prevented enabling
    MSI-X on passed-through virtual functions, because it checked the VF
    for PCI_COMMAND_MEMORY but this is not a valid bit for VFs.

    Instead, check the physical function for PCI_COMMAND_MEMORY.

David

  parent reply	other threads:[~2016-02-15 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1455225026-25792-1-git-send-email-konrad.wilk@oracle.com>
     [not found] ` <1455225026-25792-2-git-send-email-konrad.wilk@oracle.com>
2016-02-12  9:19   ` [Xen-devel] [PATCH 1/4] xen/pciback: Check PF instead of VF for PCI_COMMAND_MEMORY Jan Beulich
     [not found] ` <1455225026-25792-3-git-send-email-konrad.wilk@oracle.com>
2016-02-12  9:25   ` [Xen-devel] [PATCH 2/4] xen/pciback: Save the number of MSI-X entries to be copied later Jan Beulich
     [not found] ` <1455225026-25792-5-git-send-email-konrad.wilk@oracle.com>
2016-02-14  1:23   ` [PATCH 4/4] xen/pcifront: Fix mysterious crashes when NUMA locality information was extracted Boris Ostrovsky
     [not found]     ` <20160215140532.GB3698@char.us.oracle.com>
2016-02-15 14:37       ` Boris Ostrovsky
2016-02-15 14:27   ` [Xen-devel] " David Vrabel
2016-02-15 14:35 ` David Vrabel [this message]
2016-02-15 14:38   ` [Xen-devel] [PATCH] Fixes to Xen pcifront and pciback (v1) David Vrabel

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=56C1E24C.5040704@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tommi@airikka.net \
    --cc=xen-devel@lists.xenproject.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