All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Joe Perches <joe@perches.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Petr Mladek <pmladek@suse.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-media@vger.kernel.org,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	hverkuil@xs4all.nl,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	mchehab@kernel.org, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs
Date: Fri, 03 Apr 2020 09:37:14 +0300	[thread overview]
Message-ID: <87zhbtkrc5.fsf@intel.com> (raw)
In-Reply-To: <04bb934e551f43540d1daacd2759beacc0b3116a.camel@perches.com>

On Thu, 02 Apr 2020, Joe Perches <joe@perches.com> wrote:
> On Thu, 2020-04-02 at 11:34 +0300, Jani Nikula wrote:
>> Or could we conceive of a way to make this locally extensible yet safe,
>> letting callers use something like %{foo}, as well as providing a
>> locally relevant function to do the conversion?
>
> No.  printf validation would be broken.

I tossed the idea on a whim, and thinking further I could probably come
up with a number of challenges, but care to elaborate on what you see as
the problem in validation?

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Joe Perches <joe@perches.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Petr Mladek <pmladek@suse.com>
Cc: mchehab@kernel.org,
	"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	hverkuil@xs4all.nl,
	"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	laurent.pinchart@ideasonboard.com,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	linux-media@vger.kernel.org,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs
Date: Fri, 03 Apr 2020 09:37:14 +0300	[thread overview]
Message-ID: <87zhbtkrc5.fsf@intel.com> (raw)
In-Reply-To: <04bb934e551f43540d1daacd2759beacc0b3116a.camel@perches.com>

On Thu, 02 Apr 2020, Joe Perches <joe@perches.com> wrote:
> On Thu, 2020-04-02 at 11:34 +0300, Jani Nikula wrote:
>> Or could we conceive of a way to make this locally extensible yet safe,
>> letting callers use something like %{foo}, as well as providing a
>> locally relevant function to do the conversion?
>
> No.  printf validation would be broken.

I tossed the idea on a whim, and thinking further I could probably come
up with a number of challenges, but care to elaborate on what you see as
the problem in validation?

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2020-04-03  6:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 14:05 [PATCH 1/1] lib/vsprintf: Add support for printing V4L2 and DRM fourccs Sakari Ailus
2020-04-01 14:05 ` Sakari Ailus
2020-04-01 14:13 ` Hans Verkuil
2020-04-01 14:13   ` Hans Verkuil
2020-04-01 15:13   ` Andy Shevchenko
2020-04-01 15:13     ` Andy Shevchenko
2020-04-02  7:32     ` Sakari Ailus
2020-04-02  7:32       ` Sakari Ailus
2020-04-06  7:37     ` Pekka Paalanen
2020-04-06  7:37       ` Pekka Paalanen
2020-04-02  7:18   ` Sakari Ailus
2020-04-02  7:18     ` Sakari Ailus
2020-04-02  8:34 ` Jani Nikula
2020-04-02  8:34   ` Jani Nikula
2020-04-02  8:52   ` Sakari Ailus
2020-04-02  8:52     ` Sakari Ailus
2020-04-02 13:53   ` Mauro Carvalho Chehab
2020-04-02 13:53     ` Mauro Carvalho Chehab
2020-04-02 23:28     ` Joe Perches
2020-04-02 23:28       ` Joe Perches
2020-04-02 23:26   ` Joe Perches
2020-04-02 23:26     ` Joe Perches
2020-04-03  6:37     ` Jani Nikula [this message]
2020-04-03  6:37       ` Jani Nikula
2020-04-03 13:11       ` Joe Perches
2020-04-03 13:11         ` Joe Perches
  -- strict thread matches above, loose matches on Subject: below --
2020-04-27 14:50 Sakari Ailus
2020-04-27 14:50 ` Sakari Ailus
2020-04-27 14:54 ` Sakari Ailus
2020-04-27 14:54   ` Sakari Ailus

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=87zhbtkrc5.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hverkuil@xs4all.nl \
    --cc=joe@perches.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --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 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.