diff options
| author |   Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk> | 2015-09-07 17:01:59 -0300 |
|---|---|---|
| committer |   Jonathan Corbet <corbet@lwn.net> | 2015-09-13 14:38:51 -0600 |
| commit | 4d73270192ec8238135d9fb65b49f6f42f50818d (patch) | |
| tree | 14c83716bac9b796a1629ac5d51b80ab9b786ab8 /Documentation/networking | |
| parent | sysfs.txt: mention that store method buffers are null-terminated (diff) | |
| download | linux-dev-4d73270192ec8238135d9fb65b49f6f42f50818d.tar.xz linux-dev-4d73270192ec8238135d9fb65b49f6f42f50818d.zip | |
scripts/kernel-doc: Replacing highlights hash by an array
The "highlight" code is very sensible to the order of the hash keys,
but the order of the keys cannot be predicted. It generates
faulty DocBook entries like:
- @<function>device_for_each_child</function>
Sorting the result is not enough some times (as it's deterministic but
we can't control it).
We should use an array for that job, so we can guarantee that the order
of the regex execution on dohighlight is correct.
[jc: I think this is kind of papering around the real problem, that people
are saying @function() when "function" is not a parameter. But this makes
things better than they were before, so...]
Signed-off-by: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/networking')
0 files changed, 0 insertions, 0 deletions