From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2] igb: fix itnull.cocci warnings
Date: Thu, 07 Jan 2016 22:25:24 -0800 [thread overview]
Message-ID: <1452234324.19358.25.camel@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1512231354150.4367@hadrien>
On Wed, 2015-12-23 at 13:55 +0100, Julia Lawall wrote:
> The index variable of list_for_each_entry_safe should never be NULL.
>
> Generated by: scripts/coccinelle/iterators/itnull.cocci
>
> CC: Gangfeng Huang <gangfeng.huang@ni.com>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: Julia Lawall <julia.lawall@lip6.fr>
> ---
>
> v2: Add sign off
>
> ?igb_cdev.c |??? 3 +--
> ?1 file changed, 1 insertion(+), 2 deletions(-)
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160107/95924108/attachment-0001.asc>
prev parent reply other threads:[~2016-01-08 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 12:55 [Intel-wired-lan] [PATCH v2] igb: fix itnull.cocci warnings Julia Lawall
2016-01-08 6:25 ` Jeff Kirsher [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=1452234324.19358.25.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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