From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Frank Pan <frankpzh@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Yu Zhao <yu.zhao@intel.com>, Chris Wright <chrisw@sous-sol.org>,
Mitch Williams <mitch.a.williams@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"David S. Miller" <davem@davemloft.net>,
Matt Carlson <mcarlson@broadcom.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Add a helper function in PCI IOV to get VF device
Date: Fri, 18 Jun 2010 10:17:14 -0700 [thread overview]
Message-ID: <20100618101714.15146089@virtuousgeek.org> (raw)
In-Reply-To: <AANLkTil74rKaddoYKj-zuEjfl0cKT8uyofjH9wZ0zFOf@mail.gmail.com>
On Fri, 11 Jun 2010 15:42:12 +0800
Frank Pan <frankpzh@gmail.com> wrote:
> > Per the discussion in this thread it sounds like this really has
> > nothing to do with sysfs and more to do with being a convenient API for
> > drivers.
> Yes.
>
> > Is that correct? If so, and assuming there's not some other way of
> > getting this info from a driver, I'm ok with it, but it should be
> > submitted as part of a patchset including driver code that uses it.
> Yes, I may submit them all after the driver hack is complete. I put the
> issue here to get response of some thing like, is this change possible?
> or is there a better way to do it?
>
> Thanks for reply.
I think once we see the driver usage it'll be easier to say.
Chris is the one you'll need to convince though.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-06-18 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 5:05 Add a helper function in PCI IOV to get VF device Frank Pan
2010-06-01 18:39 ` Greg KH
2010-06-01 18:57 ` Williams, Mitch A
2010-06-02 6:12 ` Frank Pan
2010-06-02 18:59 ` Williams, Mitch A
2010-06-03 2:57 ` Frank Pan
2010-06-03 3:11 ` Frank Pan
2010-06-03 17:10 ` Williams, Mitch A
2010-06-04 2:28 ` Frank Pan
2010-06-03 17:56 ` Chris Wright
2010-06-04 2:43 ` Frank Pan
2010-06-08 22:12 ` Chris Wright
2010-06-02 6:02 ` Frank Pan
2010-06-08 21:35 ` Jesse Barnes
2010-06-11 7:42 ` Frank Pan
2010-06-18 17:17 ` Jesse Barnes [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=20100618101714.15146089@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=frankpzh@gmail.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mitch.a.williams@intel.com \
--cc=rjw@sisk.pl \
--cc=yu.zhao@intel.com \
/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