From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Emmanuel Roullit <emmanuel.roullit@gmail.com>, rasesh.mody@cavium.com
Cc: dev@dpdk.org, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/qede: correct function declaration syntax
Date: Mon, 16 Jan 2017 13:17:56 +0000 [thread overview]
Message-ID: <bf6a492e-9099-75d1-f09b-6da6fcd31375@intel.com> (raw)
In-Reply-To: <47279052-2e92-e7f7-92dc-f677b425b1dc@intel.com>
On 1/16/2017 1:00 PM, Ferruh Yigit wrote:
> On 1/15/2017 7:51 PM, Emmanuel Roullit wrote:
>> clang reports this error message:
>> error: this function declaration is not a prototype
>> [-Werror,-Wstrict-prototypes]
>>
>> Signed-off-by: Emmanuel Roullit <emmanuel.roullit@gmail.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Fixes: 5cdd769a26ec ("qede: add L2 support")
CC: stable@dpdk.org
Applied to dpdk-next-net/master, thanks.
parent reply other threads:[~2017-01-16 13:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <47279052-2e92-e7f7-92dc-f677b425b1dc@intel.com>]
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=bf6a492e-9099-75d1-f09b-6da6fcd31375@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=emmanuel.roullit@gmail.com \
--cc=rasesh.mody@cavium.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).