From: David Miller <davem@davemloft.net>
To: kan.liang@intel.com
Cc: netdev@vger.kernel.org, bwh@kernel.org, ben@decadent.org.uk,
andi@firstfloor.org, jesse.brandeburg@intel.com,
shannon.nelson@intel.com, f.fainelli@gmail.com,
alexander.duyck@gmail.com, jeffrey.t.kirsher@intel.com,
carolyn.wyborny@intel.com, donald.c.skidmore@intel.com,
mitch.a.williams@intel.com, ogerlitz@mellanox.com,
edumazet@google.com, jiri@mellanox.com, sfeldma@gmail.com,
gospo@cumulusnetworks.com, sasha.levin@oracle.com,
dsahern@gmail.com, tj@kernel.org, cascardo@redhat.com,
corbet@lwn.net, decot@googlers.com
Subject: Re: [PATCH V6 2/8] test_bitmap: unit tests for lib/bitmap.c
Date: Thu, 18 Feb 2016 14:00:08 -0500 (EST) [thread overview]
Message-ID: <20160218.140008.1645431745407584155.davem@davemloft.net> (raw)
In-Reply-To: <1455625964-8943-3-git-send-email-kan.liang@intel.com>
From: Kan Liang <kan.liang@intel.com>
Date: Tue, 16 Feb 2016 07:32:38 -0500
> @@ -43,6 +43,7 @@ obj-$(CONFIG_TEST_USER_COPY) += test_user_copy.o
> obj-$(CONFIG_TEST_STATIC_KEYS) += test_static_keys.o
> obj-$(CONFIG_TEST_STATIC_KEYS) += test_static_key_base.o
> obj-$(CONFIG_TEST_PRINTF) += test_printf.o
> +obj-$(CONFIG_TEST_BITMAP) += test_bitmap.o
...
>
> -TEST_PROGS := printf.sh
> +TEST_PROGS := printf.sh bitmap.sh
I see neither test_bitmap.c nor bitmap.sh in this patch, perhaps some
forgotten git add commands?
next prev parent reply other threads:[~2016-02-18 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 12:32 [PATCH V5 0/8] ethtool per queue parameters support Kan Liang
2016-02-16 12:32 ` [PATCH V6 1/8] lib/bitmap.c: conversion routines to/from u32 array Kan Liang
2016-02-16 12:32 ` [PATCH V6 2/8] test_bitmap: unit tests for lib/bitmap.c Kan Liang
2016-02-18 19:00 ` David Miller [this message]
2016-02-18 19:06 ` Liang, Kan
2016-02-16 12:32 ` [PATCH V5 3/8] net/ethtool: introduce a new ioctl for per queue setting Kan Liang
2016-02-16 12:32 ` [PATCH V5 4/8] net/ethtool: support get coalesce per queue Kan Liang
2016-02-17 0:57 ` Ben Hutchings
2016-02-16 12:32 ` [PATCH V5 5/8] net/ethtool: support set " Kan Liang
2016-02-17 1:00 ` Ben Hutchings
2016-02-16 12:32 ` [PATCH V5 6/8] i40e: queue-specific settings for interrupt moderation Kan Liang
2016-02-16 12:32 ` [PATCH V5 7/8] i40e/ethtool: support coalesce getting by queue Kan Liang
2016-02-16 12:32 ` [PATCH V5 8/8] i40e/ethtool: support coalesce setting " Kan Liang
-- strict thread matches above, loose matches on Subject: below --
2016-02-08 7:45 [PATCH V4 0/8] ethtool per queue parameters support Kan Liang
2016-02-08 7:45 ` [PATCH V6 2/8] test_bitmap: unit tests for lib/bitmap.c Kan Liang
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=20160218.140008.1645431745407584155.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=andi@firstfloor.org \
--cc=ben@decadent.org.uk \
--cc=bwh@kernel.org \
--cc=carolyn.wyborny@intel.com \
--cc=cascardo@redhat.com \
--cc=corbet@lwn.net \
--cc=decot@googlers.com \
--cc=donald.c.skidmore@intel.com \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@mellanox.com \
--cc=kan.liang@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sasha.levin@oracle.com \
--cc=sfeldma@gmail.com \
--cc=shannon.nelson@intel.com \
--cc=tj@kernel.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).