public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 0/5] ASoC: Intel: Balance ACPI device refcount
Date: Thu, 12 Jan 2023 13:28:47 +0200	[thread overview]
Message-ID: <20230112112852.67714-1-andriy.shevchenko@linux.intel.com> (raw)

While looking for the open coded put_device(&adev->dev) cases, where
adev stands for ACPI device, I noticed that in a few ASoC Intel driver,
among others, the refcount is not balanced properly in some cases.

This series fixes that issue and converts to use acpi_dev_put().

Changelog v2:
- split Intel drivers out from others (Pierre)
- sent with cover letter (Mark)

Andy Shevchenko (5):
  ASoC: Intel: bytcht_es8316: Drop reference count of ACPI device after
    use
  ASoC: Intel: bytcr_rt5651: Drop reference count of ACPI device after
    use
  ASoC: Intel: bytcr_rt5640: Drop reference count of ACPI device after
    use
  ASoC: Intel: bytcr_wm5102: Drop reference count of ACPI device after
    use
  ASoC: Intel: sof_es8336: Drop reference count of ACPI device after use

 sound/soc/intel/boards/bytcht_es8316.c | 20 ++++++++++++--------
 sound/soc/intel/boards/bytcr_rt5640.c  | 12 ++++++------
 sound/soc/intel/boards/bytcr_rt5651.c  |  2 +-
 sound/soc/intel/boards/bytcr_wm5102.c  |  2 +-
 sound/soc/intel/boards/sof_es8336.c    | 14 ++++++++------
 5 files changed, 28 insertions(+), 22 deletions(-)

-- 
2.39.0


             reply	other threads:[~2023-01-12 11:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 11:28 Andy Shevchenko [this message]
2023-01-12 11:28 ` [PATCH v2 1/5] ASoC: Intel: bytcht_es8316: Drop reference count of ACPI device after use Andy Shevchenko
2023-01-12 11:28 ` [PATCH v2 2/5] ASoC: Intel: bytcr_rt5651: " Andy Shevchenko
2023-01-12 11:28 ` [PATCH v2 3/5] ASoC: Intel: bytcr_rt5640: " Andy Shevchenko
2023-01-12 11:28 ` [PATCH v2 4/5] ASoC: Intel: bytcr_wm5102: " Andy Shevchenko
2023-01-12 11:28 ` [PATCH v2 5/5] ASoC: Intel: sof_es8336: " Andy Shevchenko
2023-01-12 14:56 ` [PATCH v2 0/5] ASoC: Intel: Balance ACPI device refcount Pierre-Louis Bossart
2023-01-12 18:23 ` Mark Brown

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=20230112112852.67714-1-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox