From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 10E753FFABE for ; Mon, 2 Mar 2026 14:39:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772462395; cv=none; b=BS69WlxBVFiKcN7m8eoMkquofIa+K92lEQupFM8ehLqEcocxfLebTkNdEhZM69h/iLN08rZ01FDIZ2rasAPjRfDjf7dh4xKJhHGm3kjrRGYWC/FbiEsqokLiQ0eoqIRqfd+hncfysZ5vQnJ+JTGjisLynJslarX8dqbVgeHDq6Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772462395; c=relaxed/simple; bh=XvdaJG//De7KlW7eAqEXOrUhRmsZMSWL0JPrhyoVVjo=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=Ew9xYWhVwxkjmMrq7ta+qBE5cfl5MPuntpVUtPHBF2jFmMBtBqHEXfIBRov7yjNuZ/+l5Uy9SsUPdnArMgCy99LTKW/zr845zjhINjedcok0Q5e4atJdamXU0pafLQaG/6zBZVeyhP/SCMEQl5iGWIL6PqnXms6SmGmhLABdD4E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ZK9gu2aK; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ZK9gu2aK" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F4F6C19423; Mon, 2 Mar 2026 14:39:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772462394; bh=XvdaJG//De7KlW7eAqEXOrUhRmsZMSWL0JPrhyoVVjo=; h=Date:Subject:Cc:To:From:References:In-Reply-To:From; b=ZK9gu2aK894ymhI6SkKpsxh2wZz5Q0C/iVnsJDkFuUNkOd38m8zvv4qKpbZbMxHuS U8cLQHhriByIyalyKl19GZSNFNqhbmxpRHRHRTfu4dVU+JwdohAt+MsZSh4Br7tzL+ 1HCgEDvMotBd2uVmg5d0PyP8dbfoabBCYgBksbEY7WeJCsw9KIj7GJvVHtN4CVGbQ9 R519pwSQVF6uD1QnSMKTIs5ptFOCtJSJ6wUSAkvEpAcAiySCSNRLRLqZZGDQWKg5/W v5MSa0own0vbM3knxlHOABM9HWPPuzWhtjyjCo8F3Pa7gtcxPf6aFoBGwLRKQ71FRT VIneYetkyEhVw== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 02 Mar 2026 15:39:51 +0100 Message-Id: Subject: Re: [PATCH v2 0/3] Allow attaching software node when registering platform devices Cc: "Greg Kroah-Hartman" , "Rafael J. Wysocki" , "Arnd Bergmann" , "Bartosz Golaszewski" , "Hans de Goede" , To: "Dmitry Torokhov" From: "Danilo Krummrich" References: <20260214025246.2095239-1-dmitry.torokhov@gmail.com> In-Reply-To: On Mon Mar 2, 2026 at 1:42 AM CET, Danilo Krummrich wrote: > On Sun Mar 1, 2026 at 6:02 AM CET, Dmitry Torokhov wrote: >>> Unless there there is any contrary feedback from Greg or Rafael, I can = pick up >>> the series after -rc1 is out and hand out a signed tag for the two of t= hose. >> >> Yes, could this be applied please? I have a few patches that depend on >> this that I'd like to send out. > > Sorry for the delay, will do tomorrow! Again, sorry for the delay, I gave this some extra cycles to make sure Greg= and Rafael have a chance to comment (especially since this will be shared with = other trees). I now applied this to driver-core-testing; I will share a signed tag once I= have the 0day result. I have one consideration about the if (pdevinfo->swnode && pdevinfo->properties) return ERR_PTR(-EINVAL); case (which I hate we can't catch at compile time). Maybe it is worth to at least print a warning? Thanks, Danilo