From: Mark Brown <broonie@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org,
Thomas Zimmermann <tzimmermann@suse.de>,
Will Deacon <will@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Jaroslav Kysela <perex@perex.cz>,
iommu@lists.linux.dev, linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Yong Wu <yong.wu@mediatek.com>
Subject: Re: [PATCH 1/2] component: Add helper for device nodes
Date: Thu, 3 Nov 2022 18:32:43 +0000 [thread overview]
Message-ID: <Y2QJS+M1xX2RaK1v@sirena.org.uk> (raw)
In-Reply-To: <20221103182222.2247724-2-sean.anderson@seco.com>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Thu, Nov 03, 2022 at 02:22:21PM -0400, Sean Anderson wrote:
> There is a common case where component_patch_add_release is called with
> component_release_of/component_compare_of and a device node. Add a
> helper and convert existing users.
The usual pattern here would be to split adding the helper from updating
to use the helper - it makes things easier to merge.
Acked-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-03 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:22 [PATCH 0/2] drm: Add component_match_add_of and convert users of drm_of_component_match_add Sean Anderson
2022-11-03 18:22 ` [PATCH 1/2] component: Add helper for device nodes Sean Anderson
2022-11-03 18:32 ` Mark Brown [this message]
2022-11-03 18:22 ` [PATCH 2/2] drm: Convert users of drm_of_component_match_add to component_match_add_of Sean Anderson
2022-11-07 20:27 ` sarha
2022-12-16 17:08 ` [PATCH 0/2] drm: Add component_match_add_of and convert users of drm_of_component_match_add Sean Anderson
2022-12-16 17:41 ` Robin Murphy
2022-12-22 21:24 ` Sean Anderson
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=Y2QJS+M1xX2RaK1v@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=robin.murphy@arm.com \
--cc=sean.anderson@seco.com \
--cc=tiwai@suse.com \
--cc=tzimmermann@suse.de \
--cc=will@kernel.org \
--cc=yong.wu@mediatek.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).