linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Adam Bratschi-Kaye <ark.email@gmail.com>,
	Alex Gaynor <alex.gaynor@gmail.com>,
	Boris-Chengbiao Zhou <bobo1239@web.de>, Daniel Xu <dxu@dxuuu.xyz>,
	Finn Behrens <me@kloenk.de>, Gary Guo <gary@garyguo.net>,
	Jonathan Corbet <corbet@lwn.net>, Julian Merkle <me@jvmerkle.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Miguel Ojeda <ojeda@kernel.org>,
	Sven Van Asbroeck <thesven73@gmail.com>,
	Wedson Almeida Filho <wedsonaf@google.com>,
	Wei Liu <wei.liu@kernel.org>, Wu XiangCheng <bobwxc@email.cn>,
	Yuki Okushi <jtitor@2k36.org>
Subject: linux-next: manual merge of the rust tree with Linus' tree
Date: Tue, 4 Oct 2022 19:05:02 +1100	[thread overview]
Message-ID: <20221004190502.4e7d3348@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 6020 bytes --]

Hi all,

Today's linux-next merge of the rust tree got a conflict in:

  Documentation/index.rst

between commit:

  0c7b4366f1ab ("docs: Rewrite the front page")

from the origin tree and commit:

  d07479b211b7 ("docs: add Rust documentation")

from the rust tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc Documentation/index.rst
index 85eab6e990ab,00722aa20cd7..000000000000
--- a/Documentation/index.rst
+++ b/Documentation/index.rst
@@@ -12,84 -18,134 +12,85 @@@ documents into a coherent whole.  Pleas
  documentation are welcome; join the linux-doc list at vger.kernel.org if
  you want to help out.
  
 -Licensing documentation
 ------------------------
 +Working with the development community
 +--------------------------------------
  
 -The following describes the license of the Linux kernel source code
 -(GPLv2), how to properly mark the license of individual files in the source
 -tree, as well as links to the full license text.
 -
 -* :ref:`kernel_licensing`
 -
 -User-oriented documentation
 ----------------------------
 -
 -The following manuals are written for *users* of the kernel — those who are
 -trying to get it to work optimally on a given system.
 +The essential guides for interacting with the kernel's development
 +community and getting your work upstream.
  
  .. toctree::
 -   :maxdepth: 2
 -
 -   admin-guide/index
 -   kbuild/index
 -
 -Firmware-related documentation
 -------------------------------
 -The following holds information on the kernel's expectations regarding the
 -platform firmwares.
 +   :maxdepth: 1
  
 -.. toctree::
 -   :maxdepth: 2
 +   process/development-process
 +   process/submitting-patches
 +   Code of conduct <process/code-of-conduct>
 +   maintainer/index
 +   All development-process docs <process/index>
  
 -   firmware-guide/index
 -   devicetree/index
  
 -Application-developer documentation
 ------------------------------------
 +Internal API manuals
 +--------------------
  
 -The user-space API manual gathers together documents describing aspects of
 -the kernel interface as seen by application developers.
 +Manuals for use by developers working to interface with the rest of the
 +kernel.
  
  .. toctree::
 -   :maxdepth: 2
 -
 -   userspace-api/index
 +   :maxdepth: 1
  
 +   core-api/index
 +   driver-api/index
 +   subsystem-apis
 +   Locking in the kernel <locking/index>
  
 -Introduction to kernel development
 -----------------------------------
 +Development tools and processes
 +-------------------------------
  
 -These manuals contain overall information about how to develop the kernel.
 -The kernel community is quite large, with thousands of developers
 -contributing over the course of a year.  As with any large community,
 -knowing how things are done will make the process of getting your changes
 -merged much easier.
 +Various other manuals with useful information for all kernel developers.
  
  .. toctree::
 -   :maxdepth: 2
 +   :maxdepth: 1
  
 -   process/index
 -   dev-tools/index
 +   process/license-rules
     doc-guide/index
 +   dev-tools/index
 +   dev-tools/testing-overview
     kernel-hacking/index
     trace/index
 -   maintainer/index
     fault-injection/index
     livepatch/index
