From: AbdAllah MEZITI <abdallah.meziti.pro@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
swarren@wwwdotorg.org, devel@driverdev.osuosl.org,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@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, Ray Jui <rjui@broadcom.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] somedriver: remove the initialization of static pointers.
Date: Sun, 5 Feb 2017 08:12:26 +0100 [thread overview]
Message-ID: <20170205081226.3c3c681e@GL552JX> (raw)
In-Reply-To: <20170205002943.GA21184@kroah.com>
On Sun, 5 Feb 2017 01:29:43 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Sat, Feb 04, 2017 at 08:39:21PM +0100, AbdAllah-MEZITI wrote:
> > In C a static pointer will be initialized to NULL (e.g: draft C99
> > standard $6.7.8): "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>
>
> Your subject is very odd :(
>
> And is that the correct spelling of your name that you use for legal
> documents? If not, please fix up when you resend this.
>
> Also, fix the line-wrapping of your changelog, and the C99 standard is
> not a "draft" anymore, it was released in 1999 :)
>
> thanks,
>
> greg k-h
Do not worry, this is just an answer to the Task 10 of the Eudyptula Challenge.
yes, this is the correct spelling of my name that i use for legal documents.
OK.
AbdAllah MEZITI.
next prev parent reply other threads:[~2017-02-05 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 19:39 [PATCH] somedriver: remove the initialization of static pointers AbdAllah-MEZITI
2017-02-05 0:29 ` Greg Kroah-Hartman
2017-02-05 7:12 ` AbdAllah MEZITI [this message]
2017-02-06 17:33 ` Mathieu Poirier
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=20170205081226.3c3c681e@GL552JX \
--to=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=gregkh@linuxfoundation.org \
--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