DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: add EAL bus support in release notes
Date: Tue, 14 Feb 2017 15:12:09 +0100	[thread overview]
Message-ID: <5863283.oP4xk1QIUq@xps13> (raw)
In-Reply-To: <DB5PR04MB16051D7AB3B69918F404E13789580@DB5PR04MB1605.eurprd04.prod.outlook.com>

2017-02-14 12:56, Hemant Agrawal:
> > Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> > @@ -237,6 +237,16 @@ Resolved Issues
> >  EAL
> >  ~~~
> > 
> > +* **Added support for representing buses in EAL**
> > +
> > +  A new structure ``rte_bus`` is introduced in EAL. This allows for
> > + devices to  be represented by buses they are connected to. A new bus
> > + can be added to  DPDK by extending the ``rte_bus`` structure and
> > + implementing the scan and  probe functions. Once a new bus is
> > + registered using provided APIs, new  devices can be detected and
> > initialized using bus scan and probe callbacks.
> > +
> > +  With this change, devices other than PCI or VDEV type can also be
> > + represented  in DPDK framework.
> > 
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

It was in "Resolved Issues".
Moved and applied, thanks

      reply	other threads:[~2017-02-14 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 11:29 Shreyansh Jain
2017-02-14  0:42 ` Mcnamara, John
2017-02-14  3:23 ` Jerin Jacob
2017-02-14 12:56 ` Hemant Agrawal
2017-02-14 14:12   ` Thomas Monjalon [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=5863283.oP4xk1QIUq@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=shreyansh.jain@nxp.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).