netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Julia Lawall <Julia.Lawall@lip6.fr>
Cc: Yishai Hadas <yishaih@mellanox.com>,
	joe@perches.com, kernel-janitors@vger.kernel.org,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/26] net/mlx4_core: constify local structures
Date: Mon, 12 Sep 2016 07:59:54 +0300	[thread overview]
Message-ID: <20160912045954.GD8812@leon.nu> (raw)
In-Reply-To: <1473599168-30561-8-git-send-email-Julia.Lawall@lip6.fr>

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

On Sun, Sep 11, 2016 at 03:05:49PM +0200, Julia Lawall wrote:
> For structure types defined in the same file or local header files, find
> top-level static structure declarations that have the following
> properties:
> 1. Never reassigned.
> 2. Address never taken
> 3. Not passed to a top-level macro call
> 4. No pointer or array-typed field passed to a function or stored in a
> variable.
> Declare structures having all of these properties as const.
>
> Done using Coccinelle.
> Based on a suggestion by Joe Perches <joe@perches.com>.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>

Thanks,
Reviewed-by: Leon Romanovsky <leonro@mellanox.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-09-12  4:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 13:05 [PATCH 00/26] constify local structures Julia Lawall
2016-09-11 13:05 ` [PATCH 05/26] ARCNET: " Julia Lawall
2016-09-12 12:31   ` Julia Lawall
2016-09-11 13:05 ` [PATCH 06/26] ath: " Julia Lawall
2016-09-14 17:02   ` [06/26] " Kalle Valo
2016-09-11 13:05 ` [PATCH 07/26] net/mlx4_core: " Julia Lawall
2016-09-12  4:59   ` Leon Romanovsky [this message]
2016-09-11 13:05 ` [PATCH 08/26] iwlegacy: " Julia Lawall
2016-09-12 11:24   ` Stanislaw Gruszka
2016-09-11 13:05 ` [PATCH 11/26] can: " Julia Lawall
2016-09-12 12:33   ` Julia Lawall
2016-09-11 13:06 ` [PATCH 20/26] stmmac: pci: " Julia Lawall
2016-09-12 12:08   ` Julia Lawall
2016-09-11 13:06 ` [PATCH 23/26] sh_eth: " Julia Lawall
2016-09-11 18:14   ` Sergei Shtylyov
2016-09-12  8:55     ` Julia Lawall
2016-09-12  9:43     ` Julia Lawall
2016-09-11 13:06 ` [PATCH 25/26] pch_gbe: " Julia Lawall
2016-09-12  2:48   ` David Miller
2016-09-12  9:07     ` Julia Lawall
2016-09-12 16:33       ` David Miller
2016-09-12 12:25   ` Julia Lawall
     [not found] ` <1473599168-30561-1-git-send-email-Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
2016-09-11 13:06   ` [PATCH 21/26] rtlwifi: rtl818x: " Julia Lawall
2016-09-11 17:21   ` [PATCH 00/26] " Jarkko Sakkinen
2016-09-12  8:54     ` Julia Lawall
2016-09-12 13:16       ` Jarkko Sakkinen
2016-09-12 13:23         ` Julia Lawall
2016-09-12 13:43         ` Felipe Balbi
2016-09-12 13:52           ` Julia Lawall
2016-09-12 18:50             ` Jarkko Sakkinen
2016-09-12 13:57           ` Geert Uytterhoeven
2016-09-12 20:14           ` Jarkko Sakkinen
2016-09-12 21:11             ` Julia Lawall
2016-09-11 17:56   ` Joe Perches
2016-09-11 19:11     ` Julia Lawall

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=20160912045954.GD8812@leon.nu \
    --to=leon@kernel.org \
    --cc=Julia.Lawall@lip6.fr \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yishaih@mellanox.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).