All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Jianbo Liu <jianbo.liu@linaro.org>,
	David Marchand <david.marchand@6wind.com>,
	Shreyansh Jain <shreyansh.jain@nxp.com>,
	dev@dpdk.org
Subject: Re: Clarification for eth_driver changes
Date: Thu, 10 Nov 2016 12:07:02 +0100	[thread overview]
Message-ID: <3418950.5t2zjhjnTA@xps13> (raw)
In-Reply-To: <CAOaVG16rdaGTNpVxiY2qhX1=zLJfgjrpAnLGRmxzJ3eVGKUfYA@mail.gmail.com>

Hi Stephen,

2016-11-10 02:51, Stephen Hemminger:
> I also think drv_flags should part of device not PCI. Most of the flags
> there like link state support are generic. If it isn't changed for this
> release will probably have to break ABI to fully support VMBUS

When do you plan to send VMBUS patches?
Could you send a deprecation notice for this change?
Are you aware of the work started by Shreyansh to have a generic bus model?
Could you help in 17.02 timeframe to have a solid bus model?

Thanks

  reply	other threads:[~2016-11-10 11:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  7:26 Clarification for eth_driver changes Shreyansh Jain
2016-11-10  7:51 ` Jianbo Liu
2016-11-10  8:03   ` Thomas Monjalon
2016-11-10  8:42     ` Shreyansh Jain
2016-11-10  8:58       ` Thomas Monjalon
2016-11-10  9:20         ` Jianbo Liu
2016-11-10 10:51           ` Stephen Hemminger
2016-11-10 11:07             ` Thomas Monjalon [this message]
2016-11-10 11:09             ` Shreyansh Jain
2016-11-10  8:38   ` Shreyansh Jain
2016-11-10  8:16 ` David Marchand
2016-11-10 11:05   ` Shreyansh Jain
2016-11-11 19:16     ` Ferruh Yigit
2016-11-12 17:44       ` Shreyansh Jain
2016-11-14 17:38         ` Ferruh Yigit
2016-11-16  5:09           ` Shreyansh Jain
2016-11-14  9:07       ` David Marchand

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=3418950.5t2zjhjnTA@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jianbo.liu@linaro.org \
    --cc=shreyansh.jain@nxp.com \
    --cc=stephen@networkplumber.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.