Lines Matching +full:80 +full:a

7 The media subsystem covers support for a variety of devices: stream
33 maintainership model is to have sub-maintainers that have a broad
34 knowledge of a specific aspect of the subsystem. It is the sub-maintainers'
44 Media's workflow is heavily based on Patchwork, meaning that, once a patch
46 server, and, after a while, it should appear at:
50 If it doesn't automatically appear there after a few minutes, then
66 At the media subsystem, we have a group of senior developers that
69 subsystem as a whole. For core changes, whenever possible, multiple
92 Media maintainers may delegate a patch to other media maintainers as needed.
94 responsible for reviewing a patch.
104 There is a set of compliance tools at https://git.linuxtv.org/v4l-utils.git/
134 Be sure to not introduce new warnings on your patches without a
145 or at least be grouped per directory. So, for example, if you're doing a
146 big cleanup change set at drivers under drivers/media, please send a single
156 	$ ./scripts/checkpatch.pl --strict --max-line-length=80
163 a few cases, ``checkpatch.pl`` may actually point to something that would
167 to having longer lines than 80 characters per line. While this is not
168 strictly prohibited, efforts should be made towards staying within 80
173 In particular, we accept lines with more than 80 columns:
176     - when a function or variable name need to have a big identifier name,
177       which keeps hard to honor the 80 columns limit;
180     - when they avoid a line to end with an open parenthesis or an open
194 be sooner or later handled, so you don't need to re-submit a patch.
199 Please notice that the media subsystem is a high traffic one, so it
200 could take a while for us to be able to review your patches. Feel free
201 to ping if you don't get a feedback in a couple of weeks or to ask
205 Please note that we expect a detailed description for ``Tested-by:``,