From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Hu Haowen <src.res@email.cn>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the ftrace tree with the jc_docs tree
Date: Fri, 20 Aug 2021 14:02:30 +1000 [thread overview]
Message-ID: <20210820140230.42f20261@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
Hi all,
Today's linux-next merge of the ftrace tree got a conflict in:
MAINTAINERS
between commit:
0c3b533cfdd5 ("MAINTAINERS: add entry for traditional Chinese documentation")
from the jc_docs tree and commit:
db396be6ddc4 ("MAINTAINERS: Add an entry for os noise/latency")
from the ftrace tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc MAINTAINERS
index 34cbc59bbea0,4268644cf86a..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -18921,14 -18798,20 +18921,28 @@@ F: arch/x86/mm/testmmiotrace.
F: include/linux/mmiotrace.h
F: kernel/trace/trace_mmiotrace.c
+ TRACING OS NOISE / LATENCY TRACERS
+ M: Steven Rostedt <rostedt@goodmis.org>
+ M: Daniel Bristot de Oliveira <bristot@kernel.org>
+ S: Maintained
+ F: kernel/trace/trace_osnoise.c
+ F: include/trace/events/osnoise.h
+ F: kernel/trace/trace_hwlat.c
+ F: kernel/trace/trace_irqsoff.c
+ F: kernel/trace/trace_sched_wakeup.c
+ F: Documentation/trace/osnoise-tracer.rst
+ F: Documentation/trace/timerlat-tracer.rst
+ F: Documentation/trace/hwlat_detector.rst
+ F: arch/*/kernel/trace.c
+
+TRADITIONAL CHINESE DOCUMENTATION
+M: Hu Haowen <src.res@email.cn>
+L: linux-doc-tw-discuss@lists.sourceforge.net
+S: Maintained
+W: https://github.com/srcres258/linux-doc
+T: git git://github.com/srcres258/linux-doc.git doc-zh-tw
+F: Documentation/translations/zh_TW/
+
TRIVIAL PATCHES
M: Jiri Kosina <trivial@kernel.org>
S: Maintained
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-08-20 4:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 4:02 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-15 1:16 linux-next: manual merge of the ftrace tree with the jc_docs tree Stephen Rothwell
2023-02-15 2:03 ` Bagas Sanjaya
2023-02-13 1:24 Stephen Rothwell
2018-03-21 4:31 Stephen Rothwell
2018-03-21 4:37 ` Stephen Rothwell
2018-03-21 13:15 ` Steven Rostedt
2018-03-21 20:55 ` Tom Zanussi
2018-03-21 22:21 ` Stephen Rothwell
2018-03-21 23:09 ` Tom Zanussi
2018-03-22 13:41 ` Steven Rostedt
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=20210820140230.42f20261@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=src.res@email.cn \
/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).