[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1497140448.3254.3.camel@perches.com>
Date: Sat, 10 Jun 2017 17:20:48 -0700
From: Joe Perches <joe@...ches.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Daniel Vetter <daniel.vetter@...el.com>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Sean Paul <seanpaul@...omium.org>,
David Airlie <airlied@...ux.ie>,
dri-devel@...ts.freedesktop.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm: Use vsnprintf extension %ph
On Sat, 2017-06-10 at 19:12 +0300, Andy Shevchenko wrote:
> On Wed, May 31, 2017 at 2:35 AM, Joe Perches <joe@...ches.com> wrote:
> > Using the extension saves a bit of code.
> > + seq_printf(m, "faux/mst: %*ph\n", 2, buf);
> > + seq_printf(m, "mst ctrl: %*ph\n", 1, buf);
> > + seq_printf(m, "branch oui: %*phN devid: ", 3, buf);
>
> All above may use shorter form, i.e.
> "..., "%Xph", buf);", where X is a constant written explicitly inplace.
I know. Consistency is better though.
Note the use of DP_RECEIVER_CAP_SIZE, etc...
Powered by blists - more mailing lists