From: "Rose, Gregory V" <gregory.v.rose@intel.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
Ian Campbell <ijc@hellion.org.uk>,
"davem@davemloft.net" <davem@davemloft.net>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@redhat.com" <gospo@redhat.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: RE: [net-next 1/8] pci: Add flag indicating device has been assigned by KVM
Date: Fri, 23 Sep 2011 12:20:27 -0700 [thread overview]
Message-ID: <43F901BD926A4E43B106BF17856F0755019C518E80@orsmsx508.amr.corp.intel.com> (raw)
In-Reply-To: <20110923190537.GA18850@phenom.oracle.com>
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Friday, September 23, 2011 12:06 PM
> To: Rose, Gregory V
> Cc: Kirsher, Jeffrey T; Ian Campbell; davem@davemloft.net; Jesse Barnes;
> netdev@vger.kernel.org; gospo@redhat.com; linux-pci@vger.kernel.org
> Subject: Re: [net-next 1/8] pci: Add flag indicating device has been
> assigned by KVM
>
> > > > Version 2 of this patch with the modified comment was just posted to
> > > netdev. Ian Campbell had mentioned that the Xen pciback driver should
> be
> > > modified to use this flag but I don't believe any patches for it have
> been
> > > created yet.
> > >
> > > http://marc.info/?i=20110729165446.GA6731@dumpdata.com
> > >
> >
> > I'm not sure who generated the patches to xen-pciback. It wasn't me and
> I couldn't tell from the links you provided who did generate that patch.
> I don't see it now though.
>
> I provided it.
>
> And I asked for a git tree so I could double check that it actually
> worked as I don't have the full set of your patches.
>
> Can you provide me a link to your public git tree or just repost it once
> more?
Ah, I get it now.
Jeff Kirsher is the maintainer of our git trees. Hopefully he'll come around and provide that info for you soon.
- Greg
next prev parent reply other threads:[~2011-09-23 19:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 10:12 [net-next 0/8][pull request] Intel Wired LAN Driver Update Jeff Kirsher
2011-09-21 10:12 ` [net-next 1/8] pci: Add flag indicating device has been assigned by KVM Jeff Kirsher
2011-09-23 4:16 ` Jeff Kirsher
2011-09-23 5:20 ` Jesse Barnes
[not found] ` <20110923104957.2f76d1a4@jbarnes-x220>
2011-09-23 5:23 ` Jeff Kirsher
2011-09-23 7:27 ` Ian Campbell
2011-09-23 14:41 ` Rose, Gregory V
2011-09-23 15:03 ` Ian Campbell
2011-09-23 15:11 ` Rose, Gregory V
2011-09-23 15:45 ` Jeff Kirsher
2011-09-23 16:43 ` Konrad Rzeszutek Wilk
2011-09-23 17:04 ` Rose, Gregory V
2011-09-23 18:00 ` Konrad Rzeszutek Wilk
2011-09-23 18:24 ` Rose, Gregory V
2011-09-23 19:05 ` Konrad Rzeszutek Wilk
2011-09-23 19:20 ` Rose, Gregory V [this message]
2011-09-24 4:41 ` Jeff Kirsher
2011-09-26 16:25 ` [net-next 1/8] pci: Add flag indicating device has been assigned by KVM [and Xen] Konrad Rzeszutek Wilk
2011-09-26 16:31 ` Rose, Gregory V
2011-09-26 16:42 ` Konrad Rzeszutek Wilk
2011-09-26 17:01 ` Rose, Gregory V
2011-09-21 10:12 ` [net-next 2/8] ixgbe: Reconfigure SR-IOV Init Jeff Kirsher
2011-09-21 10:12 ` [net-next 3/8] ixgbe: DCB, do not call set_state() from IEEE mode Jeff Kirsher
2011-09-21 10:12 ` [net-next 4/8] ixgbe: cleanup X540 interrupt enablement Jeff Kirsher
2011-09-21 10:12 ` [net-next 5/8] ixgbe: dcb, set priority to traffic class mappings Jeff Kirsher
2011-09-21 10:12 ` [net-next 6/8] ixgbe: avoid HW lockup when adapter is reset with Tx work pending Jeff Kirsher
2011-09-21 10:12 ` [net-next 7/8] ixgbe: add WOL support for X540 Jeff Kirsher
2011-09-21 10:12 ` [net-next 8/8] ixgbe: remove global reset to the MAC Jeff Kirsher
2011-09-21 19:13 ` [net-next 0/8][pull request] Intel Wired LAN Driver Update David Miller
2011-09-21 19:58 ` Rose, Gregory V
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=43F901BD926A4E43B106BF17856F0755019C518E80@orsmsx508.amr.corp.intel.com \
--to=gregory.v.rose@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=ijc@hellion.org.uk \
--cc=jbarnes@virtuousgeek.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@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 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.