All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arve Hjønnevåg" <arve@android.com>
To: Zhengwang Ruan <ruan.zhengwang@gmail.com>
Cc: gregkh@linuxfoundation.org, chris+android@zenthought.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2 v2] Staging:android: Initialise buffer and buffer_size before used
Date: Tue, 6 Mar 2012 20:01:58 -0800	[thread overview]
Message-ID: <CAMP5XgfWBj_V+21avHyEbViYK1N0fHBmyj6CcYry0Fd4QttgqQ@mail.gmail.com> (raw)
In-Reply-To: <1331087818-9942-2-git-send-email-ruan.zhengwang@gmail.com>

On Tue, Mar 6, 2012 at 6:36 PM, Zhengwang Ruan <ruan.zhengwang@gmail.com> wrote:
> GCC warns 'buffer' and 'buffer_size' are used with being uninitialized, and
> 'buffer' is used as returned value, and 'buffer_size' is initialized using
> uninitialized_var to clear warning.

Why do you clear the warning on buffer_size with uninitialized_var()
but not on buffer? Neither variable is used before being initialized.

-- 
Arve Hjønnevåg

WARNING: multiple messages have this Message-ID (diff)
From: "Arve Hjønnevåg" <arve@android.com>
To: Zhengwang Ruan <ruan.zhengwang@gmail.com>
Cc: gregkh@linuxfoundation.org, chris+android@zenthought.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2 v2] Staging:android: Initialise buffer and buffer_size before used
Date: Wed, 07 Mar 2012 04:01:58 +0000	[thread overview]
Message-ID: <CAMP5XgfWBj_V+21avHyEbViYK1N0fHBmyj6CcYry0Fd4QttgqQ@mail.gmail.com> (raw)
In-Reply-To: <1331087818-9942-2-git-send-email-ruan.zhengwang@gmail.com>

On Tue, Mar 6, 2012 at 6:36 PM, Zhengwang Ruan <ruan.zhengwang@gmail.com> wrote:
> GCC warns 'buffer' and 'buffer_size' are used with being uninitialized, and
> 'buffer' is used as returned value, and 'buffer_size' is initialized using
> uninitialized_var to clear warning.

Why do you clear the warning on buffer_size with uninitialized_var()
but not on buffer? Neither variable is used before being initialized.

-- 
Arve Hjønnevåg
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-03-07  4:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07  2:36 [PATCH 1/2 v2] Staging:android: Change type for binder_debug_no_lock switch to bool Zhengwang Ruan
2012-03-07  2:36 ` Zhengwang Ruan
2012-03-07  2:36 ` [PATCH 2/2 v2] Staging:android: Initialise buffer and buffer_size before used Zhengwang Ruan
2012-03-07  2:36   ` Zhengwang Ruan
2012-03-07  4:01   ` Arve Hjønnevåg [this message]
2012-03-07  4:01     ` Arve Hjønnevåg
2012-03-07  4:58     ` Zhengwang Ruan
2012-03-07  4:58       ` Zhengwang Ruan
2012-03-07  5:46   ` Greg KH
2012-03-07  5:46     ` Greg KH
2012-03-07  6:16     ` Zhengwang Ruan
2012-03-07  6:16       ` Zhengwang Ruan
2012-03-07  5:58   ` Dan Carpenter
2012-03-07  6:00     ` Dan Carpenter
2012-03-07  6:01     ` Zhengwang Ruan
2012-03-07  6:01       ` Zhengwang Ruan
2012-03-07  6:20       ` Dan Carpenter
2012-03-07  6:20         ` Dan Carpenter
2012-03-07  6:25         ` Zhengwang Ruan
2012-03-07  6:25           ` Zhengwang Ruan
  -- strict thread matches above, loose matches on Subject: below --
2012-03-07  2:49 [PATCH 1/2 v2] Staging:android: Change type for binder_debug_no_lock switch to bool ruan.zhengwang
2012-03-07  2:49 ` ruan.zhengwang
2012-03-07  2:49 ` [PATCH 2/2 v2] Staging:android: Initialise buffer and buffer_size before used ruan.zhengwang
2012-03-07  2:49   ` ruan.zhengwang
2012-02-27 10:17 Zhengwang Ruan
2012-02-27 10:48 ` Dan Carpenter
2012-02-27 10:17 [PATCH 1/2 v2] Staging:android: Change type for binder_debug_no_lock switch to bool Zhengwang Ruan

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=CAMP5XgfWBj_V+21avHyEbViYK1N0fHBmyj6CcYry0Fd4QttgqQ@mail.gmail.com \
    --to=arve@android.com \
    --cc=chris+android@zenthought.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ruan.zhengwang@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.