| /openbmc/openbmc/poky/meta/recipes-devtools/perl/files/ |
| H A D | perl-rdepends.txt | 22 RDEPENDS:perl-module-anydbm-file += "perl-module-warnings"
36 RDEPENDS:perl-module-app-cpan += "perl-module-warnings"
45 RDEPENDS:perl-module-app-prove += "perl-module-warnings"
53 RDEPENDS:perl-module-app-prove-state += "perl-module-warnings"
57 RDEPENDS:perl-module-app-prove-state-result += "perl-module-warnings"
59 RDEPENDS:perl-module-app-prove-state-result-test += "perl-module-warnings"
66 RDEPENDS:perl-module-archive-tar-constant += "perl-module-warnings"
84 RDEPENDS:perl-module-attribute-handlers += "perl-module-warnings"
87 RDEPENDS:perl-module-attributes += "perl-module-warnings"
94 RDEPENDS:perl-module-autodie-exception += "perl-module-warnings"
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl/ |
| H A D | libtest-warnings-perl_0.033.bb | 1 SUMMARY = "Test::Warnings - Test for warnings and the lack of them"
3 warnings generated by your tests, combined with the convenience of \
6 be calculated *before* the warnings test is run, resulting in a TAP error. \
9 HOMEPAGE = "https://github.com/karenetheridge/Test-Warnings"
10 BUGTRACKER = "https://rt.cpan.org/Public/Dist/Display.html?Name=Test-Warnings"
16 SRC_URI = "${CPAN_MIRROR}/authors/id/E/ET/ETHER/Test-Warnings-${PV}.tar.gz"
20 S = "${WORKDIR}/Test-Warnings-${PV}"
|
| /openbmc/u-boot/tools/patman/ |
| H A D | checkpatch.py | 51 warnings: Number of warnings
56 fields = ['ok', 'problems', 'errors', 'warnings', 'checks', 'lines',
70 # total: 0 errors, 0 warnings, 159 lines checked
72 # total: 0 errors, 2 warnings, 7 checks, 473 lines checked
73 re_stats = re.compile('total: (\\d+) errors, (\d+) warnings, (\d+)')
74 re_stats_full = re.compile('total: (\\d+) errors, (\d+) warnings, (\d+)'
96 result.warnings = int(match.group(2))
151 warning_count += result.warnings
153 print('%d errors, %d warnings, %d checks for %s:' % (result.errors,
154 result.warnings, result.checks, col.Color(col.BLUE, fname)))
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-extended/mdadm/files/ |
| H A D | 0001-Use-CC-to-check-for-implicit-fallthrough-warning-sup.patch | 24 - FALLTHROUGH := $(shell gcc -Q --help=warnings 2>&1 | grep "implicit-fallthrough" | wc -l)
25 + FALLTHROUGH := $(shell ${CC} -Q --help=warnings 2>&1 | grep "implicit-fallthrough" | wc -l)
32 - FORMATOVERFLOW := $(shell gcc -Q --help=warnings 2>&1 | grep "format-overflow" | wc -l)
33 + FORMATOVERFLOW := $(shell ${CC} -Q --help=warnings 2>&1 | grep "format-overflow" | wc -l)
40 - STRINGOPOVERFLOW := $(shell gcc -Q --help=warnings 2>&1 | grep "stringop-overflow" | wc -l)
41 + STRINGOPOVERFLOW := $(shell ${CC} -Q --help=warnings 2>&1 | grep "stringop-overflow" | wc -l)
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | logging.yml | 1 # Python logging configuration to write all warnings to a separate file
5 warnings:
8 filename: warnings.log
13 handlers: [warnings]
|
| /openbmc/linux/Documentation/process/ |
| H A D | maintainer-soc-clean-dts.rst | 18 new ``make dtbs_check W=1`` warnings. Warnings in a new board DTS, which are
20 warnings. The platform maintainers have automation in place which should point
21 out any new warnings.
23 If a commit introducing new warnings gets accepted somehow, the resulting
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libtest/ |
| H A D | libtest-nowarnings-perl_1.04.bb | 1 SUMMARY = "Make sure you didn't emit any warnings while testing"
2 DESCRIPTION = "In general, your tests shouldn't produce warnings. This \
3 modules causes any warnings to be captured and stored. It automatically \
5 were no warnings. If there were any warings, the test will give a \\"not ok\\" \
9 If some of your tests are supposed to produce warnings then you should \
|
| /openbmc/linux/scripts/ |
| H A D | Makefile.extrawarn | 9 # Default set of warnings, always enabled
38 # These warnings generated too much noise in a regular build.
49 # disable pointer signed / unsigned warnings in gcc 4.0
58 # warnings for bounds checks involving those possible values. While
61 # warnings are produced (?!). Using -Walloc-size-larger-than=SIZE_MAX
93 # W=1 - warnings which may be relevant and do not occur too often
153 # W=2 - warnings which occur quite often but may still be relevant
173 # The following turn off the warnings enabled by -Wextra
187 # W=3 - more obscure warnings, can most likely be ignored
207 # The following turn off the warnings enabled by -Wextra
[all …]
|
| /openbmc/linux/Documentation/doc-guide/ |
| H A D | contributing.rst | 30 Addressing warnings
34 warnings. When you have that many, you might as well have none at all;
36 ones. For this reason, eliminating warnings is one of the highest-priority
41 Warnings issued by a compiler for C code can often be dismissed as false
43 Warnings from the documentation build almost always point at a real
44 problem; making those warnings go away requires understanding the problem
46 warnings should probably not say "fix a warning" in the changelog title;
49 Another important point is that documentation warnings are often created by
51 maintainer appreciates being copied on fixes for these warnings, the
55 For example, in a documentation build I grabbed a pair of warnings nearly
[all …]
|
| /openbmc/linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | parse-build.sh | 38 grep warning: < $F > $T/warnings
39 grep "include/linux/*rcu*\.h:" $T/warnings > $T/hwarnings
40 grep "kernel/rcu/[^/]*:" $T/warnings > $T/cwarnings
41 grep "^ld: .*undefined reference to" $T/warnings | head -1 > $T/ldwarnings
|
| H A D | kvm-test-1-run-qemu.sh | 110 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
111 grep "^(qemu) qemu:" $resdir/kvm-test-1-run*.sh.out >> $resdir/Warnings 2>&1
112 …ed -n "s/^(qemu) qemu: terminating on signal [0-9]* from pid \([0-9]*\).*$/\1/p" $resdir/Warnings`"
115 echo "ps -fp $killpid" >> $resdir/Warnings 2>&1
116 ps -fp $killpid >> $resdir/Warnings 2>&1
139 echo "PID $qemu_pid killed due to run STOP.1 request `date`" >> $resdir/Warnings 2>&1
171 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds `date`" >> $resdir/Warnings 2>&1
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | builddashboard.html | 25 {% if build.warnings.count or build.errors.count %}
32 {% if build.warnings.count %}
34 …<a href="#warnings" class="show-warnings"> {{build.warnings.count}} warning{{build.warnings.count|…
281 {% if build.warnings.count %}
282 <div class="panel panel-default" id="warnings">
286 …le" href="#warning-info" data-toggle="collapse">{{build.warnings.count}} warning{{build.warnings.c…
307 //show warnings section when requested from the previous page
308 if (location.href.search('#warnings') > -1) {
312 //show warnings section when requested from the build outcome
313 $(".show-warnings").click(function() {
|
| /openbmc/linux/tools/testing/selftests/kvm/x86_64/ |
| H A D | mmio_warning_test.c | 81 int warnings; in get_warnings_count() local
85 if (fscanf(f, "%d", &warnings) < 1) in get_warnings_count()
86 warnings = 0; in get_warnings_count()
89 return warnings; in get_warnings_count()
118 "Warnings found in kernel. Run 'dmesg' to inspect them."); in main()
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libstrictures/ |
| H A D | libstrictures-perl_2.000006.bb | 1 SUMMARY = "strictures - turn on strict and make all warnings fatal"
6 warnings on but don't make them fatal -- which from my point of view is \
7 useless because I want an exception to tell me my code isn't warnings-clean. \
42 perl-module-warnings \
|
| /openbmc/openbmc/poky/bitbake/lib/bs4/ |
| H A D | __init__.py | 30 import warnings
63 # Define some custom warnings.
177 warnings.warn(
184 warnings.warn(
191 warnings.warn(
198 warnings.warn(
205 warnings.warn(
213 warnings.warn(
228 …warnings.warn("You provided Unicode markup but also provided a value for from_encoding. Your from_…
271 # This code adapted from warnings.py so that we get the same line
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | dqblk_xfs.h | 68 __u16 d_iwarns; /* # warnings issued wrt num inodes */
69 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
78 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
108 * warnings are set/cleared by the administrators (or automatically by going
175 __u16 qs_bwarnlimit; /* limit for num warnings */
176 __u16 qs_iwarnlimit; /* limit for num warnings */
220 __u16 qs_bwarnlimit; /* limit for num warnings */
221 __u16 qs_iwarnlimit; /* limit for num warnings */
222 __u16 qs_rtbwarnlimit;/* limit for rt blks warnings */
|
| /openbmc/linux/tools/verification/rv/ |
| H A D | Makefile | 69 .PHONY: all warnings show_warnings
70 all: warnings rv
74 WARNINGS = show_warnings macro
82 WARNINGS = show_warnings macro
107 ifneq ("$(WARNINGS)", "")
110 warnings: $(WARNINGS) target
|
| /openbmc/linux/tools/testing/ktest/examples/include/ |
| H A D | patchcheck.conf | 56 # Instead of just checking for warnings to files that are changed
57 # it can be advantageous to check for any new warnings. If a
59 # touched by the commit. To detect these kinds of warnings, you
65 # warnings file.
74 # and record all the warnings that exist before the patches
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | stallwarn.rst | 13 What Causes RCU CPU Stall Warnings?
18 warnings:
77 RCU CPU stall warnings.
80 timeout down to just barely avoid RCU CPU stall warnings, and then
88 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
115 of RCU CPU stall warnings, eventually leading the realization
119 CPU stall warning. Note that SRCU does *not* have CPU stall warnings.
121 in progress. No grace period, no CPU stall warnings.
125 If you have a series of stall warnings from a single extended stall,
199 own warnings, as this often gives better-quality stack traces.
[all …]
|
| /openbmc/linux/tools/tracing/rtla/ |
| H A D | Makefile | 69 .PHONY: all warnings show_warnings
70 all: warnings rtla
74 WARNINGS = show_warnings macro
82 WARNINGS = show_warnings macro
107 ifneq ("$(WARNINGS)", "")
110 warnings: $(WARNINGS) target
|
| /openbmc/phosphor-networkd/src/ |
| H A D | config_parser.cpp | 153 std::vector<std::string> warnings; member
165 warnings.emplace_back(std::format("{}:{}: Section missing ]", in pumpSection()
174 warnings.emplace_back( in pumpSection()
210 warnings.insert(warnings.end(), in pumpKV()
270 parse.warnings.emplace_back( in setFile()
277 this->warnings = std::move(parse.warnings); in setFile()
|
| /openbmc/linux/drivers/base/test/ |
| H A D | test_async_driver_probe.c | 21 static atomic_t warnings, errors, timeout, async_completed; variable
51 atomic_inc(&warnings); in test_probe()
240 * Otherwise if they completed without errors or warnings then in test_async_probe_init()
247 } else if (!atomic_read(&errors) && !atomic_read(&warnings)) { in test_async_probe_init()
267 * errors or warnings being reported by the probe routine. in test_async_probe_init()
274 pr_err("Test failed with %d errors and %d warnings\n", in test_async_probe_init()
275 atomic_read(&errors), atomic_read(&warnings)); in test_async_probe_init()
|
| /openbmc/linux/lib/ |
| H A D | debugobjects.c | 1035 seq_printf(m, "warnings :%d\n", debug_objects_warnings); in debug_stats_show()
1163 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1189 if (warnings != debug_objects_warnings) { in check_results()
1190 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1191 warnings, debug_objects_warnings); in check_results()
1215 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1221 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1225 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1228 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1231 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
|
| /openbmc/linux/tools/power/acpi/ |
| H A D | Makefile.config | 64 WARNINGS := -Wall
65 WARNINGS += $(call cc-supports,-Wstrict-prototypes)
66 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
71 CFLAGS += $(WARNINGS)
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/abseil-cpp/abseil-cpp/ |
| H A D | 0005-Don-t-match-Wnon-virtual-dtor-in-the-flags-are-neede.patch | 5 suppress warnings in headers". It should fall through to the "don't impose
6 our warnings on others" case. Do this by matching on "-Wno-*" instead of
28 # These flags are needed to suppress warnings that might fire in our headers.
|