From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: [PATCH 2/2] MAINTAIERS/printk: Add link to printk git
Date: Wed, 5 Jan 2022 10:41:57 +0100 [thread overview]
Message-ID: <20220105094157.26216-3-pmladek@suse.com> (raw)
In-Reply-To: <20220105094157.26216-1-pmladek@suse.com>
It might also help to avoid confusion with the historic
pmladek/printk.git that has got obsoleted by printk/linux.git
in February 2020.
Signed-off-by: Petr Mladek <pmladek@suse.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index e9547ccda7d0..653415ed050b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -15339,6 +15339,7 @@ M: Sergey Senozhatsky <senozhatsky@chromium.org>
R: Steven Rostedt <rostedt@goodmis.org>
R: John Ogness <john.ogness@linutronix.de>
S: Maintained
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git
F: include/linux/printk.h
F: kernel/printk/
--
2.26.2
next prev parent reply other threads:[~2022-01-05 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 9:41 [PATCH 0/2] MAINTAINERS: Update information about printk git tree Petr Mladek
2022-01-05 9:41 ` [PATCH 1/2] MAINTAINERS/vsprintf: Update link to " Petr Mladek
2022-01-05 9:41 ` Petr Mladek [this message]
2022-01-05 11:57 ` [PATCH 0/2] MAINTAINERS: Update information about " Andy Shevchenko
2022-01-06 9:29 ` Petr Mladek
2022-01-06 18:25 ` 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=20220105094157.26216-3-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
Powered by JetHome