From: Vinod Koul <vinod.koul@intel.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Dan Williams <dan.j.williams@intel.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: ioatdma: constify dca_ops structures
Date: Mon, 16 Nov 2015 03:54:24 +0000 [thread overview]
Message-ID: <20151116035805.GD25173@localhost> (raw)
In-Reply-To: <alpine.DEB.2.10.1511131244230.2561@hadrien>
On Fri, Nov 13, 2015 at 12:46:00PM +0100, Julia Lawall wrote:
> The dca_ops structure is never modified, so declare it as const.
>
> Done with the help of Coccinelle.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Dan Williams <dan.j.williams@intel.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: ioatdma: constify dca_ops structures
Date: Mon, 16 Nov 2015 09:28:05 +0530 [thread overview]
Message-ID: <20151116035805.GD25173@localhost> (raw)
In-Reply-To: <alpine.DEB.2.10.1511131244230.2561@hadrien>
On Fri, Nov 13, 2015 at 12:46:00PM +0100, Julia Lawall wrote:
> The dca_ops structure is never modified, so declare it as const.
>
> Done with the help of Coccinelle.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2015-11-16 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 10:31 [PATCH] dmaengine: ioatdma: constify dcs_ops structures Julia Lawall
2015-11-13 10:31 ` Julia Lawall
2015-11-13 11:46 ` [PATCH v2] dmaengine: ioatdma: constify dca_ops structures Julia Lawall
2015-11-13 11:46 ` Julia Lawall
2015-11-13 16:38 ` Dan Williams
2015-11-13 16:38 ` Dan Williams
2015-11-16 3:54 ` Vinod Koul [this message]
2015-11-16 3:58 ` Vinod Koul
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=20151116035805.GD25173@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.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 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.