public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Daniel Scally <djrscally@gmail.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Yong Zhi <yong.zhi@intel.com>, Bingbu Cao <bingbu.cao@intel.com>,
	Tianshu Qiu <tian.shu.qiu@intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v3 0/4] software nodes: Get rid of rarely used APIs
Date: Tue, 17 Jan 2023 19:03:46 +0100	[thread overview]
Message-ID: <Y8bjAhZhcUOhFn/p@kroah.com> (raw)
In-Reply-To: <20221228094922.84119-1-andriy.shevchenko@linux.intel.com>

On Wed, Dec 28, 2022 at 11:49:18AM +0200, Andy Shevchenko wrote:
> There is only a single user of software_node_register_nodes() and
> software_node_unregister_nodes(). Convert it to what others use and
> remove the unneeded APIs.
> 
> Since we have maintainers' tags applied it can be routed either through
> driver core or media tree — whatever you prefer.

I'll take these now, thanks!

greg k-h

      parent reply	other threads:[~2023-01-17 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  9:49 [PATCH v3 0/4] software nodes: Get rid of rarely used APIs Andy Shevchenko
2022-12-28  9:49 ` [PATCH v3 1/4] media: ipu3-cio2: Don't dereference fwnode handle Andy Shevchenko
2022-12-28  9:49 ` [PATCH v3 2/4] media: ipu3-cio2: Convert to use software_node_register_node_group() Andy Shevchenko
2022-12-28  9:49 ` [PATCH v3 3/4] software node: Switch property entry test to a new API Andy Shevchenko
2022-12-28  9:49 ` [PATCH v3 4/4] software node: Remove unused APIs Andy Shevchenko
2023-01-17 18:03 ` Greg Kroah-Hartman [this message]

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=Y8bjAhZhcUOhFn/p@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=djrscally@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rafael@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tian.shu.qiu@intel.com \
    --cc=yong.zhi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox