From: Jonathan Corbet <corbet@lwn.net>
To: Will Deacon <will@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adam Zerella <adam.zerella@gmail.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>
Subject: Re: linux-next: manual merge of the jc_docs tree with the arm-perf tree
Date: Tue, 5 Nov 2019 12:13:45 -0700 [thread overview]
Message-ID: <20191105121345.445a3438@lwn.net> (raw)
In-Reply-To: <20191105181137.GB32767@willie-the-truck>
On Tue, 5 Nov 2019 18:11:38 +0000
Will Deacon <will@kernel.org> wrote:
> Looks fine to me, thanks. Jon -- are you ok living with this conflict?
Just another day in the life of the docs tree...:) No worries here.
Thanks, Stephen.
jon
prev parent reply other threads:[~2019-11-05 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 0:37 linux-next: manual merge of the jc_docs tree with the arm-perf tree Stephen Rothwell
2019-11-05 18:11 ` Will Deacon
2019-11-05 19:13 ` Jonathan Corbet [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=20191105121345.445a3438@lwn.net \
--to=corbet@lwn.net \
--cc=adam.zerella@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=qiangqing.zhang@nxp.com \
--cc=sfr@canb.auug.org.au \
--cc=will@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).