dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Huang Shijie <sjhuang@iluvatar.ai>,
	Alexandre Bailon <abailon@baylibre.com>,
	vkoul@kernel.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org, dave.jiang@intel.com,
	radhey.shyam.pandey@xilinx.com, appana.durga.rao@xilinx.com,
	jmkrzyszt@gmail.com, gomonovych@gmail.com, keescook@chromium.org,
	horms+renesas@verge.net.au, geert+renesas@glider.be,
	shawnguo@kernel.org, baoyou.xie@linaro.org,
	michal.simek@xilinx.com, baohua@kernel.org,
	ludovic.desroches@microchip.com, linus.walleij@linaro.org,
	david.brown@linaro.org
Subject: [09/46] dmaengine: cppi41: use dmaenginem_async_device_register to simplify the code
Date: Wed, 8 Aug 2018 00:16:52 -0700	[thread overview]
Message-ID: <20180808071652.GP99251@atomide.com> (raw)

* Peter Ujfalusi <peter.ujfalusi@ti.com> [180807 07:05]:
> But does the removed three lines worth over the clarity of how the
> module removal is proceeding?
> 
> Alexandre and Tony put lots of effort to the cppi4 driver, I let them
> decide.

Up to you guys as far as I'm concerned.

Tony
---
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-08-08  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  7:16 Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-07  7:16 [09/46] dmaengine: cppi41: use dmaenginem_async_device_register to simplify the code Huang Shijie
2018-08-07  7:01 Peter Ujfalusi
2018-08-06  3:28 Huang Shijie
2018-08-03  8:02 Huang Shijie
2018-08-03  7:55 Peter Ujfalusi
2018-08-03  7:19 Huang Shijie

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=20180808071652.GP99251@atomide.com \
    --to=tony@atomide.com \
    --cc=abailon@baylibre.com \
    --cc=appana.durga.rao@xilinx.com \
    --cc=baohua@kernel.org \
    --cc=baoyou.xie@linaro.org \
    --cc=dave.jiang@intel.com \
    --cc=david.brown@linaro.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gomonovych@gmail.com \
    --cc=horms+renesas@verge.net.au \
    --cc=jmkrzyszt@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=michal.simek@xilinx.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=radhey.shyam.pandey@xilinx.com \
    --cc=shawnguo@kernel.org \
    --cc=sjhuang@iluvatar.ai \
    --cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).