Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> writes: > This series is big (51 patches) because it needs to fix thousands of > broken cross references on media. I may end splitting it on two series > to make easier for review, one for the script and another for media doc > fixes. That might help, yes. > Such series affect this RFC as it is creating a tools/docs and placing > there the parse-headers.py code as: > > tools/docs/lib/parse_data_structs.py | 230 +++++++++++++++-------------------- > tools/docs/parse-headers.py | 5 > > Now, if you prefer tools/doc instead and/or place the libs elsewhere, > we have a couple of options: > > 1. rebase my series to do the changes. I suspect that there won't > be much conflicts, but this may delay a little bit sending you > what I have; > > 2. add a patch at the end moving stuff elsewhere; > > 3. on your series, move them elsewhere. > > What do you prefer? Between "tools/doc" and "tools/docs" I don't really have overly strong feelings; if you work has the latter we can just stick with that. If you propose "tools/Documentation", though, expect resistance :) As I said, my series was an RFC to see what it would look like; it did't take all that long the first time around, and will be even quicker to redo on top of a new base, whatever that turns out to be. Thanks, jon
