DMA Engine development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Andy Shevchenko <andy@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Viresh Kumar <vireshk@kernel.org>
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
	"Frank Li" <Frank.Li@kernel.org>,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 0/2] dmaengine: Use named initializers for arrays of pci_device_id
Date: Thu, 11 Jun 2026 09:45:08 +0200	[thread overview]
Message-ID: <cover.1781161455.git.ukleinek@kernel.org> (raw)

From: Uwe Kleine-König <ukleinek@kernel.org>

Hello,

(implicit) v1 of this series was only a single patch, it's archived at
https://lore.kernel.org/all/20260504102008.1996139-2-u.kleine-koenig@baylibre.com .

Andy criticised that the changes to the HSU driver don't fit to the
remaining stuff in that patch. So I put that change in a separate patch.

Andy also suggested to use the PCI_DEVICE_DATA(). I didn't implement that as we
don't agree about this being better. He likes it being compact, I don't like it
as it hides assignments in a macro that I prefer to be explicit.

Best regards
Uwe

Uwe Kleine-König (The Capable Hub) (2):
  dmaengine: hsu: Drop unused platform driver data
  dmaengine: Consistently define pci_device_ids using named initializers

 drivers/dma/amd/ptdma/ptdma-pci.c  |  4 ++--
 drivers/dma/dw-edma/dw-edma-pcie.c |  2 +-
 drivers/dma/dw/pci.c               | 22 +++++++++++-----------
 drivers/dma/hsu/pci.c              |  4 ++--
 drivers/dma/pch_dma.c              | 26 +++++++++++++-------------
 5 files changed, 29 insertions(+), 29 deletions(-)


base-commit: abe651837cb394f76d738a7a747322fca3bf17ba
-- 
2.47.3


             reply	other threads:[~2026-06-11  8:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  7:45 Uwe Kleine-König (The Capable Hub) [this message]
2026-06-11  7:45 ` [PATCH v2 1/2] dmaengine: hsu: Drop unused platform driver data Uwe Kleine-König (The Capable Hub)
2026-06-11  8:11   ` sashiko-bot
2026-06-11  8:30   ` Andy Shevchenko
2026-06-11  7:45 ` [PATCH v2 2/2] dmaengine: Consistently define pci_device_ids using named initializers Uwe Kleine-König (The Capable Hub)
2026-06-11  8:33   ` Andy Shevchenko

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=cover.1781161455.git.ukleinek@kernel.org \
    --to=u.kleine-koenig@baylibre.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Frank.Li@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=ukleinek@kernel.org \
    --cc=vireshk@kernel.org \
    --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