From: Vinod Koul <vinod.koul@intel.com>
To: Appana Durga Kedareswara Rao <appanad@xilinx.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"akinobu.mita@gmail.com" <akinobu.mita@gmail.com>,
"joabreu@synopsys.com" <joabreu@synopsys.com>,
"mike.looijmans@topic.nl" <mike.looijmans@topic.nl>,
"kedare06@gmail.com" <kedare06@gmail.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [LINUX,3/4] dmaengine: xilinx_dma: Fix compilation warning
Date: Wed, 3 Jan 2018 10:57:46 +0530 [thread overview]
Message-ID: <20180103052746.GI18649@localhost> (raw)
On Wed, Jan 03, 2018 at 05:13:29AM +0000, Appana Durga Kedareswara Rao wrote:
> Hi Vinod,
>
> Thanks for the review...
>
> >
> >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote:
> >
> >Fix title here too
>
> Sure will fix in v2...
>
> >
> >BTW whats with LINUX tag in patches, pls drop them
>
> Ok will mention the Linux tag info in the cover letter patch from the next
> patch series on wards...
Please wrap your replies within 80chars. It is very hard to read! I have
reflown for readability
Can you explain what you mean by that info, what are you trying to convey?
next reply other threads:[~2018-01-03 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 5:27 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 9:09 [LINUX,3/4] dmaengine: xilinx_dma: Fix compilation warning Appana Durga Kedareswara Rao
2018-01-03 6:10 Appana Durga Kedareswara Rao
2018-01-03 5:13 Appana Durga Kedareswara Rao
2018-01-03 3:59 Vinod Koul
2017-12-21 10:11 Kedareswara rao Appana
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=20180103052746.GI18649@localhost \
--to=vinod.koul@intel.com \
--cc=akinobu.mita@gmail.com \
--cc=appanad@xilinx.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=joabreu@synopsys.com \
--cc=kedare06@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mike.looijmans@topic.nl \
/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).