linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Sergey Senozhatsky" <sergey.senozhatsky.work@gmail.com>,
	linux-kernel@vger.kernel.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Uwe Kleine-König" <uwe@kleine-koenig.org>,
	"Joe Perches" <joe@perches.com>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH] MAINTAINERS: Add VSPRINTF
Date: Thu, 31 Oct 2019 16:09:52 +0100	[thread overview]
Message-ID: <20191031150952.3ag6qa5y4wvikd76@pathway.suse.cz> (raw)
In-Reply-To: <20191031145112.thphlpnjvnykbzyy@pathway.suse.cz>

On Thu 2019-10-31 15:51:12, Petr Mladek wrote:
> On Thu 2019-10-31 14:51:24, Rasmus Villemoes wrote:
> > On 31/10/2019 14.33, Petr Mladek wrote:
> > > printk maintainers have been reviewing patches against vsprintf code last
> > > few years. Most changes have been committed via printk.git last two years.
> > > 
> > > New group is used because printk() is not the only vsprintf() user.
> > > Also the group of interested people is not the same.
> > 
> > Can you add
> > 
> > R: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> 
> Sure. The more reviewers the better :-)

I acutally wanted to add also

R: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Best Regards,
Petr

  reply	other threads:[~2019-10-31 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 13:33 [PATCH] MAINTAINERS: Add VSPRINTF Petr Mladek
2019-10-31 13:51 ` Rasmus Villemoes
2019-10-31 14:51   ` Petr Mladek
2019-10-31 15:09     ` Petr Mladek [this message]
2019-11-02 10:18       ` Andy Shevchenko
2019-11-07 15:22         ` Petr Mladek
2019-11-02 11:09 ` Steven Rostedt
2019-11-04 12:41 ` Sergey Senozhatsky

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=20191031150952.3ag6qa5y4wvikd76@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=rostedt@goodmis.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=uwe@kleine-koenig.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).