[v2,0/4] ASoC: rt5677: Refactor GPIO and use device_get_match_data()

Message

Andy Shevchenko June 30, 2023, 5:21 p.m. UTC

The code can be simplified with refactored GPIO parts and with use of
device_get_match_data(). Besides that couple of additional changes,
one for maintenance and one for making IRQ domain agnostic (not being
pinned to OF).

Changelog v2:
- refactored GPIO code in (a new) patch 1
- fixed compilation error in patch 2 (LKP)

Andy Shevchenko (4):
  ASoC: rt5677: Refactor GPIO support code
  ASoC: rt5677: Use agnostic irq_domain_create_linear()
  ASoC: rt5677: Use device_get_match_data()
  ASoC: rt5677: Sort headers alphabetically

 sound/soc/codecs/rt5677.c | 117 +++++++++++++-------------------------
 sound/soc/codecs/rt5677.h |  92 +++++-------------------------
 2 files changed, 53 insertions(+), 156 deletions(-)

Comments

Mark Brown July 12, 2023, 11:47 a.m. UTC | #1

On Fri, 30 Jun 2023 20:21:51 +0300, Andy Shevchenko wrote:
> The code can be simplified with refactored GPIO parts and with use of
> device_get_match_data(). Besides that couple of additional changes,
> one for maintenance and one for making IRQ domain agnostic (not being
> pinned to OF).
> 
> Changelog v2:
> - refactored GPIO code in (a new) patch 1
> - fixed compilation error in patch 2 (LKP)
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: rt5677: Refactor GPIO support code
      commit: 5512ffd9f39832f312b7f903703ac39d6367fe8a
[2/4] ASoC: rt5677: Use agnostic irq_domain_create_linear()
      commit: c3d42d7baf6b4032171270e3df001fb946493452
[3/4] ASoC: rt5677: Use device_get_match_data()
      commit: 043bb9c012ee7d092a477159cc66dbdf62fd2666
[4/4] ASoC: rt5677: Sort headers alphabetically
      commit: ea1c1019a88d88cf0a7d6892f594b72ddb3b8c0b

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

Andy Shevchenko July 12, 2023, 1:56 p.m. UTC | #2

On Wed, Jul 12, 2023 at 12:47:06PM +0100, Mark Brown wrote:
> On Fri, 30 Jun 2023 20:21:51 +0300, Andy Shevchenko wrote:
> > The code can be simplified with refactored GPIO parts and with use of
> > device_get_match_data(). Besides that couple of additional changes,
> > one for maintenance and one for making IRQ domain agnostic (not being
> > pinned to OF).

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

JFYI: You might need to amend your scripts (?) as in the merge commit
      the Subject is cut (I believe that your scripts doesn't handle
      RFC2822 long lines in the email headers).

Mark Brown July 12, 2023, 3:23 p.m. UTC | #3

On Wed, Jul 12, 2023 at 04:56:51PM +0300, Andy Shevchenko wrote:

> JFYI: You might need to amend your scripts (?) as in the merge commit
>       the Subject is cut (I believe that your scripts doesn't handle
>       RFC2822 long lines in the email headers).

Report that to Konstantin, this is just b4.

Andy Shevchenko July 12, 2023, 3:31 p.m. UTC | #4

+Cc: Konstantin.

Konstantin, seems b4 doesn't handle long Subject lines for merge commits
(PR mode).

On Wed, Jul 12, 2023 at 04:23:11PM +0100, Mark Brown wrote:
> On Wed, Jul 12, 2023 at 04:56:51PM +0300, Andy Shevchenko wrote:
> 
> > JFYI: You might need to amend your scripts (?) as in the merge commit
> >       the Subject is cut (I believe that your scripts doesn't handle
> >       RFC2822 long lines in the email headers).
> 
> Report that to Konstantin, this is just b4.