From: Jonathan Corbet <corbet@lwn.net>
To: David Hildenbrand <david@redhat.com>
Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the akpm tree with the jc_docs tree
Date: Mon, 8 Oct 2018 08:32:28 -0600 [thread overview]
Message-ID: <20181008083228.33ec7c1d@lwn.net> (raw)
In-Reply-To: <6ab76538-b836-3b22-cb29-102c613091cf@redhat.com>
On Mon, 8 Oct 2018 10:38:29 +0200
David Hildenbrand <david@redhat.com> wrote:
> > I can do the renaming and add the patch
> >
> > "memory-hotplug.txt: add some details about locking internals"
> >
> > on top of the jc_docs tree.
> >
> > Does it sound Ok?
> >
>
> Fine with me.
Works for me too.
Andrew, what is your preference for mm docs patches going forward? It
seems we should try to focus them on one tree or the other. My preference
would be to keep carrying them to avoid conflicts elsewhere, but I can
certainly direct them youward if you'd rather they went that way.
Thanks,
jon
next prev parent reply other threads:[~2018-10-08 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 7:38 linux-next: manual merge of the akpm tree with the jc_docs tree Stephen Rothwell
2018-10-08 8:13 ` Mike Rapoport
2018-10-08 8:38 ` David Hildenbrand
2018-10-08 14:32 ` Jonathan Corbet [this message]
2018-10-11 0:21 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2020-12-01 9:18 Stephen Rothwell
2016-11-09 4:19 Stephen Rothwell
2016-11-09 19:16 ` Mimi Zohar
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=20181008083228.33ec7c1d@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).