mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/3 v2] sh: fix DMA driver's descriptor chaining and  cookie assignment
Date: Thu, 17 Dec 2009 09:43:36 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0912170940470.5991@axis700.grange> (raw)
In-Reply-To: <29ab51dc0912170033s4185153emc1aaafdc83607532@mail.gmail.com>

On Thu, 17 Dec 2009, Nobuhiro Iwamatsu wrote:

> HI,
> 
> 2009/12/17 Guennadi Liakhovetski <g.liakhovetski@gmx.de>:
> > Hello Iwamatsu-san
> >
> > On Thu, 17 Dec 2009, Nobuhiro Iwamatsu wrote:
> >
> >> Hi,
> >>
> >> 2009/12/12 Nobuhiro Iwamatsu <iwamatsu@nigauri.org>:
> >> > Hi,
> >> >
> >> > Oh, I was going to check an old patch.
> >> >
> >> > 2009/12/11 Paul Mundt <lethal@linux-sh.org>:
> >> >> On Thu, Dec 10, 2009 at 06:35:11PM +0100, Guennadi Liakhovetski wrote:
> >> >>> The SH DMA driver wrongly assigns negative cookies to transfer descriptors,
> >> >>> also, its chaining of partial descriptors is broken. The latter problem is
> >> >>> usually invisible, because maximum transfer size per chunk is 16M, but if you
> >> >>> artificially set this limit lower, the driver fails. Since cookies are also
> >> >>> used in chunk management, both these problems are fixed in one patch. As side
> >> >>> effects a possible memory leak, when descriptors are prepared, but not
> >> >>> submitted, and multiple races have also been fixed.
> >> >>>
> >> >>> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> >> >>
> >> >> Looks good to me.
> >> > Me too.
> >> >
> >> > But I want to check other CPU of sh. I will do next week.
> >> > Please wait "Acked-by".
> >> >
> >> >
> >>
> >> I tested this patch. But I can not apply to Paul's git/HEAD.
> >> I re-create patch and I attached.
> >> This version of patch work fine.
> >> Guennadi, could you test this patch on sh7724?
> >
> > Thanks for testing. I looked at your version of my patch, and I don't
> > agree with it. You needlessly changed indentation in it and also forgot to
> > include a "From: " line in it to indicate its original authorship.
> > Besides, I think, Dan will be applying this patch on top of current next
> > or Linus' tree. Of course, it can be, that my version of the patch does
> > not apply to those trees either now. So, Dan, if you cannot merge my
> > version of this patch yourself, please, let me know, I'll rebase it, but
> > please do not use this version.
> 
> Yes, you are right.
> And sorry, I am not going to seize your patch by force.

Sure, I never assumed the opposite, that's why I said "you forgot." Same 
thing happened to me too recently, fortunately, I noticed it early enough 
to push a correct version. The actual problem with your version was 
white-space changes.

> I sent the patch which I revised at hand.

Thanks
Guennadi
---
Guennadi Liakhovetski

  reply	other threads:[~2009-12-17  8:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 17:35 [PATCH 0/3 v2] sh: fix dma driver Guennadi Liakhovetski
2009-12-10 17:35 ` [PATCH 1/3 v2] sh: stylistic improvements for the DMA driver Guennadi Liakhovetski
2009-12-10 17:35 ` [PATCH 2/3 v2] sh: fix DMA driver's descriptor chaining and cookie assignment Guennadi Liakhovetski
2009-12-11  8:02   ` Paul Mundt
2009-12-12  2:15     ` Nobuhiro Iwamatsu
2009-12-17  3:09       ` Nobuhiro Iwamatsu
2009-12-17  7:40         ` Guennadi Liakhovetski
2009-12-17  8:33           ` Nobuhiro Iwamatsu
2009-12-17  8:43             ` Guennadi Liakhovetski [this message]
2009-12-17 17:50               ` Dan Williams
2009-12-10 17:35 ` [PATCH 3/3] dmaengine: clarify the meaning of the DMA_CTRL_ACK flag Guennadi Liakhovetski
2009-12-12  4:58 ` [PATCH 0/3 v2] sh: fix dma driver Dan Williams

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=Pine.LNX.4.64.0912170940470.5991@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=dan.j.williams@intel.com \
    --cc=iwamatsu@nigauri.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®