All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH 1/2] dma: tegra20-apbdma: err message correction
Date: Fri, 10 May 2013 17:04:43 -0600	[thread overview]
Message-ID: <518D7D0B.3080304@wwwdotorg.org> (raw)
In-Reply-To: <1368220014-12036-1-git-send-email-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 05/10/2013 03:06 PM, Dmitry Osipenko wrote:
> Fixed err msg params order on irq request fail.

These two look fine to me, but patches to DMA drivers should be taken
through the DMA driver tree; that's Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
and Dan Williams <djbw-b10kYP2dOMg@public.gmane.org>.

  parent reply	other threads:[~2013-05-10 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 21:06 [PATCH 1/2] dma: tegra20-apbdma: err message correction Dmitry Osipenko
     [not found] ` <1368220014-12036-1-git-send-email-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-10 21:06   ` [PATCH 2/2] dma: tegra: avoid channel lock up after free Dmitry Osipenko
2013-05-10 23:04   ` Stephen Warren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-11 16:30 [PATCH 1/2] dma: tegra20-apbdma: err message correction Dmitry Osipenko
     [not found] ` <1368289853-20011-1-git-send-email-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-13  4:00   ` Laxman Dewangan
2013-05-13  4:04   ` Laxman Dewangan
     [not found]     ` <51906635.3040507-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-05-30 18:05       ` Vinod Koul

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=518D7D0B.3080304@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.