All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Vinod Koul <vinod.koul@intel.com>,
	linux-kernel@vger.kernel.org,
	spear-devel <spear-devel@list.st.com>
Subject: Re: [PATCH 2/2] dw_dmac: return proper residue value
Date: Wed, 23 Jan 2013 12:33:55 +0200	[thread overview]
Message-ID: <1358937235.12502.70.camel@smile> (raw)
In-Reply-To: <CAKohpokH_8-u3tt-Zv=Zxe+wcESQfecCFCEPFGrVMWCLDr5OAQ@mail.gmail.com>

On Wed, 2013-01-23 at 15:54 +0530, Viresh Kumar wrote: 
> On 23 January 2013 15:50, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > What about to calc len every time from lli.* instead of keeping it in
> > the len field of the descriptor?
> 
> That's even bad.. we spend time on something for no good reason. :)
> I would still suggest you to add len and total_len in descriptor :)

Okay, let's stick to this one for now.
I will come with patch v2 soon.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2013-01-23 10:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21  9:00 [PATCH 1/2] dw_dmac: fill len field of the descriptor Andy Shevchenko
2013-01-21  9:00 ` [PATCH 2/2] dw_dmac: return proper residue value Andy Shevchenko
2013-01-21  8:49   ` Vinod Koul
2013-01-21  9:45     ` Andy Shevchenko
2013-01-21 14:22       ` Vinod Koul
2013-01-22  7:24         ` Andy Shevchenko
2013-01-22  8:11   ` Viresh Kumar
2013-01-22  9:22     ` Andy Shevchenko
2013-01-22  9:40       ` Viresh Kumar
2013-01-23  9:12         ` Andy Shevchenko
2013-01-23  9:22           ` Viresh Kumar
2013-01-23  9:36             ` Andy Shevchenko
2013-01-23  9:51               ` Viresh Kumar
2013-01-23 10:20                 ` Andy Shevchenko
2013-01-23 10:24                   ` Viresh Kumar
2013-01-23 10:33                     ` Andy Shevchenko [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=1358937235.12502.70.camel@smile \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spear-devel@list.st.com \
    --cc=vinod.koul@intel.com \
    --cc=viresh.kumar@linaro.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.