From: Vinod Koul <vkoul@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: dmaengine@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>
Subject: Re: [PATCH v1 1/2] dmaengine: stm32-dmamux: Switch to use device_property_count_u32()
Date: Mon, 29 Jul 2019 12:25:43 +0530 [thread overview]
Message-ID: <20190729065543.GJ12733@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20190723190757.67351-1-andriy.shevchenko@linux.intel.com>
On 23-07-19, 22:07, Andy Shevchenko wrote:
> Use use device_property_count_u32() directly, that makes code neater.
Applied both, thanks
--
~Vinod
prev parent reply other threads:[~2019-07-29 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 19:07 [PATCH v1 1/2] dmaengine: stm32-dmamux: Switch to use device_property_count_u32() Andy Shevchenko
2019-07-23 19:07 ` [PATCH v1 2/2] dmaengine: stm32-mdma: " Andy Shevchenko
2019-07-29 6:55 ` Vinod Koul [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=20190729065543.GJ12733@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
/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).