mbox series

[0/2] ASoC: Intel: atom: fix kernel-doc and W=1 warnings

Message ID 20200701183716.83314-1-pierre-louis.bossart@linux.intel.com (mailing list archive)
Headers show
Series ASoC: Intel: atom: fix kernel-doc and W=1 warnings | expand

Message

Pierre-Louis Bossart July 1, 2020, 6:37 p.m. UTC
Yet another series to fix broken kernel-doc and mark unused variables
as such.

Pierre-Louis Bossart (2):
  ASoC: Intel: atom: fix kernel-doc
  ASoC: Intel: atom: fix 'defined but not used' warning

 sound/soc/intel/atom/sst-atom-controls.c | 65 ++++++++++++++++--------
 sound/soc/intel/atom/sst/sst_loader.c    |  4 ++
 sound/soc/intel/atom/sst/sst_stream.c    | 43 +++++++++-------
 3 files changed, 74 insertions(+), 38 deletions(-)


base-commit: a2b782d59c57cb6f673dbb4804ffc500336d7a54

Comments

Mark Brown July 1, 2020, 10:23 p.m. UTC | #1
On Wed, 1 Jul 2020 13:37:14 -0500, Pierre-Louis Bossart wrote:
> Yet another series to fix broken kernel-doc and mark unused variables
> as such.
> 
> Pierre-Louis Bossart (2):
>   ASoC: Intel: atom: fix kernel-doc
>   ASoC: Intel: atom: fix 'defined but not used' warning
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: Intel: atom: fix kernel-doc
      commit: 11013884025044374ee6222408f67ec518831353
[2/2] ASoC: Intel: atom: fix 'defined but not used' warning
      commit: 544079abf603bf7823453748285b7cc048b09a9f

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.

Thanks,
Mark