diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-10-18 10:12:27 -0200 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-10-24 08:12:35 -0200 |
| commit | 8c27ceff3604b249a9efafbd1bd8b141b79e619d (patch) | |
| tree | 82e4ab0c2825fa25c3168e648268883c0b23ee30 /Documentation/admin-guide/reporting-bugs.rst | |
| parent | 9d85025b0418163fae079c9ba8f8445212de8568 (diff) | |
| download | talos-obmc-linux-8c27ceff3604b249a9efafbd1bd8b141b79e619d.tar.gz talos-obmc-linux-8c27ceff3604b249a9efafbd1bd8b141b79e619d.zip | |
docs: fix locations of several documents that got moved
The previous patch renamed several files that are cross-referenced
along the Kernel documentation. Adjust the links to point to
the right places.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'Documentation/admin-guide/reporting-bugs.rst')
| -rw-r--r-- | Documentation/admin-guide/reporting-bugs.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/admin-guide/reporting-bugs.rst b/Documentation/admin-guide/reporting-bugs.rst index 05c53ac7fa76..0c0f2698ec5a 100644 --- a/Documentation/admin-guide/reporting-bugs.rst +++ b/Documentation/admin-guide/reporting-bugs.rst @@ -61,7 +61,7 @@ files to the get_maintainer.pl script:: If it is a security bug, please copy the Security Contact listed in the MAINTAINERS file. They can help coordinate bugfix and disclosure. See -:ref:`Documentation/SecurityBugs <securitybugs>` for more information. +:ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` for more information. If you can't figure out which subsystem caused the issue, you should file a bug in kernel.org bugzilla and send email to @@ -94,7 +94,7 @@ step-by-step instructions for how a user can trigger the bug. If the failure includes an "OOPS:", take a picture of the screen, capture a netconsole trace, or type the message from your screen into the bug -report. Please read "Documentation/oops-tracing.txt" before posting your +report. Please read "Documentation/admin-guide/oops-tracing.rst" before posting your bug report. This explains what you should do with the "Oops" information to make it useful to the recipient. @@ -120,7 +120,7 @@ summary from [1.]>" for easy identification by the developers:: [4.2.] Kernel .config file: [5.] Most recent kernel version which did not have the bug: [6.] Output of Oops.. message (if applicable) with symbolic information - resolved (see Documentation/oops-tracing.txt) + resolved (see Documentation/admin-guide/oops-tracing.rst) [7.] A small shell script or example program which triggers the problem (if possible) [8.] Environment |
