| Todd Foggoa | a292c8c | 2016-04-06 09:57:01 -0400 | [diff] [blame] | 1 | |
| 2 | Changes needed to DPDK are stored here as git patch files. Maintaining these |
| 3 | files using “git format-patch” and “git am” will make it simpler to manage |
| 4 | these changes. Patches made to DPDK should only be temporary until they are |
| 5 | accepted upstream and made available in the next DPDK release. |
| 6 | |
| 7 | The following is the method used to generate these patches: |
| 8 | |
| 9 | 1. Git clone the DPDK to a new directory: |
| 10 | # git clone http://dpdk.org/git/dpdk dpdk |
| 11 | |
| 12 | 2. Create a branch based on the DPDK release you wish to patch. |
| 13 | Note, “git tag” will show you all the release tags. The following example is |
| 14 | for DPDK release tag “v2.2.0” and will create a branch named “two_dot_two”. |
| 15 | # cd dpdk |
| 16 | # git checkout -b two_dot_two v2.2.0 |
| 17 | |
| 18 | 3. Apply all the existing VPP DPDK patches to this new branch. |
| 19 | # git am <VPP directory>/dpdk/dpdk-2.2.0_patches/* |
| 20 | |
| 21 | 4. Make your changes and commit your change to your DPDK repository. |
| 22 | # <edit files> |
| 23 | # git commit -s |
| 24 | |
| 25 | 5. Create the patch files with format-patch. This creates all the patch files |
| 26 | for your branch (two_dot_two), with your latest commits as the last ones. |
| 27 | # git format-patch master..two_dot_two |
| 28 | |
| 29 | 6. Copy, add and commit the new patches into the VPP patches directory. |
| 30 | # cp <new patch files> <VPP directory>/dpdk/dpdk-2.2.0_patches |
| 31 | # cd <VPP directory> |
| 32 | # git add dpdk/dpdk-2.2.0_patches/<new patch files> |
| 33 | # git commit -s |
| 34 | |