Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Angelo Dureghello <adureghello@baylibre.com>
Cc: "Greg Ungerer" <gerg@linux-m68k.org>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Steven King" <sfking@fdwdc.com>, "Arnd Bergmann" <arnd@arndb.de>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Greg Ungerer" <gerg@uclinux.org>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v5 06/10] m68k: stmark2: use ioport.h macros for resources
Date: Thu, 11 Jun 2026 10:18:41 +0300	[thread overview]
Message-ID: <aiphUQvNzzaoTjxX@ashevche-desk.local> (raw)
In-Reply-To: <20260610-wip-stmark2-dac-v5-6-b76b83366d5c@baylibre.com>

On Wed, Jun 10, 2026 at 10:35:11PM +0200, Angelo Dureghello wrote:

> Change resource declaration using DEFINE_RES_*() macros.
> DEFINE_DMA_RES() is for a single dma channel, not a range, so used twice.
> 
> Also, some drivers assume IRQ resources are from index 1, so just to stay
> uniform, moved IRQ resource at index 1.

Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>

-- 
With Best Regards,
Andy Shevchenko




  reply	other threads:[~2026-06-11  7:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 20:35 [PATCH v5 00/10] add mcf54415 DAC driver Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 01/10] m68k: mcf5441x: fix clocks numbering Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 02/10] m68k: mcf5441x: add clock for DAC channel 1 Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 03/10] m68k: add DAC modules base addresses Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 04/10] m68k: mcf5441x: add CCM registers Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 05/10] m68k: mcf5441x: add CCR MISCCR2 bitfields Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 06/10] m68k: stmark2: use ioport.h macros for resources Angelo Dureghello
2026-06-11  7:18   ` Andy Shevchenko [this message]
2026-06-10 20:35 ` [PATCH v5 07/10] m68k: stmark2: add mcf5441x DAC platform devices Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 08/10] m68k: stmark2: enable DACs outputs Angelo Dureghello
2026-06-10 20:35 ` [PATCH v5 09/10] iio: dac: add mcf54415 DAC Angelo Dureghello
2026-06-11 10:48   ` Jonathan Cameron
2026-06-15 11:20     ` Angelo Dureghello
2026-06-21 12:55       ` Jonathan Cameron
2026-06-10 20:35 ` [PATCH v5 10/10] m68k: defconfig: update stmark2 defconfig Angelo Dureghello
2026-06-11 13:04 ` [PATCH v5 00/10] add mcf54415 DAC driver Greg Ungerer

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=aiphUQvNzzaoTjxX@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=adureghello@baylibre.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andy@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dlechner@baylibre.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=jic23@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=sfking@fdwdc.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