diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2019-09-07 11:48:28 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-09-07 11:48:28 -0700 |
| commit | b3a9964cfa690150e49ae75ba16416ccaac3a8ba (patch) | |
| tree | 6a3c23f9efbe81afa4e4a754bd905f86248c5cf8 | |
| parent | d3464ccd105b42f87302572ee1f097e6e0b432c6 (diff) | |
| parent | a8e0abae2fe0e788fa3d92c043605d1211c13735 (diff) | |
| download | linux-b3a9964cfa690150e49ae75ba16416ccaac3a8ba.tar.bz2 | |
Merge tag 'char-misc-5.3-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc
Pull Documentation updates from Greg KH:
"A few small patches for the documenation file that came in through the
char-misc tree in -rc7 for your tree.
They fix the mistake in the .rst format that kept the table of
companies from showing up in the html output, and most importantly,
add people's names to the list showing support for our process"
* tag 'char-misc-5.3-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
Documentation/process: Add Qualcomm process ambassador for hardware security issues
Documentation/process/embargoed-hardware-issues: Microsoft ambassador
Documentation/process: Add Google contact for embargoed hardware issues
Documentation/process: Volunteer as the ambassador for Xen
| -rw-r--r-- | Documentation/process/embargoed-hardware-issues.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst index d37cbc502936..402636356fbe 100644 --- a/Documentation/process/embargoed-hardware-issues.rst +++ b/Documentation/process/embargoed-hardware-issues.rst @@ -5,7 +5,7 @@ Scope ----- Hardware issues which result in security problems are a different category -of security bugs than pure software bugs which only affect the Linux +of security bugs than pure software bugs which only affect the Linux kernel. Hardware issues like Meltdown, Spectre, L1TF etc. must be treated @@ -159,7 +159,7 @@ Mitigation development The initial response team sets up an encrypted mailing-list or repurposes an existing one if appropriate. The disclosing party should provide a list -of contacts for all other parties who have already been, or should be +of contacts for all other parties who have already been, or should be, informed about the issue. The response team contacts these parties so they can name experts who should be subscribed to the mailing-list. @@ -217,11 +217,11 @@ an involved disclosed party. The current ambassadors list: AMD IBM Intel - Qualcomm + Qualcomm Trilok Soni <tsoni@codeaurora.org> - Microsoft + Microsoft Sasha Levin <sashal@kernel.org> VMware - XEN + Xen Andrew Cooper <andrew.cooper3@citrix.com> Canonical Tyler Hicks <tyhicks@canonical.com> Debian Ben Hutchings <ben@decadent.org.uk> @@ -230,8 +230,8 @@ an involved disclosed party. The current ambassadors list: SUSE Jiri Kosina <jkosina@suse.cz> Amazon - Google - ============== ======================================================== + Google Kees Cook <keescook@chromium.org> + ============= ======================================================== If you want your organization to be added to the ambassadors list, please contact the hardware security team. The nominated ambassador has to |