RFC : field name identifier conventions
Get series with b4
b4 am 200710241328.20335@strip-the-willowVersions newest first
- v1 RFC Latest0 of 1 patch 0 repliesNew
Patches in v1 No applies recorded yet
The patch the cover letter announces is not in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1][RFC]: field name identifier conventions
Following the earlier discussion I have created two patches which shorten the identifiers in some of the structs:
1) A patch for the CCIDs, where I used the scheme suggested by Arnaldo (i.e. "c<N>{tx,rx}", e.g. hcrx->c2tx_ssthresh). This resulted in a rather large patch (66k) and was rather disappointing - there was not much of the expected reduction in multiline expressions. For these reasons I think it is better to stick with the old scheme. But if people are still interested in this and may have different opinion, have a look at how the conversion looks at:
http://www.erg.abdn.ac.uk/users/gerrit/dccp/rfc_patch_new_ccid_field_ids.diff
2) A patch for ackvec.{c,h}. This follows next and simply replaces the `dccp' in the struct dccp_ackvec{,_record} fields. I like this patch because it makes the code easier to read.
Arnaldo can you please indicate whether you find this patch acceptable - I am working on Ack Vectors (adding a tail pointer and fixing acknowledging old Ack Vectors): if you are not ok with the patch, then I use the old scheme.