[-next,0/4] ASoC: Use DIV_ROUND_UP() instead of open-coding it

Message

Shang XiaoJing Sept. 27, 2022, 2:09 p.m. UTC

Use DIV_ROUND_UP() instead of open-coding it, which intents and makes
it more clear what is going on for the casual reviewer.

Shang XiaoJing (4):
  ASoC: cs35l36: Use DIV_ROUND_UP() instead of open-coding it
  ASoC: wm8978: Use DIV_ROUND_UP() instead of open-coding it
  ASoC: rsnd: Use DIV_ROUND_UP() instead of open-coding it
  ASoC: ti: davinci-mcasp: Use DIV_ROUND_UP() instead of open-coding it

 sound/soc/codecs/cs35l36.c   | 4 ++--
 sound/soc/codecs/wm8978.c    | 2 +-
 sound/soc/sh/rcar/core.c     | 4 ++--
 sound/soc/ti/davinci-mcasp.c | 7 +++----
 4 files changed, 8 insertions(+), 9 deletions(-)

Comments

Mark Brown Oct. 18, 2022, 11:28 a.m. UTC | #1

On Tue, 27 Sep 2022 22:09:44 +0800, Shang XiaoJing wrote:
> Use DIV_ROUND_UP() instead of open-coding it, which intents and makes
> it more clear what is going on for the casual reviewer.
> 
> Shang XiaoJing (4):
>   ASoC: cs35l36: Use DIV_ROUND_UP() instead of open-coding it
>   ASoC: wm8978: Use DIV_ROUND_UP() instead of open-coding it
>   ASoC: rsnd: Use DIV_ROUND_UP() instead of open-coding it
>   ASoC: ti: davinci-mcasp: Use DIV_ROUND_UP() instead of open-coding it
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: cs35l36: Use DIV_ROUND_UP() instead of open-coding it
      commit: ff091dd23b423e19c8191928daedf62eab6ce523
[2/4] ASoC: wm8978: Use DIV_ROUND_UP() instead of open-coding it
      commit: c54402609820427ff6f725f9182216e7cfe7cfa7
[3/4] ASoC: rsnd: Use DIV_ROUND_UP() instead of open-coding it
      commit: 4aa2b05a24a83cc618fab4c4d343f2179962e5ed
[4/4] ASoC: ti: davinci-mcasp: Use DIV_ROUND_UP() instead of open-coding it
      commit: 98059ddfd1ada95fc9f535ea9c08618aa44ad5d3

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