All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Initialise buffer and buffer_size before used
Date: Mon, 27 Feb 2012 09:55:58 +0000	[thread overview]
Message-ID: <20120227095558.GA2817@mwanda> (raw)
In-Reply-To: <1330331985-20767-2-git-send-email-ruan.zhengwang@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

On Mon, Feb 27, 2012 at 04:39:45PM +0800, Zhengwang Ruan 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.
> 

If you wanted to use the uninitialized_var() macro for a pointer,
the trick is:

	struct binder_buffer *uninitialized_var(buffer);

But this is fine as is.

The subject should have a subsystem prefix.  You'll need to resend
both patches for that reason.  (You had them correct in the original
version you sent to kj).  The subjects could also say [patch 1/2]
and [patch 2/2] but it doesn't matter since the line numbers didn't
change and they can be applied in any order.

Don't forget to CC Greg.  He reads the list as well, but you should
always CC a maintainer and a list for each patch.

Anyway, it looks good.  Just fix the subjects and resend.  When you
resend a patch it should say [patch 1/2 v2] in the subject and below
the signed off by line put:
---
v2: added a subsystem prefix to the subject

Sorry that it's a lot of nit picky work.  We have to push as much
work as we can on to patch submitters so that maintainers can apply
things with a click of the mouse.  After a while you'll learn all
the rules.  :)

regards,
dan carpenter


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-27  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  8:39 [PATCH] Initialise buffer and buffer_size before used Zhengwang Ruan
2012-02-27  9:55 ` Dan Carpenter [this message]
2012-02-27 10:22 ` 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=20120227095558.GA2817@mwanda \
    --to=dan.carpenter@oracle.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 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.