All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	david.vrabel@citrix.com, boris.ostrovsky@oracle.com
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH 2/2] xen/pciback: Remove is_busmaster=0 as pci_disable_device does it already
Date: Fri,  3 Apr 2015 10:28:09 -0400	[thread overview]
Message-ID: <1428071289-11995-3-git-send-email-konrad.wilk@oracle.com> (raw)
In-Reply-To: <1428071289-11995-1-git-send-email-konrad.wilk@oracle.com>

There is no need for this.

Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
 drivers/xen/xen-pciback/pciback_ops.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/xen/xen-pciback/pciback_ops.c b/drivers/xen/xen-pciback/pciback_ops.c
index 26e6513..a131733 100644
--- a/drivers/xen/xen-pciback/pciback_ops.c
+++ b/drivers/xen/xen-pciback/pciback_ops.c
@@ -118,8 +118,6 @@ void xen_pcibk_reset_device(struct pci_dev *dev)
 #endif
 		if (pci_is_enabled(dev))
 			pci_disable_device(dev);
-
-		dev->is_busmaster = 0;
 	} else {
 		pci_read_config_word(dev, PCI_COMMAND, &cmd);
 		if (cmd & (PCI_COMMAND_INVALIDATE)) {
-- 
2.1.0


  parent reply	other threads:[~2015-04-03 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 14:28 [PATCH] XSA120 follows to the Linux kernel Konrad Rzeszutek Wilk
2015-04-03 14:28 ` [PATCH 1/2] xen/pciback: Don't disable PCI_COMMAND on PCI device reset Konrad Rzeszutek Wilk
2015-04-03 14:28 ` Konrad Rzeszutek Wilk
2015-04-03 14:28 ` Konrad Rzeszutek Wilk [this message]
2015-04-03 14:28 ` [PATCH 2/2] xen/pciback: Remove is_busmaster=0 as pci_disable_device does it already Konrad Rzeszutek Wilk
2015-04-10 14:37 ` [PATCH] XSA120 follows to the Linux kernel David Vrabel
2015-04-10 14:37 ` [Xen-devel] " David Vrabel
2015-04-14  8:45   ` Jan Beulich
2015-04-14  8:45   ` [Xen-devel] " Jan Beulich

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=1428071289-11995-3-git-send-email-konrad.wilk@oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.