From: Vinod Koul <vinod.koul@intel.com>
To: "Krzysztof Kozłowski" <k.kozlowski.k@gmail.com>
Cc: Michal Suchanek <hramrach@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dmaengine: pl330: do not emit loop for 1 byte transfer.
Date: Thu, 20 Aug 2015 06:27:36 +0530 [thread overview]
Message-ID: <20150820005736.GQ13546@localhost> (raw)
In-Reply-To: <CAJKOXPc7nBjXfWojOqX--zkPyBCByvbjj2SLHxLDkoXd627RRw@mail.gmail.com>
On Thu, Aug 20, 2015 at 08:58:49AM +0900, Krzysztof Kozłowski wrote:
> 2015-08-20 1:42 GMT+09:00 Vinod Koul <vinod.koul@intel.com>:
> >
> > On Thu, Jul 23, 2015 at 06:04:49PM +0200, Michal Suchanek wrote:
> > > When there is only one burst required do not emit loop instructions to
> > > loop exactly once. Emit just the body of the loop.
> >
> > Applied, thanks
>
> Where is the patch? I can't find it on my subscribed mailing lists
> (like dmaengine, LKML). It seems it is not present also in Google. The
> same applies to 2/2. I see only replies (Vinod's and Michal's) but not
> original email.
Now that you mentioned I did notice that too. Somehow the vger lists have
rejected this patch, althpugh it is addressed to both dmaengine and lkml
list
--
~Vinod
prev parent reply other threads:[~2015-08-20 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1438078857.git.hramrach@gmail.com>
[not found] ` <c73013adee799f93a2cd4f5329901479251a1594.1438078857.git.hramrach@gmail.com>
2015-08-19 16:41 ` [PATCH 2/2] dmaengine: pl330: event debug messages Vinod Koul
2015-08-19 18:19 ` Michal Suchanek
[not found] ` <a86692e4ffd0c56dfce5f6f6b353effedd9e5457.1438078857.git.hramrach@gmail.com>
2015-08-19 16:42 ` [PATCH 1/2] dmaengine: pl330: do not emit loop for 1 byte transfer Vinod Koul
2015-08-19 23:58 ` Krzysztof Kozłowski
2015-08-20 0:57 ` Vinod Koul [this message]
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=20150820005736.GQ13546@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=hramrach@gmail.com \
--cc=k.kozlowski.k@gmail.com \
--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.