All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sujith Sankar (ssujith)" <ssujith-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Thomas Monjalon
	<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] enic: fix warnings
Date: Thu, 4 Dec 2014 10:58:17 +0000	[thread overview]
Message-ID: <D0A63A74.29977%ssujith@cisco.com> (raw)
In-Reply-To: <2887963.q9hPn3S3sv@xps13>


On 04/12/14 4:18 pm, "Thomas Monjalon" <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org> wrote:

>2014-12-04 10:29, Sujith Sankar:
>> 
>> On 02/12/14 8:29 pm, "Thomas Monjalon" <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
>>wrote:
>> 
>> >A lot of warnings were not seen because $(WERROR_FLAGS) was not set
>> >in the Makefile. But they appear with toolchains that enforce more
>>checks.
>> >
>> >-Wno-deprecated seems useless.
>> >-Wno-strict-aliasing is added to avoid false positives.
>> >
>> >This patch cleans up unused variable, unused functions, wrong types,
>> >static declarations, etc. A lot of functions have unused parameters;
>> >it suggests that more clean-up could be needed.
>> >
>> >Signed-off-by: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
>> >---
>> > lib/librte_pmd_enic/Makefile         |  3 +-
>> > lib/librte_pmd_enic/enic.h           |  4 +-
>> > lib/librte_pmd_enic/enic_ethdev.c    | 20 ++++-----
>> 
>> Thomas, the name of this file got modified.  It was enic_etherdev.c in
>>my
>> submission.
>> Any idea how this happened?  I do not remember seeing a request for
>>this.
>
>Yes, sorry I forgot to request it.
>I renamed the file to be consistent with other drivers.
>Everywhere in DPDK we talk about ethdev for device operations, not
>etherdev.

Ok. 
Thank you.

>
>-- 
>Thomas

      reply	other threads:[~2014-12-04 10:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 14:59 [PATCH] enic: fix warnings Thomas Monjalon
     [not found] ` <1417532360-8568-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-12-03 14:52   ` Sujith Sankar (ssujith)
     [not found]     ` <D0A4DD27.2962A%ssujith-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2014-12-03 15:05       ` Thomas Monjalon
2014-12-03 15:10         ` Sujith Sankar (ssujith)
2014-12-04 12:06       ` Thomas Monjalon
2014-12-04 10:29   ` Sujith Sankar (ssujith)
     [not found]     ` <D0A6345D.2995A%ssujith-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2014-12-04 10:48       ` Thomas Monjalon
2014-12-04 10:58         ` Sujith Sankar (ssujith) [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=D0A63A74.29977%ssujith@cisco.com \
    --to=ssujith-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.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.