From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] MAINTAINERS: Update information about printk git tree
Date: Wed, 5 Jan 2022 13:57:47 +0200 [thread overview]
Message-ID: <YdWHu6vpOWe4+2Gb@smile.fi.intel.com> (raw)
In-Reply-To: <20220105094157.26216-1-pmladek@suse.com>
On Wed, Jan 05, 2022 at 10:41:55AM +0100, Petr Mladek wrote:
> I have noticed one outdated and one missing link to the printk git tree.
> I am not sure if it is worth sending for review and having two patches.
> I just want to avoid possible complains ;-)
FWIW,
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Petr Mladek (2):
> MAINTAINERS/vsprintf: Update link to printk git tree
> MAINTAIERS/printk: Add link to printk git
>
> MAINTAINERS | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> --
> 2.26.2
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-01-05 11:59 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 ` [PATCH 2/2] MAINTAIERS/printk: Add link to printk git Petr Mladek
2022-01-05 11:57 ` Andy Shevchenko [this message]
2022-01-06 9:29 ` [PATCH 0/2] MAINTAINERS: Update information about printk git tree 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=YdWHu6vpOWe4+2Gb@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.