| /openbmc/openbmc-test-automation/test_lists/ |
| H A D | skip_test_palmetto | 1 # https://github.com/openbmc/openbmc/issues/93
4 # https://github.com/openbmc/openbmc-test-automation/issues/207
6 # https://github.com/openbmc/openbmc-test-automation/issues/123
14 # https://github.com/openbmc/openbmc/issues/901
16 # https://github.com/openbmc/openbmc/issues/1142
18 # https://github.com/openbmc/openbmc-test-automation/issues/396
28 # https://github.com/openbmc/openbmc-test-automation/issues/546
38 # https://github.com/openbmc/openbmc-test-automation/issues/729
49 # https://github.com/openbmc/openbmc-test-automation/issues/1411
|
| /openbmc/openbmc/poky/bitbake/lib/bb/tests/fetch-testdata/apple/cups/ |
| H A D | releases | 531 …ected-links="repo_issues repo_labels repo_milestones /apple/cups/issues" href="/apple/cups/issues">
533 <span itemprop="name">Issues</span>
580 …ected-links="repo_issues repo_labels repo_milestones /apple/cups/issues" href="/apple/cups/issues">
581 <span itemprop="name">Issues</span>
731 …issues/5661" data-hovercard-type="issue" data-hovercard-url="/apple/cups/issues/5661/hovercard" hr…
734 …on-text="Issue title is private" data-url="https://github.com/apple/cups/issues/5621" data-hoverca…
736 …e/cups/issues/5633" data-hovercard-type="issue" data-hovercard-url="/apple/cups/issues/5633/hoverc…
737 …e/cups/issues/5639" data-hovercard-type="issue" data-hovercard-url="/apple/cups/issues/5639/hoverc…
738 …e/cups/issues/5640" data-hovercard-type="issue" data-hovercard-url="/apple/cups/issues/5640/hoverc…
740 …on-text="Issue title is private" data-url="https://github.com/apple/cups/issues/5643" data-hoverca…
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/classes/ |
| H A D | bandit.bbclass | 1 # Class to scan Python code for security issues, using Bandit.
6 # No output if no issues found, a warning if issues found.
25 # Whether Bandit finding issues results in a warning (0) or an error (1).
41 bb.note("Bandit found no issues (report written to %s)" % report)
45 bb.error("Bandit found issues (report written to %s)" % report)
47 bb.warn("Bandit found issues (report written to %s)" % report)
|
| /openbmc/docs/tof/ |
| H A D | contract.md | 10 handling and enforcement of subproject maintainer issues, and many other
31 for ignoring well-reasoned issues.
35 Issues the TOF handle include:
67 ## Github issues
69 The TOF tracks any ongoing decisions using GitHub issues in the
70 [TOF repository](https://github.com/openbmc/technical-oversight-forum/issues).
71 Issues can be opened by anyone, including TOF members themselves. Issues can be
122 private, using the same process as public issues.
|
| /openbmc/linux/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues
9 Hardware issues which result in security problems are a different category
13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
16 hardware vendors and other parties. For some of the issues, software
29 issues. Reports of pure software security bugs in the Linux kernel are not
46 While hardware security issues are often handled by the affected hardware
79 is aware of the sensitive nature of such issues and offers a Memorandum of
87 keep hardware security issues under embargo for coordination between
91 issues in the past and has the necessary mechanisms in place to allow
95 initial contact, which oversees the process of handling such issues under
[all …]
|
| H A D | stable-api-nonsense.rst | 45 First off, I'm not going to address **any** legal issues about closed
50 the technical issues here (not to make light of the legal issues, they
84 Now a number of these issues can be addressed by simply compiling your
120 issues:
146 Security issues are also very important for Linux. When a
|
| /openbmc/openbmc-test-automation/tools/ |
| H A D | github_issues_to_csv | 4 Exports issues from a list of repositories to individual CSV files.
5 Uses basic authentication (GitHub username + password) to retrieve issues
69 Requests issues from GitHub API and writes to CSV file.
100 description="Write GitHub repository issues to CSV file."
114 "--all", action="store_true", help="Returns both open and closed issues."
133 csvfilename = csvfilename + "-issues.csv"
150 l_url = "https://api.github.com/repos/{}/issues?state={}"
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | contributing.md | 30 the issues in the first part)
93 ## GitHub issues
95 In order to manage and track the layer issues more efficiently, the
96 GitHub issues facility is used by this project:
98 * <https://github.com/agherzan/meta-raspberrypi/issues>
102 "Signed-off-by" tag to close the relevant issues automatically:
112 * <https://help.github.com/articles/closing-issues-using-keywords>
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | release-notes.rst | 32 Known Issues or Limitations
61 Known Issues or Limitations
82 Known Issues or Limitations
105 Known Issues or Limitations
110 - Below SCT FAILURE is a known issues in the FVP:
130 Known Issues or Limitations
136 - Below SCT FAILURE is a known issues in the FVP:
149 Known Issues or Limitations
163 Known Issues or Limitations
177 Known Issues or Limitations
[all …]
|
| /openbmc/openbmc/meta-arm/ |
| H A D | SECURITY.md | 3 Arm takes security issues seriously and welcomes feedback from researchers and
6 vulnerabilities and other security issues.
8 Security issues can be complex and one single timescale doesn't fit all
37 significant issues.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 4 Reporting issues
40 If you are facing multiple issues with the Linux kernel at once, report each
51 Step-by-step guide how to report issues to the kernel maintainers
54 The above TL;DR outlines roughly how to report issues to the Linux kernel
56 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For
72 will often be needed anyway to hunt down and fix issues.
80 issue, or a really severe problem: those are 'issues of high priority' that
96 issues at once, create separate notes for each of them and make sure they
107 time this won't be bugzilla.kernel.org, as issues typically need to be sent
129 up there, scroll down to the instructions for issues only happening with
[all …]
|
| /openbmc/webui-vue/ |
| H A D | CONTRIBUTING.md | 91 [existing GitHub issues](https://github.com/openbmc/webui-vue/issues) to see if
93 [Bug report template](https://github.com/openbmc/webui-vue/issues/new?assignees=&labels=&template=b…
97 [existing GitHub issues](https://github.com/openbmc/webui-vue/issues). If no one
99 [Feature request template](https://github.com/openbmc/webui-vue/issues/new?assignees=&labels=&templ…
|
| /openbmc/docs/ |
| H A D | community-membership.md | 33 issues and reviews assigned to them, participate in design reviews through
44 - Filing or commenting on issues on GitHub
89 - May also review for more holistic issues, but not a requirement
128 - Providing results and insight to the community on platform-specific issues.
141 issues, interactions with other parts of the system, etc.
162 code/design/proposal review, coordinating on issues, etc.
211 - Initiating, contributing and resolving discussions (emails, GitHub issues,
213 - Identifying subtle or complex issues in designs and implementation reviews
258 changes and expectations (emails, GitHub issues, meetings)
259 - Identifying subtle or complex issues in designs and implementation that
|
| /openbmc/openbmc-tools/witherspoon-debug/ |
| H A D | debug | 44 # Tracking issue: https://github.com/openbmc/openbmc/issues/2880
46 # Fake expand(1): https://github.com/openbmc/openbmc/issues/2879
63 # Fix the broken objdump link: https://github.com/openbmc/openbmc/issues/2878
76 # https://github.com/openbmc/openbmc/issues/2430
|
| /openbmc/openbmc/poky/meta/recipes-support/libyaml/ |
| H A D | libyaml_0.2.5.bb | 21 …ks this is a misuse (or wrong use) of the libyaml API - https://github.com/yaml/libyaml/issues/303"
22 …m thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302"
23 …m thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302"
|
| /openbmc/qemu/scripts/ |
| H A D | clean-header-guards.pl | 154 my @issues = ();
156 and push @issues, "contains lowercase letters";
158 and push @issues, "is a reserved identifier";
160 and $& ne "_H" and push @issues, "doesn't end with _H";
170 push @issues, "doesn't match the file name";
172 if (@issues and $opt_v) {
174 join(", ", @issues), "\n";
|
| /openbmc/linux/tools/testing/selftests/rseq/ |
| H A D | compiler.h | 21 * https://github.com/llvm/llvm-project/issues/52735
23 * Work around these issues by adding a volatile inline asm with
26 * issues are found in the future.
|
| /openbmc/linux/drivers/media/pci/tw5864/ |
| H A D | tw5864-core.c | 33 * BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY
43 * There is a workaround for both issues: avoid P-frames by setting GOP size
48 * These issues are not decoding errors; all produced H.264 streams are decoded
50 * analog-to-digital conversion issues nor internal memory errors; we conclude
51 * it's internal H.264 encoder issues.
53 * worked properly at all in our development environment. So these issues may
299 dev_info(&pci_dev->dev, "Note: there are known video quality issues. For details\n"); in tw5864_initdev()
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
| H A D | deterministic_imports.patch | 6 There are two issues here. Firstly, the modules are accessed in on disk order. This
10 has caused a long string of different issues for us.
14 Upstream-Status: Submitted [https://github.com/python/cpython/issues/120492; need to first talk to …
|
| /openbmc/openbmc/poky/meta/recipes-devtools/jquery/ |
| H A D | jquery_3.7.1.bb | 22 # https://github.com/jquery/jquery/issues/3927
23 …E-2007-2379] = "upstream-wontfix: There are ways jquery can expose security issues but any issues \
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl-cross/files/ |
| H A D | determinism.patch | 8 Reported upstream: https://github.com/arsv/perl-cross/issues/87
12 Reported upstream: https://github.com/arsv/perl-cross/issues/88
20 Reported upstream: https://github.com/arsv/perl-cross/issues/87
|
| /openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
| H A D | question.md | 12 We do not field questions or feature requests by Github Issues!
18 Github Issues in openbmc/openbmc are for bugs only!
|
| /openbmc/linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.debug | 46 performance but will catch some internal issues.
139 performance but will catch some internal issues.
151 performance but will catch some internal issues.
164 performance but will help resolve GuC related issues.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl/files/ |
| H A D | determinism.patch | 8 Reported upstream: https://github.com/arsv/perl-cross/issues/87
12 Reported upstream: https://github.com/arsv/perl-cross/issues/88
20 Reported upstream: https://github.com/arsv/perl-cross/issues/87
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | security-subjects.rst | 8 and need to handle security issues and practices both internal (in the code
32 reporting potential security issues in the specific ``SECURITY.md`` file at the
50 for them for significant issues.
60 open list to discuss public security issues/patches and security-related
113 for. They do not share information about confidential issues outside of the team
117 added to individual issues only and adhere to the same standards as the YP
|