From: Vinod Koul <vinod.koul@intel.com>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: julia.lawall@lip6.fr, linus.walleij@linaro.org,
dan.j.williams@intel.com, linux-arm-kernel@lists.infradead.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ste_dma40: make stedma40_chan_cfg const
Date: Mon, 21 Aug 2017 21:57:31 +0530 [thread overview]
Message-ID: <20170821162730.GQ3053@localhost> (raw)
In-Reply-To: <1502630584-6844-1-git-send-email-bhumirks@gmail.com>
On Sun, Aug 13, 2017 at 06:53:04PM +0530, Bhumika Goyal wrote:
> Make these const as they are only used during a copy operation.
> Done using Coccinelle.
Pls make sure you use the right subsystem tags, hint, you cna check git log
on that subsystem/file to find the right ones
Applied after fixing the tags, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ste_dma40: make stedma40_chan_cfg const
Date: Mon, 21 Aug 2017 21:57:31 +0530 [thread overview]
Message-ID: <20170821162730.GQ3053@localhost> (raw)
In-Reply-To: <1502630584-6844-1-git-send-email-bhumirks@gmail.com>
On Sun, Aug 13, 2017 at 06:53:04PM +0530, Bhumika Goyal wrote:
> Make these const as they are only used during a copy operation.
> Done using Coccinelle.
Pls make sure you use the right subsystem tags, hint, you cna check git log
on that subsystem/file to find the right ones
Applied after fixing the tags, thanks
--
~Vinod
next prev parent reply other threads:[~2017-08-21 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 13:23 [PATCH] ste_dma40: make stedma40_chan_cfg const Bhumika Goyal
2017-08-13 13:23 ` Bhumika Goyal
2017-08-14 12:40 ` Linus Walleij
2017-08-14 12:40 ` Linus Walleij
2017-08-21 16:27 ` Vinod Koul [this message]
2017-08-21 16:27 ` Vinod Koul
2017-08-21 16:40 ` Bhumika Goyal
2017-08-21 16:40 ` Bhumika Goyal
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=20170821162730.GQ3053@localhost \
--to=vinod.koul@intel.com \
--cc=bhumirks@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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.