From: David Miller <davem@davemloft.net>
To: ajitk@serverengines.com, ajitkhaparde@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] be2net: remove usage of be_pci_func
Date: Mon, 08 Mar 2010 10:46:34 -0800 (PST) [thread overview]
Message-ID: <20100308.104634.257362723.davem@davemloft.net> (raw)
In-Reply-To: <20100308002125.GA18118@serverengines.com>
From: Ajit Khaparde <ajitkhaparde@gmail.com>
Date: Mon, 8 Mar 2010 05:51:27 +0530
> When PCI functions are virtuialized in applications by assigning PCI
> functions to VM (PCI passthrough), the be2net driver in the VM sees a
> different function number. So, use of PCI function number in any
> calculation will break existing code. This patch takes care of it.
>
> Signed-off-by: Ajit Khaparde <ajitk@serverengines.com>
Applied.
prev parent reply other threads:[~2010-03-08 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 0:21 [PATCH 1/2] be2net: remove usage of be_pci_func Ajit Khaparde
2010-03-08 18:46 ` David Miller [this message]
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=20100308.104634.257362723.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajitk@serverengines.com \
--cc=ajitkhaparde@gmail.com \
--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 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).