From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Vinod Koul <vinod.koul@intel.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 12:23:45 +0200 [thread overview]
Message-ID: <c6d21fbc-3339-4112-2ed8-2b18b3ec3b9c@ti.com> (raw)
In-Reply-To: <20170102102136.GY3573@localhost>
On 01/02/2017 12:21 PM, Vinod Koul wrote:
> 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 :)
Let's wait for Aaro to test it and I will resend after that.
--
Péter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Vinod Koul <vinod.koul@intel.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 12:23:45 +0200 [thread overview]
Message-ID: <c6d21fbc-3339-4112-2ed8-2b18b3ec3b9c@ti.com> (raw)
In-Reply-To: <20170102102136.GY3573@localhost>
On 01/02/2017 12:21 PM, Vinod Koul wrote:
> 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 :)
Let's wait for Aaro to test it and I will resend after that.
--
P�ter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Vinod Koul <vinod.koul@intel.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 12:23:45 +0200 [thread overview]
Message-ID: <c6d21fbc-3339-4112-2ed8-2b18b3ec3b9c@ti.com> (raw)
In-Reply-To: <20170102102136.GY3573@localhost>
On 01/02/2017 12:21 PM, Vinod Koul wrote:
> 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 :)
Let's wait for Aaro to test it and I will resend after that.
--
Péter
next prev parent reply other threads:[~2017-01-02 10:23 UTC|newest]
Thread overview: 11+ 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:07 ` Peter Ujfalusi
2017-01-02 10:09 ` Peter Ujfalusi
2017-01-02 10:09 ` Peter Ujfalusi
2017-01-02 10:09 ` Peter Ujfalusi
2017-01-02 10:21 ` Vinod Koul
2017-01-02 10:23 ` Peter Ujfalusi [this message]
2017-01-02 10:23 ` Peter Ujfalusi
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=c6d21fbc-3339-4112-2ed8-2b18b3ec3b9c@ti.com \
--to=peter.ujfalusi@ti.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=stable@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.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 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.