From: Greg KH <gregkh@linuxfoundation.org>
To: AbdAllah-MEZITI <abdallah.meziti.pro@gmail.com>
Cc: devel@driverdev.osuosl.org,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ray Jui <rjui@broadcom.com>, Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
Michael Zoran <mzoran@crowfest.net>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] staging: bcm2835-audio: Remove the initialization of static pointers.
Date: Thu, 9 Feb 2017 13:17:23 +0100 [thread overview]
Message-ID: <20170209121723.GA32270@kroah.com> (raw)
In-Reply-To: <1486511160-2992-1-git-send-email-abdallah.meziti.pro@gmail.com>
On Wed, Feb 08, 2017 at 12:45:47AM +0100, AbdAllah-MEZITI wrote:
> In C a static pointer will be initialized to NULL.
> The §6.7.8 of the ISO/IEC 9899:1999 (E) document says that:
> If an object that has static storage duration is not initialized
> explicitly, then:
> __ if it has pointer type, it is initialized to a null pointer.
>
> Signed-off-by: AbdAllah-MEZITI <abdallah.meziti.pro@gmail.com>
>
> v2: -fix the line-wrapping of the changelog.
> -fix the ref. documentation: C99 standards release,
> and not the draft.
> -this patch is the Task 10 Eudyptula Challenge
> that only fix one code style problem.
> v3: -fix the subject prefix: must be based on the previous submissions.
> ---
> drivers/staging/bcm2835-audio/bcm2835.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
This patch does not apply to my tree at all, sorry.
greg k-h
prev parent reply other threads:[~2017-02-09 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 23:45 [PATCH v3] staging: bcm2835-audio: Remove the initialization of static pointers AbdAllah-MEZITI
2017-02-09 12:17 ` Greg KH [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=20170209121723.GA32270@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abdallah.meziti.pro@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mzoran@crowfest.net \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=swarren@wwwdotorg.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