linux-kernel.vger.kernel.org archive mirror
 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 12:48:29 -0600	[thread overview]
Message-ID: <87cz4zb8xu.fsf@meer.lwn.net> (raw)
In-Reply-To: <fe5d1e0e-0725-45eb-8b96-edcd12ae4a8b@intel.com>

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

> On 3/15/23 14:15, Jonathan Corbet wrote:
>> On the other hand, it *is* a fair amount of churn.  If it's more than
>> people can handle, I'll quietly back away and we'll muddle along as we have
>> been; this isn't something I'm going to dig in my heels over.
>
> I'm not fundamentally opposed to this.  It'll probably cost me a few
> keystrokes in moments of confusion, but that's the price of progress. :)
>
> Things in Documentation/ have also been mobile enough in recent years
> that I tend to "find Documentation | grep something" rather than try to
> remember the paths for things.  Adding an arch/ in there won't hurt
> anything.

So, if I'm not going to get tarred and feathered for this, I'd like to
proceed, and am wondering what the best way is.  Patch 1 is a pure docs
change that won't affect anybody.  I could also apply #2 if I could get
an ack from the x86 community, but that is sure to create conflicts with
tip and get us all more cheery notes from Stephen Rothwell.

I could do the "fix up and send at the end of the merge window" trick
with it.  Or perhaps some of this should go via tip?  Suggestions
welcome.

Thanks,

jon

  reply	other threads:[~2023-03-23 18:48 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 [this message]
2023-03-23 19:20     ` Dave Hansen
2023-03-23 19:40       ` Jonathan Corbet
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=87cz4zb8xu.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;
as well as URLs for NNTP newsgroup(s).