2018-06-11 11:50 GMT+02:00 Ferruh Yigit <ferruh.yi...@intel.com>: > On 6/11/2018 10:33 AM, Michał Krawczyk wrote: >> 2018-06-11 11:26 GMT+02:00 Ferruh Yigit <ferruh.yi...@intel.com>: >>> On 6/11/2018 9:45 AM, Michał Krawczyk wrote: >>>> 2018-06-08 21:45 GMT+02:00 Ferruh Yigit <ferruh.yi...@intel.com>: >>>>> On 6/7/2018 10:42 AM, Michal Krawczyk wrote: >>>>>> The upcoming patches for the ENA PMD are part of 1.1.0 update of the PMD >>>>>> and the version number is updated accordingly. >>>>> >>>>> Does it make sense to add a release notes update to announce driver >>>>> update? >>>> >>>> Is it possible to move the patch at the end of the uploaded patches, >>>> so there won't be need to reupload everything? >>> >>> Yes release notes update can separate patch, to prevent a new version of all >>> set, if you are asking this. >> >> That would be great, thanks. > > Just recognized that you will already need to send a new version of the set, > please check the build error on 2/27. > > If you confirm you are OK with it, I can fix it while applying via: > s/(u64)/(unsigned long long)
I just prepared patch for this issue and I will send it right away. > >> >>> Or is there any existing documentation patch I am missing? >> >> No, there was no documentation patch. >> >>> >>>> The new commit message could be: >>>> >>>> >>>> net/ena: change version number to 1.1.0 >>>> >>>> ENA PMD version 1.1.0 introduces: >>>> * Update of the ena_com to the newer version >>>> * Remove support of legacy LLQ >>>> * Watchdog and device reset >>>> * LSC interrupt >>>> * Rx out of order completion >>>> * Linearization of mbufs with too many fragments >>>> * Information about maximum number of Tx and Rx descriptors >>>> * Validation of requested id on Tx (for Tx OOO completion) >>>> * Likely/unlikely statements >>>> * Link speed is now set as none >>>> * Other minor bug fixes and changes >>>>> >>>>>> >>>>>> Signed-off-by: Michal Krawczyk <m...@semihalf.com> >>>>> <...> >>> >
