From: <Tudor.Ambarus@microchip.com>
To: <vkoul@kernel.org>
Cc: <f.fainelli@gmail.com>, <rjui@broadcom.com>,
<sbranden@broadcom.com>, <bcm-kernel-feedback-list@broadcom.com>,
<lars@metafoo.de>, <shawnguo@kernel.org>,
<s.hauer@pengutronix.de>, <kernel@pengutronix.de>,
<festevam@gmail.com>, <linux-imx@nxp.com>,
<sean.wang@mediatek.com>, <matthias.bgg@gmail.com>,
<daniel@zonque.org>, <haojian.zhuang@gmail.com>,
<robert.jarzmik@free.fr>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@somainline.org>,
<green.wan@sifive.com>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@foss.st.com>, <wens@csie.org>,
<jernej.skrabec@gmail.com>, <samuel@sholland.org>,
<ldewangan@nvidia.com>, <jonathanh@nvidia.com>,
<thierry.reding@gmail.com>, <peter.ujfalusi@gmail.com>,
<michal.simek@xilinx.com>, <tony@atomide.com>,
<krzysztof.kozlowski@linaro.org>, <trix@redhat.com>,
<radhey.shyam.pandey@xilinx.com>, <shravya.kumbham@xilinx.com>,
<harini.katakam@xilinx.com>, <swati.agarwal@amd.com>,
<dmaengine@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-sunxi@lists.linux.dev>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2] dmaengine: drivers: Use devm_platform_ioremap_resource()
Date: Wed, 9 Nov 2022 07:54:08 +0000 [thread overview]
Message-ID: <1f33df58-50e3-5cbc-7722-792473f2b738@microchip.com> (raw)
In-Reply-To: <20221108121837.540293-1-tudor.ambarus@microchip.com>
please ignore, will send v3
prev parent reply other threads:[~2022-11-09 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 12:18 [PATCH v2] dmaengine: drivers: Use devm_platform_ioremap_resource() Tudor Ambarus
2022-11-09 7:54 ` Tudor.Ambarus [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=1f33df58-50e3-5cbc-7722-792473f2b738@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=agross@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel@zonque.org \
--cc=dmaengine@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=festevam@gmail.com \
--cc=green.wan@sifive.com \
--cc=haojian.zhuang@gmail.com \
--cc=harini.katakam@xilinx.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=peter.ujfalusi@gmail.com \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=rjui@broadcom.com \
--cc=robert.jarzmik@free.fr \
--cc=s.hauer@pengutronix.de \
--cc=samuel@sholland.org \
--cc=sbranden@broadcom.com \
--cc=sean.wang@mediatek.com \
--cc=shawnguo@kernel.org \
--cc=shravya.kumbham@xilinx.com \
--cc=swati.agarwal@amd.com \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=trix@redhat.com \
--cc=vkoul@kernel.org \
--cc=wens@csie.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