Drop the reference of meta-intel in README

This has been created as a separate layer for a long time, the
reference of meta-intel in the README seems a bit confusion.
So drop all of them.

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This commit is contained in:
Kevin Hao 2018-12-04 14:50:02 +08:00 committed by Anuj Mittal
parent af002507e3
commit 909bdd8dc6

21
README
View File

@ -1,18 +1,7 @@
meta-dpdk meta-dpdk
========= =========
This README file contains information on building and booting This README file contains information on building the DPDK package.
meta-intel BSP layers. Please see the corresponding sections below
for details.
Yocto Project Compatible
========================
The BSPs contained in this layer are compatible with the Yocto Project
as per the requirements listed here:
https://www.yoctoproject.org/webform/yocto-project-compatible-registration
Dependencies Dependencies
@ -71,15 +60,11 @@ Specifically, they should:
tested the patch, and for any non-trivial or non-obvious testing tested the patch, and for any non-trivial or non-obvious testing
setup, provide details of that setup. setup, provide details of that setup.
Doing a quick 'git log' in meta-intel will provide you with many Doing a quick 'git log' in meta-dpdk will provide you with many
examples of good example commits if you have questions about any examples of good example commits if you have questions about any
aspect of the preferred format. aspect of the preferred format.
The meta-intel maintainers will do their best to review and/or pull in The meta-dpdk maintainers will do their best to review and/or pull in
a patch or patchset within 24 hours of the time it was posted. For a patch or patchset within 24 hours of the time it was posted. For
larger and/or more involved patches and patchsets, the review process larger and/or more involved patches and patchsets, the review process
may take longer. may take longer.
Please see the meta-intel/MAINTAINERS file for the list of maintainers
and their specific areas; it's also a good idea to cc: the specific
maintainer, if applicable.