Generic Linux architectural discussions
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH RFC 0/2] Begin reorganizing the arch documentation
Date: Thu, 23 Mar 2023 13:40:13 -0600	[thread overview]
Message-ID: <87v8ir9rz6.fsf@meer.lwn.net> (raw)
In-Reply-To: <498938d3-60a4-6219-a02c-a03e490103c3@intel.com>

Dave Hansen <dave.hansen@intel.com> writes:

> On 3/23/23 11:48, Jonathan Corbet wrote:
>> I could do the "fix up and send at the end of the merge window" trick
>> with it.
>
> That would work for me.
>
>>  Or perhaps some of this should go via tip?  Suggestions welcome.
>
> Since we have so many branches, we'll still have to do the merges
> between whatever branch carries the move and the actual doc-update branches.
>
> The end-of-the-merge-window is nice for us maintainers because we can
> ask the submitters to do any rebasing.

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.

Thanks,

jon

  reply	other threads:[~2023-03-23 19:40 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 [this message]
2023-03-30 18:52         ` Jonathan Corbet
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=87v8ir9rz6.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=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