All of
 help / color / mirror / Atom feed
From: Mark Brown <>
To: Kuninori Morimoto <>
Cc: Linux-ALSA <>,
	Mark Brown <>
Subject: Re: [PATCH] ASoC: rsnd: adg: clearly handle clock error / NULL case
Date: Fri, 20 Aug 2021 15:39:12 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 20 Aug 2021 13:08:26 +0900, Kuninori Morimoto wrote:
> From: Kuninori Morimoto <>
> This driver is assuming that all adg->clk[i] is not NULL.
> Because of this prerequisites, for_each_rsnd_clk() is possible to work
> for all clk without checking NULL. In other words, all adg->clk[i]
> should not NULL.
> [...]

Applied to for-next


[1/1] ASoC: rsnd: adg: clearly handle clock error / NULL case
      commit: cc64c390b215b404524725a94857d6fb58d9a62a

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.


  reply	other threads:[~2021-08-20 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20  4:08 [PATCH] ASoC: rsnd: adg: clearly handle clock error / NULL case Kuninori Morimoto
2021-08-20 14:39 ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-10 23:23 Kuninori Morimoto
2021-06-11  7:51 ` Dan Carpenter
2021-06-13 22:57   ` Kuninori Morimoto

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.