From: Guru Das Srinagesh <gurooodas@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
jsimmons@infradead.org, gregkh@linuxfoundation.org,
joe@perches.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, lustre-devel@lists.lustre.org
Subject: Re: [PATCH v4] staging: lustre: llite: Fix variable length array warning
Date: Tue, 9 May 2017 02:10:34 -0700 [thread overview]
Message-ID: <20170509091034.GA29060@alpha> (raw)
In-Reply-To: <20170509083136.auumomyrgat4oc2k@mwanda>
On Tue, May 09, 2017 at 11:31:36AM +0300, Dan Carpenter wrote:
> Just ignore the warning.
>
Thank you for your comments on this patch.
prev parent reply other threads:[~2017-05-09 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 6:57 [PATCH v4] staging: lustre: llite: Fix variable length array warning Guru Das Srinagesh
2017-05-09 8:31 ` Dan Carpenter
2017-05-09 9:10 ` Guru Das Srinagesh [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=20170509091034.GA29060@alpha \
--to=gurooodas@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).