+    rust/index
  
  
 -Kernel API documentation
 -------------------------
 +User-oriented documentation
 +---------------------------
  
 -These books get into the details of how specific kernel subsystems work
 -from the point of view of a kernel developer.  Much of the information here
 -is taken directly from the kernel source, with supplemental material added
 -as needed (or at least as we managed to add it — probably *not* all that is
 -needed).
 +The following manuals are written for *users* of the kernel — those who are
 +trying to get it to work optimally on a given system and application
 +developers seeking information on the kernel's user-space APIs.
  
  .. toctree::
 -   :maxdepth: 2
 +   :maxdepth: 1
  
 -   driver-api/index
 -   core-api/index
 -   locking/index
 -   accounting/index
 -   block/index
 -   cdrom/index
 -   cpu-freq/index
 -   fb/index
 -   fpga/index
 -   hid/index
 -   i2c/index
 -   iio/index
 -   isdn/index
 -   infiniband/index
 -   leds/index
 -   netlabel/index
 -   networking/index
 -   pcmcia/index
 -   power/index
 -   target/index
 -   timers/index
 -   spi/index
 -   w1/index
 -   watchdog/index
 -   virt/index
 -   input/index
 -   hwmon/index
 -   gpu/index
 -   security/index
 -   sound/index
 -   crypto/index
 -   filesystems/index
 -   mm/index
 -   bpf/index
 -   usb/index
 -   PCI/index
 -   scsi/index
 -   misc-devices/index
 -   scheduler/index
 -   mhi/index
 -   peci/index
 -
 -Architecture-agnostic documentation
 ------------------------------------
 +   admin-guide/index
 +   The kernel build system <kbuild/index>
 +   admin-guide/reporting-issues.rst
 +   User-space tools <tools/index>
 +   userspace-api/index
 +
 +See also: the `Linux man pages <https://www.kernel.org/doc/man-pages/>`_,
 +which are kept separately from the kernel's own documentation.
 +
 +Firmware-related documentation
 +------------------------------
 +The following holds information on the kernel's expectations regarding the
 +platform firmwares.
  
  .. toctree::
 -   :maxdepth: 2
 +   :maxdepth: 1
 +
 +   firmware-guide/index
 +   devicetree/index
  
 -   asm-annotations
  
  Architecture-specific documentation
  -----------------------------------

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-10-04  8:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  8:05 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-21  4:31 linux-next: manual merge of the rust tree with Linus' tree Stephen Rothwell
2025-07-21  8:23 ` Miguel Ojeda
2025-03-17 10:20 Stephen Rothwell
2025-03-17 19:37 ` Miguel Ojeda
2025-03-17 22:31   ` Stephen Rothwell
2025-03-17 22:35     ` Miguel Ojeda
2025-03-17 10:05 Stephen Rothwell
2025-03-17 19:36 ` Miguel Ojeda
2024-09-16  8:03 Stephen Rothwell
2024-09-16  8:12 ` Miguel Ojeda
2022-09-12  7:24 Stephen Rothwell
2022-07-25  8:41 Stephen Rothwell
2022-07-25  8:52 ` Miguel Ojeda
2022-07-13 10:34 Stephen Rothwell
2022-07-13 10:50 ` Miguel Ojeda
2022-07-13 11:39 ` Peter Zijlstra
2022-07-15  1:13   ` Miguel Ojeda
2022-07-15  9:01     ` Peter Zijlstra
2022-07-15 11:01       ` Miguel Ojeda
2021-12-10 18:18 broonie
2021-11-03  3:19 Stephen Rothwell
2021-11-03 10:30 ` Miguel Ojeda
2021-11-03 21:01   ` Stephen Rothwell
2021-11-04 12:19     ` Miguel Ojeda
2021-11-04 20:31       ` Stephen Rothwell
2021-11-05 11:00         ` Miguel Ojeda
2021-07-19  6:16 Stephen Rothwell
2021-07-12  0:37 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221004190502.4e7d3348@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alex.gaynor@gmail.com \
    --cc=ark.email@gmail.com \
    --cc=bobo1239@web.de \
    --cc=bobwxc@email.cn \
    --cc=corbet@lwn.net \
    --cc=dxu@dxuuu.xyz \
    --cc=gary@garyguo.net \
    --cc=jtitor@2k36.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=me@jvmerkle.de \
    --cc=me@kloenk.de \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=ojeda@kernel.org \
    --cc=thesven73@gmail.com \
    --cc=wedsonaf@google.com \
    --cc=wei.liu@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).