| Message ID | 51e941b6b028ed619dfa93e29ab0c2930050af5b.1567712829.git.mchehab+samsung@kernel.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | Address issues with SPDX requirements and PEP-263 | expand |
diff --git a/tools/power/x86/intel_pstate_tracer/intel_pstate_tracer.py b/tools/power/x86/intel_pstate_tracer/intel_pstate_tracer.py index 2d6d342b148f..1009be489f9a 100755 --- a/tools/power/x86/intel_pstate_tracer/intel_pstate_tracer.py +++ b/tools/power/x86/intel_pstate_tracer/intel_pstate_tracer.py @@ -1,6 +1,6 @@ #!/usr/bin/python +# -*- coding: utf-8; mode: python -*- # SPDX-License-Identifier: GPL-2.0-only -# -*- coding: utf-8 -*- # """ This utility can be used to debug and tune the performance of the intel_pstate driver. This utility can be used in two ways:
As stated at PEP-263, the coding tag should be at the first or second line. On those two scripts, the tag is at the wrong line. Place it at the right place and use the same kind of line that we're using on other python scripts that also work fine with emacs. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> --- tools/power/x86/intel_pstate_tracer/intel_pstate_tracer.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)