From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
dri-devel@lists.freedesktop.org, hverkuil@xs4all.nl,
laurent.pinchart@ideasonboard.com,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Joe Perches <joe@perches.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH v7 2/3] v4l: ioctl: Use %p4cc printk modifier to print FourCC codes
Date: Mon, 15 Feb 2021 18:05:45 +0100 [thread overview]
Message-ID: <20210215180545.7178e180@coco.lan> (raw)
In-Reply-To: <YCqnu61J2Q8rsrZa@alley>
Em Mon, 15 Feb 2021 17:56:27 +0100
Petr Mladek <pmladek@suse.com> escreveu:
> On Mon 2021-02-15 13:40:29, Sakari Ailus wrote:
> > Now that we can print FourCC codes directly using printk, make use of the
> > feature in V4L2 core.
> >
> > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
>
> I am curious whether I could take this via printk tree or if Mauro
> would prefer to take this via his tree.
IMO, the best would be if the entire series gets merged via a single
tree.
Feel free to merge via the printk one.
Acked-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>
> Anyway, there will be v8 with small changes in the 1st patch.
>
> Best Regards,
> Petr
Thanks,
Mauro
next prev parent reply other threads:[~2021-02-15 17:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 11:40 [PATCH v7 0/3] Add %p4cc printk modifier for V4L2 and DRM fourcc codes Sakari Ailus
2021-02-15 11:40 ` [PATCH v7 1/3] lib/vsprintf: Add support for printing V4L2 and DRM fourccs Sakari Ailus
2021-02-15 13:31 ` Andy Shevchenko
2021-02-15 13:56 ` Sakari Ailus
2021-02-15 15:54 ` Andy Shevchenko
2021-02-15 16:51 ` Petr Mladek
2021-02-15 17:21 ` Sakari Ailus
2021-02-15 11:40 ` [PATCH v7 2/3] v4l: ioctl: Use %p4cc printk modifier to print FourCC codes Sakari Ailus
2021-02-15 13:34 ` Andy Shevchenko
2021-02-15 13:50 ` Sakari Ailus
2021-02-15 16:56 ` Petr Mladek
2021-02-15 17:05 ` Mauro Carvalho Chehab [this message]
2021-02-15 17:22 ` Sakari Ailus
2021-02-15 11:40 ` [PATCH v7 3/3] drm: Switch to %p4cc format modifier Sakari Ailus
2021-02-15 13:41 ` Andy Shevchenko
2021-02-15 13:48 ` Sakari Ailus
2021-02-15 17:26 ` Sakari Ailus
2021-02-15 17:36 ` Andy Shevchenko
2021-02-15 16:58 ` Petr Mladek
2021-02-16 8:37 ` Thomas Zimmermann
2021-02-16 9:01 ` Sakari Ailus
2021-02-16 9:08 ` Petr Mladek
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=20210215180545.7178e180@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=jani.nikula@linux.intel.com \
--cc=joe@perches.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sergey.senozhatsky@gmail.com \
/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).