|
Revision tags: v6.15, v6.15-rc7, v6.15-rc6, v6.15-rc5, v6.15-rc4, v6.15-rc3, v6.15-rc2, v6.15-rc1, v6.14, v6.14-rc7, v6.14-rc6, v6.14-rc5, v6.14-rc4, v6.14-rc3, v6.14-rc2, v6.14-rc1, v6.13, v6.13-rc7, v6.13-rc6, v6.13-rc5, v6.13-rc4, v6.13-rc3, v6.13-rc2, v6.13-rc1, v6.12, v6.12-rc7, v6.12-rc6, v6.12-rc5, v6.12-rc4, v6.12-rc3, v6.12-rc2, v6.12-rc1, v6.11, v6.11-rc7, v6.11-rc6, v6.11-rc5, v6.11-rc4, v6.11-rc3, v6.11-rc2, v6.11-rc1, v6.10, v6.10-rc7, v6.10-rc6, v6.10-rc5, v6.10-rc4, v6.10-rc3, v6.10-rc2, v6.10-rc1, v6.9, v6.9-rc7, v6.9-rc6, v6.9-rc5, v6.9-rc4, v6.9-rc3, v6.9-rc2, v6.9-rc1, v6.8, v6.8-rc7, v6.8-rc6, v6.8-rc5, v6.8-rc4, v6.8-rc3, v6.8-rc2, v6.8-rc1, v6.7, v6.7-rc8, v6.7-rc7, v6.7-rc6, v6.7-rc5, v6.7-rc4, v6.7-rc3, v6.7-rc2, v6.7-rc1, v6.6, v6.6-rc7, v6.6-rc6, v6.6-rc5, v6.6-rc4, v6.6-rc3, v6.6-rc2, v6.6-rc1, v6.5, v6.5-rc7, v6.5-rc6, v6.5-rc5, v6.5-rc4, v6.5-rc3, v6.5-rc2, v6.5-rc1, v6.4, v6.4-rc7, v6.4-rc6, v6.4-rc5, v6.4-rc4, v6.4-rc3, v6.4-rc2, v6.4-rc1, v6.3, v6.3-rc7, v6.3-rc6, v6.3-rc5, v6.3-rc4, v6.3-rc3, v6.3-rc2, v6.3-rc1, v6.2, v6.2-rc8, v6.2-rc7, v6.2-rc6, v6.2-rc5, v6.2-rc4, v6.2-rc3, v6.2-rc2, v6.2-rc1, v6.1, v6.1-rc8, v6.1-rc7, v6.1-rc6, v6.1-rc5, v6.1-rc4, v6.1-rc3, v6.1-rc2, v6.1-rc1, v6.0, v6.0-rc7, v6.0-rc6, v6.0-rc5, v6.0-rc4, v6.0-rc3, v6.0-rc2, v6.0-rc1, v5.19, v5.19-rc8, v5.19-rc7, v5.19-rc6, v5.19-rc5, v5.19-rc4, v5.19-rc3, v5.19-rc2, v5.19-rc1, v5.18, v5.18-rc7, v5.18-rc6, v5.18-rc5, v5.18-rc4, v5.18-rc3, v5.18-rc2, v5.18-rc1, v5.17, v5.17-rc8, v5.17-rc7, v5.17-rc6, v5.17-rc5, v5.17-rc4, v5.17-rc3, v5.17-rc2, v5.17-rc1, v5.16, v5.16-rc8, v5.16-rc7, v5.16-rc6, v5.16-rc5, v5.16-rc4, v5.16-rc3, v5.16-rc2, v5.16-rc1, v5.15, v5.15-rc7, v5.15-rc6, v5.15-rc5, v5.15-rc4, v5.15-rc3, v5.15-rc2, v5.15-rc1, v5.14, v5.14-rc7, v5.14-rc6, v5.14-rc5, v5.14-rc4, v5.14-rc3, v5.14-rc2, v5.14-rc1, v5.13, v5.13-rc7, v5.13-rc6, v5.13-rc5, v5.13-rc4, v5.13-rc3, v5.13-rc2, v5.13-rc1, v5.12, v5.12-rc8, v5.12-rc7, v5.12-rc6, v5.12-rc5, v5.12-rc4, v5.12-rc3, v5.12-rc2, v5.12-rc1, v5.12-rc1-dontuse, v5.11, v5.11-rc7, v5.11-rc6, v5.11-rc5, v5.11-rc4, v5.11-rc3, v5.11-rc2, v5.11-rc1, v5.10, v5.10-rc7, v5.10-rc6 |
|
| #
c25ce589 |
| 23-Nov-2020 |
Finn Behrens <[email protected]> |
tweewide: Fix most Shebang lines
Change every shebang which does not need an argument to use /usr/bin/env. This is needed as not every distro has everything under /usr/bin, sometimes not even bash.
tweewide: Fix most Shebang lines
Change every shebang which does not need an argument to use /usr/bin/env. This is needed as not every distro has everything under /usr/bin, sometimes not even bash.
Signed-off-by: Finn Behrens <[email protected]> Signed-off-by: Masahiro Yamada <[email protected]>
show more ...
|
|
Revision tags: v5.10-rc5, v5.10-rc4, v5.10-rc3, v5.10-rc2, v5.10-rc1, v5.9, v5.9-rc8, v5.9-rc7 |
|
| #
9303c9d5 |
| 25-Sep-2020 |
Mauro Carvalho Chehab <[email protected]> |
docs: get rid of :c:type explicit declarations for structs
The :c:type:`foo` only works properly with structs before Sphinx 3.x.
On Sphinx 3.x, structs should now be declared using the .. c:struct,
docs: get rid of :c:type explicit declarations for structs
The :c:type:`foo` only works properly with structs before Sphinx 3.x.
On Sphinx 3.x, structs should now be declared using the .. c:struct, and referenced via :c:struct tag.
As we now have the automarkup.py macro, that automatically convert: struct foo
into cross-references, let's get rid of that, solving several warnings when building docs with Sphinx 3.x.
Reviewed-by: André Almeida <[email protected]> # blk-mq.rst Reviewed-by: Takashi Iwai <[email protected]> # sound Reviewed-by: Mike Rapoport <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
|
Revision tags: v5.9-rc6, v5.9-rc5, v5.9-rc4, v5.9-rc3, v5.9-rc2, v5.9-rc1, v5.8, v5.8-rc7, v5.8-rc6, v5.8-rc5, v5.8-rc4, v5.8-rc3, v5.8-rc2 |
|
| #
a5989e29 |
| 20-Jun-2020 |
Alexander A. Klimov <[email protected]> |
Replace HTTP links with HTTPS ones: Documentation/sphinx/parse-headers.pl
Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate.
Replace HTTP links with HTTPS ones: Documentation/sphinx/parse-headers.pl
Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate.
Deterministic algorithm: For each file: For each line: If doesn't contain `\bxmlns\b`: For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`: If both the HTTP and HTTPS versions return 200 OK and serve the same content: Replace HTTP with HTTPS.
Signed-off-by: Alexander A. Klimov <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jonathan Corbet <[email protected]>
show more ...
|
|
Revision tags: v5.8-rc1, v5.7, v5.7-rc7, v5.7-rc6, v5.7-rc5, v5.7-rc4, v5.7-rc3, v5.7-rc2, v5.7-rc1, v5.6, v5.6-rc7, v5.6-rc6, v5.6-rc5, v5.6-rc4, v5.6-rc3, v5.6-rc2, v5.6-rc1, v5.5, v5.5-rc7, v5.5-rc6, v5.5-rc5, v5.5-rc4, v5.5-rc3, v5.5-rc2, v5.5-rc1, v5.4, v5.4-rc8, v5.4-rc7, v5.4-rc6, v5.4-rc5, v5.4-rc4, v5.4-rc3, v5.4-rc2, v5.4-rc1, v5.3, v5.3-rc8, v5.3-rc7, v5.3-rc6, v5.3-rc5, v5.3-rc4, v5.3-rc3, v5.3-rc2, v5.3-rc1, v5.2, v5.2-rc7, v5.2-rc6, v5.2-rc5, v5.2-rc4, v5.2-rc3, v5.2-rc2, v5.2-rc1, v5.1, v5.1-rc7, v5.1-rc6, v5.1-rc5, v5.1-rc4, v5.1-rc3, v5.1-rc2, v5.1-rc1, v5.0, v5.0-rc8, v5.0-rc7, v5.0-rc6, v5.0-rc5, v5.0-rc4, v5.0-rc3, v5.0-rc2, v5.0-rc1, v4.20, v4.20-rc7, v4.20-rc6, v4.20-rc5, v4.20-rc4, v4.20-rc3, v4.20-rc2, v4.20-rc1, v4.19, v4.19-rc8, v4.19-rc7, v4.19-rc6, v4.19-rc5, v4.19-rc4, v4.19-rc3, v4.19-rc2, v4.19-rc1, v4.18, v4.18-rc8, v4.18-rc7, v4.18-rc6, v4.18-rc5, v4.18-rc4, v4.18-rc3, v4.18-rc2, v4.18-rc1 |
|
| #
f3821276 |
| 05-Jun-2018 |
Federico Vaga <[email protected]> |
doc:sphinx: fix parse-header description
The description speaks about the option ``--man`` but it does not exist. Instead, there is the option ``--usage``
$ ./Documentation/sphinx/parse-headers
doc:sphinx: fix parse-header description
The description speaks about the option ``--man`` but it does not exist. Instead, there is the option ``--usage``
$ ./Documentation/sphinx/parse-headers.pl --man Unknown option: man Usage: parse_headers.pl [<options>] <C_FILE> <OUT_FILE> [<EXCEPTIONS_FILE>]
Where <options> can be: --debug, --help or --man.
Signed-off-by: Federico Vaga <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
show more ...
|
|
Revision tags: v4.17, v4.17-rc7, v4.17-rc6, v4.17-rc5, v4.17-rc4, v4.17-rc3 |
|
| #
32590819 |
| 25-Apr-2018 |
Mauro Carvalho Chehab <[email protected]> |
MAINTAINERS & files: Canonize the e-mails I use at files
From now on, I'll start using my @kernel.org as my development e-mail.
As such, let's remove the entries that point to the old mchehab@s-ope
MAINTAINERS & files: Canonize the e-mails I use at files
From now on, I'll start using my @kernel.org as my development e-mail.
As such, let's remove the entries that point to the old [email protected] at MAINTAINERS file.
For the files written with a copyright with mchehab@s-opensource, let's keep Samsung on their names, using [email protected], in order to keep pointing to my employer, with sponsors the work.
For the files written before I join Samsung (on July, 4 2013), let's just use [email protected].
For bug reports, we can simply point to just kernel.org, as this will reach my mchehab+samsung inbox anyway.
Signed-off-by: Mauro Carvalho Chehab <[email protected]> Signed-off-by: Brian Warner <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
|
Revision tags: v4.17-rc2, v4.17-rc1, v4.16, v4.16-rc7, v4.16-rc6, v4.16-rc5, v4.16-rc4, v4.16-rc3, v4.16-rc2, v4.16-rc1, v4.15, v4.15-rc9, v4.15-rc8, v4.15-rc7, v4.15-rc6, v4.15-rc5, v4.15-rc4, v4.15-rc3, v4.15-rc2, v4.15-rc1, v4.14, v4.14-rc8, v4.14-rc7, v4.14-rc6, v4.14-rc5, v4.14-rc4, v4.14-rc3, v4.14-rc2, v4.14-rc1, v4.13, v4.13-rc7, v4.13-rc6, v4.13-rc5, v4.13-rc4, v4.13-rc3, v4.13-rc2, v4.13-rc1, v4.12, v4.12-rc7, v4.12-rc6, v4.12-rc5, v4.12-rc4, v4.12-rc3, v4.12-rc2, v4.12-rc1, v4.11, v4.11-rc8, v4.11-rc7, v4.11-rc6, v4.11-rc5, v4.11-rc4, v4.11-rc3, v4.11-rc2, v4.11-rc1, v4.10, v4.10-rc8, v4.10-rc7, v4.10-rc6, v4.10-rc5, v4.10-rc4, v4.10-rc3, v4.10-rc2, v4.10-rc1, v4.9, v4.9-rc8 |
|
| #
c3396656 |
| 30-Nov-2016 |
Mauro Carvalho Chehab <[email protected]> |
docs-rst: parse-headers.pl: cleanup the documentation
Keeping both rst and in-file documentation in sync can be harsh.
So, simplify the script's internal documntation to a bare minimum, and add a m
docs-rst: parse-headers.pl: cleanup the documentation
Keeping both rst and in-file documentation in sync can be harsh.
So, simplify the script's internal documntation to a bare minimum, and add a mention to the ReST file with its full documentation.
This way, a quick help is still available at the command line, while the complete one is maintained at the ReST format.
As we won't be using pad2rst anymore, do a cleanup at the ReST file.
Signed-off-by: Mauro Carvalho Chehab <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
show more ...
|
|
Revision tags: v4.9-rc7, v4.9-rc6 |
|
| #
327f5a75 |
| 17-Nov-2016 |
Mauro Carvalho Chehab <[email protected]> |
parse-headers.pl: add documentation for this script
Provide a man page for parse-headers.pl, describing how to use it.
The documentation on ReST format was generated via pod2rst: http://search.cpa
parse-headers.pl: add documentation for this script
Provide a man page for parse-headers.pl, describing how to use it.
The documentation on ReST format was generated via pod2rst: http://search.cpan.org/~dowens/Pod-POM-View-Restructured-0.02/bin/pod2rst
Signed-off-by: Mauro Carvalho Chehab <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
show more ...
|
|
Revision tags: v4.9-rc5, v4.9-rc4, v4.9-rc3, v4.9-rc2, v4.9-rc1, v4.8, v4.8-rc8, v4.8-rc7, v4.8-rc6, v4.8-rc5 |
|
| #
22c40033 |
| 31-Aug-2016 |
Mauro Carvalho Chehab <[email protected]> |
[media] docs-rst: parse-headers.pl: use the C domain for cross-references
Instead of keep using the normal reference, move to the C domain ones. Using C domains everywhere will allow cross-reference
[media] docs-rst: parse-headers.pl: use the C domain for cross-references
Instead of keep using the normal reference, move to the C domain ones. Using C domains everywhere will allow cross-references between kAPI and uAPI docs.
Acked-by: Jonathan Corbet <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
bcec7c21 |
| 31-Aug-2016 |
Mauro Carvalho Chehab <[email protected]> |
[media] docs-rst: parse-headers.pl: make debug a command line option
Add a parser for the --debug option, in order to allow seeing what the parser is doing.
Acked-by: Jonathan Corbet <[email protected]
[media] docs-rst: parse-headers.pl: make debug a command line option
Add a parser for the --debug option, in order to allow seeing what the parser is doing.
Acked-by: Jonathan Corbet <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
|
Revision tags: v4.8-rc4, v4.8-rc3 |
|
| #
999d998e |
| 16-Aug-2016 |
Mauro Carvalho Chehab <[email protected]> |
docs-rst: parse-heraders.pl: escape LaTeX characters
Let's escape the LaTeX characters, to avoid troubles when outputing them.
Signed-off-by: Mauro Carvalho Chehab <[email protected]> Signed
docs-rst: parse-heraders.pl: escape LaTeX characters
Let's escape the LaTeX characters, to avoid troubles when outputing them.
Signed-off-by: Mauro Carvalho Chehab <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]>
show more ...
|
|
Revision tags: v4.8-rc2, v4.8-rc1, v4.7, v4.7-rc7 |
|
| #
fb6fc6c9 |
| 09-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: remove trailing spaces
The function that replace references add a "\ " at the end of references, to avoid the ReST markup parser to not identify them as references. That work
doc-rst: parse-headers: remove trailing spaces
The function that replace references add a "\ " at the end of references, to avoid the ReST markup parser to not identify them as references. That works fine except for the end of lines, as a sequence of { '\', ' ', '\n' } characters makes Sphinx to ignore the end of line. So, strip those escape/spaces at the end of lines.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
153234c4 |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: don't do substituition references
Add one extra escape character to avoid those warnings: Documentation/linux_tv/videodev2.h.rst:6: WARNING: Inline substitution_reference st
doc-rst: parse-headers: don't do substituition references
Add one extra escape character to avoid those warnings: Documentation/linux_tv/videodev2.h.rst:6: WARNING: Inline substitution_reference start-string without end-string.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
526b8848 |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: add an option to ignore enum symbols
At videodev2.h, we have hundreds of symbols that don't currently have a reference yet. Let's ignore for how, while we don't improve those
doc-rst: parse-headers: add an option to ignore enum symbols
At videodev2.h, we have hundreds of symbols that don't currently have a reference yet. Let's ignore for how, while we don't improve those cross-refs.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
034e6c8e |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: better handle comments at the source code
We should not let comments to mangle with the symbols parsing. Unfortunately, videodev2.h has lots of those in the middle of enums a
doc-rst: parse-headers: better handle comments at the source code
We should not let comments to mangle with the symbols parsing. Unfortunately, videodev2.h has lots of those in the middle of enums and structs. So, we need to improve our parser to discard them.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
4ff916a0 |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: fix multiline typedef handler
The typedef handler should do two things to be generic: 1) parse typedef enums; 2) accept both possible syntaxes: typedef struct foo { ..
doc-rst: parse-headers: fix multiline typedef handler
The typedef handler should do two things to be generic: 1) parse typedef enums; 2) accept both possible syntaxes: typedef struct foo { .. } foo_t; typedef struct { .. } foo_t;
Unfortunately, this is needed to parse some legacy DVB files, like dvb/audio.h.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
6c4c7dad |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: better handle typedefs
When typedef is used on its multiline format, we need to also parse enum and struct in the same line.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-
doc-rst: parse-headers: better handle typedefs
When typedef is used on its multiline format, we need to also parse enum and struct in the same line.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
9c80c745 |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: be more formal about the valid symbols
Be more formal about the valid symbols that are expected by the parser, to match what c language expects.
Signed-off-by: Mauro Carvalh
doc-rst: parse-headers: be more formal about the valid symbols
Be more formal about the valid symbols that are expected by the parser, to match what c language expects.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
9afe5112 |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: fix parsing comments and '{' on a separate line
The dmx.h header has two things that causes the parser to break while handling enums: per-header enums and the '{' starts on a new line
Bot
doc-rst: fix parsing comments and '{' on a separate line
The dmx.h header has two things that causes the parser to break while handling enums: per-header enums and the '{' starts on a new line
Both makes the parser to get lexical marks to be detected as if they were symbols.
Fix it.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
7d95fa8d |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-dst: parse-headers: highlight deprecated comments
When something is deprecated, highlight it, as we want it to be clearer to the reader.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensour
doc-dst: parse-headers: highlight deprecated comments
When something is deprecated, highlight it, as we want it to be clearer to the reader.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
6fe79d1e |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: parse-headers: improve delimiters to detect symbols
As we had to escape the symbols for the ReST markup to not do the wrong thing, the logic to discover start/end of strings are not trivial
doc-rst: parse-headers: improve delimiters to detect symbols
As we had to escape the symbols for the ReST markup to not do the wrong thing, the logic to discover start/end of strings are not trivial. Improve the end delimiter detection, in order to highlight more occurrences of the strings.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|
| #
dabf8be3 |
| 07-Jul-2016 |
Mauro Carvalho Chehab <[email protected]> |
doc-rst: add parse-headers.pl script
This script parses a header file and converts it into a parsed-literal block, creating references for ioctls, defines, typedefs, enums and structs.
It also allo
doc-rst: add parse-headers.pl script
This script parses a header file and converts it into a parsed-literal block, creating references for ioctls, defines, typedefs, enums and structs.
It also allow an external file to modify the rules, in order to fix the expressions.
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
show more ...
|