From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
aaro.koskinen@iki.fi, tony@atomide.com, stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: omap-dma: Fix dynamic lch_map alocation
Date: Mon, 2 Jan 2017 15:51:36 +0530 [thread overview]
Message-ID: <20170102102136.GY3573@localhost> (raw)
In-Reply-To: <617c5c88-aff7-ea60-a6d4-3b18b3f3dab9@ti.com>
On Mon, Jan 02, 2017 at 12:09:03PM +0200, Peter Ujfalusi wrote:
> I have typo in the subject line: s/alocation/allocation ...
>
> Vinod: can you fix it up or should I resend?
Either way is fine :)
--
~Vinod
next prev parent reply other threads:[~2017-01-02 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 10:07 [PATCH] dmaengine: omap-dma: Fix dynamic lch_map alocation Peter Ujfalusi
2017-01-02 10:09 ` Peter Ujfalusi
2017-01-02 10:21 ` Vinod Koul [this message]
2017-01-02 10:23 ` Peter Ujfalusi
2017-01-03 3:41 ` Vinod Koul
2017-01-02 19:13 ` Aaro Koskinen
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=20170102102136.GY3573@localhost \
--to=vinod.koul@intel.com \
--cc=aaro.koskinen@iki.fi \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.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).