All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	vinod.koul@intel.com, devicetree-discuss@lists.ozlabs.org,
	spear-devel@list.st.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 2/3] dmaengine: dw_dmac: Enhance device tree support
Date: Wed, 12 Dec 2012 10:42:02 +0200	[thread overview]
Message-ID: <1355301722.31620.68.camel@smile> (raw)
In-Reply-To: <201212102208.52347.arnd@arndb.de>

On Mon, 2012-12-10 at 22:08 +0000, Arnd Bergmann wrote: 
> The build bug is not the problem however, but the abuse of the
> API is. Andy, are you sure you understood what this does when
> you gave you Reviewed-by comment?

Thank you for pointing this out to refresh my memories and go through
documentation again.

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

WARNING: multiple messages have this Message-ID (diff)
From: andriy.shevchenko@linux.intel.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/3] dmaengine: dw_dmac: Enhance device tree support
Date: Wed, 12 Dec 2012 10:42:02 +0200	[thread overview]
Message-ID: <1355301722.31620.68.camel@smile> (raw)
In-Reply-To: <201212102208.52347.arnd@arndb.de>

On Mon, 2012-12-10 at 22:08 +0000, Arnd Bergmann wrote: 
> The build bug is not the problem however, but the abuse of the
> API is. Andy, are you sure you understood what this does when
> you gave you Reviewed-by comment?

Thank you for pointing this out to refresh my memories and go through
documentation again.

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

  parent reply	other threads:[~2012-12-12  8:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16  4:19 [PATCH V3 1/3] dmaengine: dw_dmac: Update documentation style comments for dw_dma_platform_data Viresh Kumar
2012-10-16  4:19 ` Viresh Kumar
2012-10-16  4:19 ` [PATCH V3 2/3] dmaengine: dw_dmac: Enhance device tree support Viresh Kumar
2012-10-16  4:19   ` Viresh Kumar
2012-10-26  8:55   ` Viresh Kumar
2012-10-26  8:55     ` Viresh Kumar
2012-10-26  8:48     ` Vinod Koul
2012-10-26  8:48       ` Vinod Koul
2012-10-26  9:05       ` Viresh Kumar
2012-10-26  9:05         ` Viresh Kumar
2012-10-26  9:10         ` Vinod Koul
2012-10-26  9:10           ` Vinod Koul
2012-12-10 22:08   ` Arnd Bergmann
2012-12-10 22:08     ` Arnd Bergmann
2012-12-10 22:21     ` Arnd Bergmann
2012-12-10 22:21       ` Arnd Bergmann
2012-12-12  3:00     ` Viresh Kumar
2012-12-12  3:00       ` Viresh Kumar
2012-12-12  8:40       ` Andy Shevchenko
2012-12-12  8:40         ` Andy Shevchenko
2012-12-12  8:43         ` Viresh Kumar
2012-12-12  8:43           ` Viresh Kumar
2012-12-12  8:43           ` Viresh Kumar
2013-01-08 23:09       ` Arnd Bergmann
2013-01-08 23:09         ` Arnd Bergmann
2012-12-12  8:42     ` Andy Shevchenko [this message]
2012-12-12  8:42       ` Andy Shevchenko
2012-10-16  4:19 ` [PATCH V3 3/3] ARM: SPEAr13xx: Pass DW DMAC platform data from DT Viresh Kumar
2012-10-16  4:19   ` Viresh Kumar

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=1355301722.31620.68.camel@smile \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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.