From: "Danilo Krummrich" <dakr@kernel.org>
To: <johannes.goede@oss.qualcomm.com>
Cc: "Mehdi Djait" <mehdi.djait@linux.intel.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
<linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Daniel Scally" <djrscally@gmail.com>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Charles Keepax" <ckeepax@opensource.cirrus.com>,
<linux-acpi@vger.kernel.org>, "Kenneth Crudup" <kenny@panix.com>,
<linux-media@vger.kernel.org>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 1/1] software node: Also support referencing non-constant software nodes
Date: Fri, 19 Dec 2025 16:47:30 +0100 [thread overview]
Message-ID: <DF2B7AJU1HWM.27NQV4BLY8QWJ@kernel.org> (raw)
In-Reply-To: <29830128-8b75-4c57-ac55-0158f3688f12@oss.qualcomm.com>
On Fri Dec 19, 2025 at 4:38 PM CET, johannes.goede wrote:
> No reason other then me not paying attention and since this fixes
> an issue related to IPU6 cameras I typed the above on auto-pilot,
> my bad.
>
> You're completely right this should go upstream through driver core
> and my request makes no sense, sorry.
No worries, could have been there is a specific reason. :)
next prev parent reply other threads:[~2025-12-19 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 0:59 IPU6 subsystem broken in 6.19-rc1 due to d7cdbbc93c5 ("software node: allow referencing firmware nodes") Kenneth Crudup
2025-12-19 1:04 ` Kenneth Crudup
2025-12-19 8:36 ` [PATCH 1/1] software node: Also support referencing non-constant software nodes Sakari Ailus
2025-12-19 13:13 ` Mehdi Djait
2025-12-19 15:05 ` johannes.goede
2025-12-19 15:11 ` Danilo Krummrich
2025-12-19 15:38 ` johannes.goede
2025-12-19 15:47 ` Danilo Krummrich [this message]
2025-12-19 20:55 ` Kenneth Crudup
2025-12-22 12:36 ` Danilo Krummrich
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=DF2B7AJU1HWM.27NQV4BLY8QWJ@kernel.org \
--to=dakr@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=kenny@panix.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=p.zabel@pengutronix.de \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.