public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: linux-doc@vger.kernel.org
Cc: linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/7] docs: Move Documentation/arm under Documentation/arch
Date: Mon, 12 Jun 2023 06:38:53 -0600	[thread overview]
Message-ID: <87h6rcn9cy.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230529144856.102755-1-corbet@lwn.net>

Jonathan Corbet <corbet@lwn.net> writes:

> Architecture-specific documentation is being moved into Documentation/arch/
> as a way of cleaning up the top-level documentation directory and making
> the docs hierarchy more closely match the source hierarchy.  Move
> Documentation/arm into arch/ and fix all in-tree references.
>
> This is one of the more intrusive moves (if not *the* most intrusive), but
> the changes are all straighforward.
>
> I'm happy to take these through the docs tree, but the potential for
> conflicts might be less if they go through an Arm tree instead.
>
> v2 changes:
>  - add tags
>  - remove ahead-of-its-time MAINTAINERS change
>  - proper changelog for patch #7
>  - IOW: nothing all that substantial.

So nobody is clamoring to pick these up, which is fine...  unless I hear
screaming, my plan is to drop these into linux-next shortly (no
conflicts at the moment) and send them linusward in a separate pull
request during the merge window.

Thanks,

jon

      parent reply	other threads:[~2023-06-12 12:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 14:48 [PATCH v2 0/7] docs: Move Documentation/arm under Documentation/arch Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 1/7] arm: docs: Move Arm documentation to Documentation/arch/ Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 2/7] arm: update in-source documentation references Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 3/7] arm64: Update Documentation/arm references Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 4/7] mips: update a reference to a moved Arm Document Jonathan Corbet
2023-05-29 14:48 ` [PATCH v2 5/7] crypto: update some Arm documentation references Jonathan Corbet
2023-05-31 21:22   ` Jernej Škrabec
2023-05-29 14:48 ` [PATCH v2 6/7] docs: update some straggling Documentation/arm references Jonathan Corbet
2023-05-29 14:57   ` Greg Kroah-Hartman
2023-05-30  7:20   ` Nicolas.Ferre
2023-06-14  7:04   ` Uwe Kleine-König
2023-05-29 14:48 ` [PATCH v2 7/7] dt-bindings: Update " Jonathan Corbet
2023-06-07 20:55   ` Rob Herring
2023-06-12 12:38 ` Jonathan Corbet [this message]

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=87h6rcn9cy.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.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