From: Chen Gang <gang.chen@asianux.com>
To: Ben Dooks <ben@fluff.org>
Cc: kgene.kim@samsung.com, ben-linux@fluff.org,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] ARM: plat-samsung: using vsnprintf instead of vsprintf for the limit buffer length 256
Date: Tue, 22 Jan 2013 09:00:03 +0800 [thread overview]
Message-ID: <50FDE493.1020204@asianux.com> (raw)
In-Reply-To: <20130121135626.GP1095@trinity.fluff.org>
于 2013年01月21日 21:56, Ben Dooks 写道:
> How about: vsnprintf(buff, sizeof(buff), fmt, va);
>
> It means we do not end up assuming the size of 'buff' and will be correct
> if the code is changed to declare 'buff' to be a different size.
thank you, I will send patch v2.
:-)
--
Chen Gang
Asianux Corporation
WARNING: multiple messages have this Message-ID (diff)
From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: plat-samsung: using vsnprintf instead of vsprintf for the limit buffer length 256
Date: Tue, 22 Jan 2013 09:00:03 +0800 [thread overview]
Message-ID: <50FDE493.1020204@asianux.com> (raw)
In-Reply-To: <20130121135626.GP1095@trinity.fluff.org>
? 2013?01?21? 21:56, Ben Dooks ??:
> How about: vsnprintf(buff, sizeof(buff), fmt, va);
>
> It means we do not end up assuming the size of 'buff' and will be correct
> if the code is changed to declare 'buff' to be a different size.
thank you, I will send patch v2.
:-)
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-01-22 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 10:25 [PATCH] ARM: plat-samsung: using vsnprintf instead of vsprintf for the limit buffer length 256 Chen Gang
2013-01-21 10:25 ` Chen Gang
2013-01-21 13:56 ` Ben Dooks
2013-01-21 13:56 ` Ben Dooks
2013-01-22 1:00 ` Chen Gang [this message]
2013-01-22 1:00 ` Chen Gang
2013-01-21 16:00 ` Russell King - ARM Linux
2013-01-21 16:00 ` Russell King - ARM Linux
2013-01-22 1:00 ` Chen Gang
2013-01-22 1:00 ` Chen Gang
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=50FDE493.1020204@asianux.com \
--to=gang.chen@asianux.com \
--cc=ben-linux@fluff.org \
--cc=ben@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.