From: Chris Wilson <chris@chris-wilson.co.uk>
To: Dan Carpenter <error27@gmail.com>, David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
kernel-janitors@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [patch] i915: snprintf returns large values
Date: Wed, 08 Sep 2010 19:49:36 +0000 [thread overview]
Message-ID: <89k83a$9jej6t@azsmga001.ch.intel.com> (raw)
In-Reply-To: <20100908194447.GC3463@bicker>
On Wed, 8 Sep 2010 21:44:47 +0200, Dan Carpenter <error27@gmail.com> wrote:
> snprintf() returns the number of bytes which would have been used if
> there was enough space. It can be larger than the size of the buffer.
> Obviously in this case the buffer is large enough but everyone just
> copy and pastes this code so it's better to limit it and set a good
> example.
Applied to drm-intel-next as it is just a pedagogical fix.
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2010-09-08 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 19:44 [patch] i915: snprintf returns large values Dan Carpenter
2010-09-08 19:49 ` Chris Wilson [this message]
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='89k83a$9jej6t@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.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