public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>,
	Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <siyanteng@loongson.cn>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>, Vineet Gupta <vgupta@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Costa Shulyupin <costa.shul@redhat.com>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
	Wu XiangCheng <bobwxc@email.cn>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:LOONGARCH" <loongarch@lists.linux.dev>
Subject: Re: [PATCH v3] docs: move loongarch under arch
Date: Fri, 21 Jul 2023 14:02:06 -0600	[thread overview]
Message-ID: <87tttxc9tt.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230717192456.453124-1-costa.shul@redhat.com>

Costa Shulyupin <costa.shul@redhat.com> writes:

> and fix all in-tree references.
>
> 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.
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
>

This, I think, is ready to apply, but I sure would like an ack from the
loongarch maintainers.  As it stands, please let me know if you object,
otherwise I'll apply this in the near future.

Thanks,

jon

  parent reply	other threads:[~2023-07-21 20:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  7:06 [PATCH] docs: move loongarch under arch Costa Shulyupin
2023-07-17  7:17 ` Randy Dunlap
2023-07-17 13:43 ` Jonathan Corbet
2023-07-17 14:13   ` [PATCH v2] " Costa Shulyupin
2023-07-17 14:23     ` Jonathan Corbet
2023-07-17 19:24       ` [PATCH v3] " Costa Shulyupin
2023-07-18  2:16         ` Yanteng Si
2023-07-21 20:02         ` Jonathan Corbet [this message]
2023-07-22  2:38           ` Huacai Chen
2023-07-31 16:31         ` Jonathan Corbet

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=87tttxc9tt.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=chenhuacai@kernel.org \
    --cc=costa.shul@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=kernel@xen0n.name \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=siyanteng@loongson.cn \
    --cc=tglx@linutronix.de \
    --cc=vgupta@kernel.org \
    --cc=yangtiezhu@loongson.cn \
    /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