Commit dba89d1b authored by Linus Torvalds's avatar Linus Torvalds
Browse files

Merge tag 'docs-6.9-2' of git://git.lwn.net/linux 

Pull more documentation updates from Jonathan Corbet:
 "A handful of late-arriving documentation fixes and enhancements"

* tag 'docs-6.9-2' of git://git.lwn.net/linux:
  docs: verify/bisect: remove a level of indenting
  docs: verify/bisect: drop 'v' prefix, EOL aspect, and assorted fixes
  docs: verify/bisect: check taint flag
  docs: verify/bisect: improve install instructions
  docs: handling-regressions.rst: Update regzbot command fixed-by to fix
  docs: *-regressions.rst: Add colon to regzbot commands
  doc: Fix typo in admin-guide/cifs/introduction.rst
  README: Fix spelling
parents a4145ce1 b8cfda5c

Documentation/admin-guide/cifs/introduction.rst

+1 −1
Original line number Diff line number Diff line
@@ -28,7 +28,7 @@ Introduction 
  high performance safe distributed caching (leases/oplocks), optional packet

  signing, large files, Unicode support and other internationalization

  improvements. Since both Samba server and this filesystem client support the

  CIFS Unix extensions, and the Linux client also suppors SMB3 POSIX extensions,

  CIFS Unix extensions, and the Linux client also supports SMB3 POSIX extensions,

  the combination can provide a reasonable alternative to other network and

  cluster file systems for fileserving in some Linux to Linux environments,

  not just in Linux to Windows (or Linux to Mac) environments.

Documentation/admin-guide/reporting-regressions.rst

+1 −1
Original line number Diff line number Diff line
@@ -31,7 +31,7 @@ The important bits (aka "TL;DR") 
   Linux kernel regression tracking bot "regzbot" track the issue by specifying

   when the regression started like this::



       #regzbot introduced v5.13..v5.14-rc1

       #regzbot introduced: v5.13..v5.14-rc1





All the details on Linux kernel regressions relevant for users

Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst

+211 −178

File changed.

Preview size limit exceeded, changes collapsed.

Documentation/process/handling-regressions.rst

+6 −6
Original line number Diff line number Diff line
@@ -27,11 +27,11 @@ The important bits (aka "The TL;DR") 
   is optional, but recommended):



    * For mailed reports, check if the reporter included a line like ``#regzbot

      introduced v5.13..v5.14-rc1``. If not, send a reply (with the regressions

      introduced: v5.13..v5.14-rc1``. If not, send a reply (with the regressions

      list in CC) containing a paragraph like the following, which tells regzbot

      when the issue started to happen::



       #regzbot ^introduced 1f2e3d4c5b6a

       #regzbot ^introduced: 1f2e3d4c5b6a



    * When forwarding reports from a bug tracker to the regressions list (see

      above), include a paragraph like the following::
@@ -79,7 +79,7 @@ When doing either, consider making the Linux kernel regression tracking bot 
"regzbot" immediately start tracking the issue:



 * For mailed reports, check if the reporter included a "regzbot command" like

   ``#regzbot introduced 1f2e3d4c5b6a``. If not, send a reply (with the

   ``#regzbot introduced: 1f2e3d4c5b6a``. If not, send a reply (with the

   regressions list in CC) with a paragraph like the following:::



       #regzbot ^introduced: v5.13..v5.14-rc1
@@ -398,9 +398,9 @@ By using a 'regzbot command' in a direct or indirect reply to the mail with the 
regression report. These commands need to be in their own paragraph (IOW: they

need to be separated from the rest of the mail using blank lines).



One such command is ``#regzbot introduced <version or commit>``, which makes

One such command is ``#regzbot introduced: <version or commit>``, which makes

regzbot consider your mail as a regressions report added to the tracking, as

already described above; ``#regzbot ^introduced <version or commit>`` is another

already described above; ``#regzbot ^introduced: <version or commit>`` is another

such command, which makes regzbot consider the parent mail as a report for a

regression which it starts to track.
@@ -432,7 +432,7 @@ or itself is a reply to that mail: 
 * Mark a regression as fixed by a commit that is heading upstream or already

   landed::



       #regzbot fixed-by: 1f2e3d4c5d

       #regzbot fix: 1f2e3d4c5d



 * Mark a regression as a duplicate of another one already tracked by regzbot::

README

+1 −1
Original line number Diff line number Diff line
@@ -11,7 +11,7 @@ In order to build the documentation, use ``make htmldocs`` or 
    https://www.kernel.org/doc/html/latest/



There are various text files in the Documentation/ subdirectory,

several of them using the ReStructured Text markup notation.

several of them using the reStructuredText markup notation.



Please read the Documentation/process/changes.rst file, as it contains the

requirements for building and running the kernel, and information about