From: Jonathan Corbet <corbet@lwn.net>
To: Dave Hansen <dave.hansen@intel.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH RFC 0/2] Begin reorganizing the arch documentation
Date: Thu, 30 Mar 2023 12:52:40 -0600 [thread overview]
Message-ID: <87a5zuf4w7.fsf@meer.lwn.net> (raw)
In-Reply-To: <87v8ir9rz6.fsf@meer.lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
> Now that I look...the only thing in linux-next currently that conflicts
> is the shadow-stack series; if that continues, it might not be necessary
> to do anything special.
There's an FPU patch now too. Git seems to handle the conflicts *almost*
seamlessly, though. So, FYI, I think I'll go ahead and drop this change
into docs-next, which will probably get us a cheery note from Stephen in
the near future.
(Stephen: the change is simply:
mv Documentation/x86 Documentation/arch/x86
the only fix I had to do in my test merge was to add the new
shadow-stack document in the new directory).
Thanks,
jon
next prev parent reply other threads:[~2023-03-30 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 21:15 [PATCH RFC 0/2] Begin reorganizing the arch documentation Jonathan Corbet
2023-03-15 21:15 ` [PATCH 1/2] docs: create a top-level arch/ directory Jonathan Corbet
2023-03-15 21:15 ` [PATCH 2/2] docs: move x86 documentation into Documentation/arch/ Jonathan Corbet
2023-03-23 19:15 ` Dave Hansen
2023-03-15 22:18 ` [PATCH RFC 0/2] Begin reorganizing the arch documentation Dave Hansen
2023-03-23 18:48 ` Jonathan Corbet
2023-03-23 19:20 ` Dave Hansen
2023-03-23 19:40 ` Jonathan Corbet
2023-03-30 18:52 ` Jonathan Corbet [this message]
2023-03-31 3:20 ` 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=87a5zuf4w7.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=x86@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