From: Or Gerlitz <or.gerlitz@gmail.com>
To: "Williams, Mitch A" <mitch.a.williams@intel.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@redhat.com" <gospo@redhat.com>,
Or Gerlitz <ogerlitz@voltaire.com>
Subject: Re: [net-next-2.6 PATCH 2/5] if_link: Add SR-IOV configuration methods
Date: Tue, 2 Feb 2010 07:16:42 +0200 [thread overview]
Message-ID: <15ddcffd1002012116la5ae23ct7754e4e9287a1a1f@mail.gmail.com> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FDD55C136@rrsmsx501.amr.corp.intel.com>
Williams, Mitch A <mitch.a.williams@intel.com> wrote:
> To be honest, Or, this completely slipped my mind. I'll add it to my to-do list.
> If it's OK with you, I'd prefer to get this set of patches in as-is and
> add the egress qos stuff later. A lot of people have been asking for
> these patches, so I'd rather not delay for this feature.
Mitch, looking on the patch series I see that except for two patches
([PATCH 1/5] pci: Add SR-IOV convenience functions and macros and
[PATCH 2/4] libnetlink: Modify parser to track the first duplicated
attributes) seven other patches have to be changed/enhanced to
incorporate the egress qos mapping. If you prefer to do that later
rather then now I am fine with that, but lets not leave that a side.
Or.
next prev parent reply other threads:[~2010-02-02 5:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 10:39 [net-next-2.6 PATCH 1/5] pci: Add SR-IOV convenience functions and macros Jeff Kirsher
2010-01-30 10:39 ` [net-next-2.6 PATCH 2/5] if_link: Add SR-IOV configuration methods Jeff Kirsher
2010-01-31 14:25 ` Or Gerlitz
2010-02-01 19:33 ` Williams, Mitch A
2010-02-02 5:16 ` Or Gerlitz [this message]
2010-02-02 16:45 ` Williams, Mitch A
2010-02-04 1:36 ` David Miller
2010-01-30 10:40 ` [net-next-2.6 PATCH 3/5] net: Add netdev ops for SR-IOV configuration Jeff Kirsher
2010-02-03 22:00 ` Ben Hutchings
2010-01-30 10:40 ` [net-next-2.6 PATCH 4/5] rtnetlink: Add VF config code to rtnetlink Jeff Kirsher
2010-01-30 10:40 ` [net-next-2.6 PATCH 5/5] igb: support for VF configuration tools Jeff Kirsher
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=15ddcffd1002012116la5ae23ct7754e4e9287a1a1f@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.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;
as well as URLs for NNTP newsgroup(s).