diff options
Diffstat (limited to 'meta-dpdk/README')
| -rw-r--r-- | meta-dpdk/README | 56 |
1 files changed, 0 insertions, 56 deletions
diff --git a/meta-dpdk/README b/meta-dpdk/README deleted file mode 100644 index 1b256d02..00000000 --- a/meta-dpdk/README +++ /dev/null | |||
| @@ -1,56 +0,0 @@ | |||
| 1 | meta-dpdk | ||
| 2 | ========= | ||
| 3 | |||
| 4 | This README file contains information on building the DPDK package. | ||
| 5 | |||
| 6 | This is a fork of meta-dpdk, git://git.yoctoproject.org/meta-dpdk | ||
| 7 | langdale branch as of commit bd1b4f10262f12dd66a91383757ccba4eeda0b08. | ||
| 8 | |||
| 9 | The software in this fork is specific to the AMD Embedded versal-net. | ||
| 10 | |||
| 11 | Dependencies | ||
| 12 | ============ | ||
| 13 | |||
| 14 | This layer depends on: | ||
| 15 | |||
| 16 | URI: git://git.openembedded.org/bitbake | ||
| 17 | branch: master | ||
| 18 | |||
| 19 | URI: git://git.openembedded.org/openembedded-core | ||
| 20 | layers: meta | ||
| 21 | branch: master | ||
| 22 | |||
| 23 | |||
| 24 | Guidelines for submitting patches | ||
| 25 | ==================================== | ||
| 26 | |||
| 27 | Please submit any patches against this fork of meta-dpdk to the meta-xilinx | ||
| 28 | mailing list (meta-xilinx@lists.yoctoproject.org). | ||
| 29 | |||
| 30 | Regardless of how you submit a patch or patchset, the patches should | ||
| 31 | at minimum follow the suggestions outlined in the 'Submitting a Change | ||
| 32 | to the Yocto Project' section in the Yocto Project Development Manual. | ||
| 33 | Specifically, they should: | ||
| 34 | |||
| 35 | - Include a 'Signed-off-by:' line. A commit can't legally be pulled | ||
| 36 | in without this. | ||
| 37 | |||
| 38 | - Provide a single-line, short summary of the change. This short | ||
| 39 | description should be prefixed by the BSP or recipe name, as | ||
| 40 | appropriate, followed by a colon. Capitalize the first character | ||
| 41 | of the summary (following the colon). | ||
| 42 | |||
| 43 | - For the body of the commit message, provide detailed information | ||
| 44 | that describes what you changed, why you made the change, and the | ||
| 45 | approach you used. | ||
| 46 | |||
| 47 | - If the change addresses a specific bug or issue that is associated | ||
| 48 | with a bug-tracking ID, include a reference to that ID in your | ||
| 49 | detailed description in the following format: [YOCTO #<bug-id>]. | ||
| 50 | |||
| 51 | - Pay attention to line length - please don't allow any particular | ||
| 52 | line in the commit message to stretch past 72 characters. | ||
| 53 | |||
| 54 | - For any non-trivial patch, provide information about how you | ||
| 55 | tested the patch, and for any non-trivial or non-obvious testing | ||
| 56 | setup, provide details of that setup. | ||