All of lore.kernel.org
 help / color / mirror / Atom feed
From: chenzhou <chenzhou10@huawei.com>
To: Joe Perches <joe@perches.com>, <davem@davemloft.net>
Cc: <sparclinux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next 0/2] sparc: use snprintf() in show() methods
Date: Mon, 11 May 2020 09:24:21 +0800	[thread overview]
Message-ID: <887e9dc1-745b-fd2d-39fe-3354e25c6ce8@huawei.com> (raw)
In-Reply-To: <d31e35da0921eb88424e2b201a38b3b8b2d2580c.camel@perches.com>

Sorry, i made a mistake, should be scnprintf().


On 2020/5/9 19:40, Joe Perches wrote:
> On Sat, 2020-05-09 at 17:18 +0800, Chen Zhou wrote:
>> snprintf() returns the number of bytes that would be written,
>> which may be greater than the the actual length to be written.
> []
>> Chen Zhou (2):
>>   sparc: use snprintf() in show_pciobppath_attr() in pci.c
>>   sparc: use snprintf() in show_pciobppath_attr() in vio.c
> Your subjects are a bit off: snprintf vs scnprintf
>
>
>
>



WARNING: multiple messages have this Message-ID (diff)
From: chenzhou <chenzhou10@huawei.com>
To: Joe Perches <joe@perches.com>, davem@davemloft.net
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next 0/2] sparc: use snprintf() in show() methods
Date: Mon, 11 May 2020 01:24:21 +0000	[thread overview]
Message-ID: <887e9dc1-745b-fd2d-39fe-3354e25c6ce8@huawei.com> (raw)
In-Reply-To: <d31e35da0921eb88424e2b201a38b3b8b2d2580c.camel@perches.com>

Sorry, i made a mistake, should be scnprintf().


On 2020/5/9 19:40, Joe Perches wrote:
> On Sat, 2020-05-09 at 17:18 +0800, Chen Zhou wrote:
>> snprintf() returns the number of bytes that would be written,
>> which may be greater than the the actual length to be written.
> []
>> Chen Zhou (2):
>>   sparc: use snprintf() in show_pciobppath_attr() in pci.c
>>   sparc: use snprintf() in show_pciobppath_attr() in vio.c
> Your subjects are a bit off: snprintf vs scnprintf
>
>
>
>

  reply	other threads:[~2020-05-11  1:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  9:18 [PATCH -next 0/2] sparc: use snprintf() in show() methods Chen Zhou
2020-05-09  9:18 ` Chen Zhou
2020-05-09  9:18 ` [PATCH -next 1/2] sparc: use snprintf() in show_pciobppath_attr() in pci.c Chen Zhou
2020-05-09  9:18   ` Chen Zhou
2020-05-09  9:18 ` [PATCH -next 2/2] sparc: use snprintf() in show_pciobppath_attr() in vio.c Chen Zhou
2020-05-09  9:18   ` Chen Zhou
2020-05-09 11:40 ` [PATCH -next 0/2] sparc: use snprintf() in show() methods Joe Perches
2020-05-09 11:40   ` Joe Perches
2020-05-11  1:24   ` chenzhou [this message]
2020-05-11  1:24     ` chenzhou
2020-05-11  1:32     ` Joe Perches
2020-05-11  1:32       ` Joe Perches
2020-05-13 22:36 ` David Miller
2020-05-13 22:36   ` David Miller

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=887e9dc1-745b-fd2d-39fe-3354e25c6ce8@huawei.com \
    --to=chenzhou10@huawei.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@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 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.