Searched refs:reverse (Results 1 – 13 of 13) sorted by relevance
50 commits=$(git log --format='%h' --reverse $range)51 headlines=$(git log --format='%s' --reverse $range)52 bodylines=$(git log --format='%b' --reverse $range)53 fixes=$(git log --format='%h %s' --reverse $range | grep -i ': *fix' | cut -d' ' -f1)55 tags=$(git log --format='%b' --reverse $range | grep -i -e 'by *:' -e 'fix.*:')
360 commits=$(git rev-list --reverse $range)362 commits=$(git rev-list --reverse --max-count=$number HEAD)
107 git log --oneline --reverse $range |
274 * way that the reverse tuple will have the same LSBs as the original300 /** Complete the reverse tuple by translating the SRC address and swapping305 /* Calculate the expected rss hash for the reverse tuple. */
684 They perform the reverse of `\*_ENCAP actions`_ by popping protocol headers
3540 reverse order of their creation.
82 To remove a service core, the steps are similar to adding but in reverse order.
786 u8 reverse; /* set to true to reverse FV order */ member
1337 if (hw->blk[params->blk].es.reverse) in ice_flow_xtract_pkt_flags()1573 if (hw->blk[params->blk].es.reverse) in ice_flow_xtract_fld()1651 if (hw->blk[params->blk].es.reverse) in ice_flow_xtract_raws()2566 if (hw->blk[blk].es.reverse) in ice_flow_set_hw_prof()
2731 u8 reverse; /* reverse FV order */ member4196 es->reverse = blk_sizes[i].reverse; in ice_init_hw_tbls()
1005 expectations. The previous calling order was the reverse of this (lifo) and
27 Added a hardware hint CLDEMOTE, which is similar to prefetch in reverse.
275 modification of the work for the customer's own use and reverse