linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: WANG Xuerui <kernel@xen0n.name>
To: Huacai Chen <chenhuacai@loongson.cn>,
	Arnd Bergmann <arnd@arndb.de>, Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Airlie <airlied@linux.ie>, Jonathan Corbet <corbet@lwn.net>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>,
	Yanteng Si <siyanteng@loongson.cn>,
	Huacai Chen <chenhuacai@gmail.com>, Guo Ren <guoren@kernel.org>,
	Xuerui Wang <kernel@xen0n.name>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH V15 00/24] arch: Add basic LoongArch support
Date: Fri, 3 Jun 2022 17:14:05 +0800	[thread overview]
Message-ID: <e3af6993-bbd5-9ce6-07e8-3c180833db75@xen0n.name> (raw)
In-Reply-To: <20220603072053.35005-1-chenhuacai@loongson.cn>

On 6/3/22 15:20, Huacai Chen wrote:
> V13 -> V14:
> 1, Add some missing Cc;
> 2, Add a comment for EFI_RT_VIRTUAL_LIMIT definition.
>
> V14 -> V15:
> 1, Remove EFISTUB for now, since the design detail need further discussion.

Thanks for the quick followup revision!

So I've pulled the latest loongarch-next HEAD (commit 
fb575e32bdd27d57b1587227abea8d4ea2eccb71), and did allmodconfig builds 
of ARCH={x86,mips,loongarch}. I used the LoongArch cross-toolchain 
compiled by Arnd and my own Gentoo toolchains (native & crossdev) for 
x86 and mips; no new problem is found.

Diff between this revision and the previous revision I tested (I think 
it's v13) is just removal of the non-reviewed architecture-independent 
EFI changes, which is good, and I believe we now have every commit here 
ready for PR. (In theory, Eric didn't respond to my previous mail to 
approve the signal.h UAPI, but I can confirm that his concerns are fully 
addressed, which involved spelling suggestion and prefixes to the type 
names.)

On the v14 thread, Bagas suggested that the ASCII art in the 
documentation in single-cell table form be replaced with ordinary code 
blocks, which I think is reasonable due to consistency; but we already 
got 2 revisions of this patchset today, and each revision adds 25 mails 
to everyone's inbox, so I think Huacai could just apply the changes, 
collect the Tested-by, and just push to the loongarch-next branch 
instead (and replying here of course).

So, Arnd, do you think we can go ahead and send the PR today or 
tomorrow? I know this batch of modification didn't get included in 
today's linux-next, but there's little substantive change, and Stephen 
didn't mention that there will be no linux-next tomorrow, so the timing 
might still work out. We may want to get the final Acked-by from Ard for 
the now stripped-down Patch 11, though, I'm not entirely sure.


      parent reply	other threads:[~2022-06-03  9:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  7:20 [PATCH V15 00/24] arch: Add basic LoongArch support Huacai Chen
2022-06-03  7:20 ` [PATCH V15 01/24] irqchip: Adjust Kconfig for Loongson Huacai Chen
2022-06-03  7:20 ` [PATCH V15 02/24] irqchip/loongson-liointc: Fix build error for LoongArch Huacai Chen
2022-06-03  7:20 ` [PATCH V15 03/24] Documentation: LoongArch: Add basic documentations Huacai Chen
2022-06-03  7:20 ` [PATCH V15 04/24] Documentation/zh_CN: Add basic LoongArch documentations Huacai Chen
2022-06-03  7:20 ` [PATCH V15 05/24] LoongArch: Add ELF-related definitions Huacai Chen
2022-06-03  7:20 ` [PATCH V15 06/24] LoongArch: Add writecombine support for drm Huacai Chen
2022-06-03  7:20 ` [PATCH V15 07/24] LoongArch: Add build infrastructure Huacai Chen
2022-06-03  7:20 ` [PATCH V15 08/24] LoongArch: Add CPU definition headers Huacai Chen
2022-06-03  7:20 ` [PATCH V15 09/24] LoongArch: Add atomic/locking headers Huacai Chen
2022-06-03  7:20 ` [PATCH V15 10/24] LoongArch: Add other common headers Huacai Chen
2022-06-03 13:40   ` Jason A. Donenfeld
2022-06-03 13:55     ` Arnd Bergmann
2022-06-03 14:01       ` Jason A. Donenfeld
2022-06-03 14:14         ` WANG Xuerui
2022-06-03 14:35           ` Huacai Chen
2022-06-04  6:38             ` Jason A. Donenfeld
2022-06-03  7:20 ` [PATCH V15 11/24] LoongArch: Add boot and setup routines Huacai Chen
2022-06-03  9:27   ` WANG Xuerui
2022-06-03 10:02     ` Arnd Bergmann
2022-06-03 10:37       ` WANG Xuerui
2022-06-03 11:48         ` Ard Biesheuvel
2022-06-03  7:20 ` [PATCH V15 12/24] LoongArch: Add exception/interrupt handling Huacai Chen
2022-06-03  7:20 ` [PATCH V15 13/24] LoongArch: Add process management Huacai Chen
2022-06-03  7:20 ` [PATCH V15 14/24] LoongArch: Add memory management Huacai Chen
2022-06-03  7:20 ` [PATCH V15 15/24] LoongArch: Add system call support Huacai Chen
2022-06-03  7:20 ` [PATCH V15 16/24] LoongArch: Add signal handling support Huacai Chen
2022-06-03  7:20 ` [PATCH V15 17/24] LoongArch: Add ELF and module support Huacai Chen
2022-06-03  7:20 ` [PATCH V15 18/24] LoongArch: Add misc common routines Huacai Chen
2022-06-03  7:20 ` [PATCH V15 19/24] LoongArch: Add some library functions Huacai Chen
2022-06-03  7:20 ` [PATCH V15 20/24] LoongArch: Add VDSO and VSYSCALL support Huacai Chen
2022-06-03  7:20 ` [PATCH V15 21/24] LoongArch: Add multi-processor (SMP) support Huacai Chen
2022-06-03  7:20 ` [PATCH V15 22/24] LoongArch: Add Non-Uniform Memory Access (NUMA) support Huacai Chen
2022-06-03  7:20 ` [PATCH V15 23/24] LoongArch: Add Loongson-3 default config file Huacai Chen
2022-06-03  7:20 ` [PATCH V15 24/24] MAINTAINERS: Add maintainer information for LoongArch Huacai Chen
2022-06-03  9:14 ` WANG Xuerui [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=e3af6993-bbd5-9ce6-07e8-3c180833db75@xen0n.name \
    --to=kernel@xen0n.name \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=chenhuacai@gmail.com \
    --cc=chenhuacai@loongson.cn \
    --cc=corbet@lwn.net \
    --cc=guoren@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=siyanteng@loongson.cn \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).