| Message ID | 20220511162403.3987658-1-cezary.rojewski@intel.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | ASoC: Intel: avs: Machine boards and HDA codec support | expand |
On 2022-05-11 6:23 PM, Cezary Rojewski wrote: > This series focuses on populating boards/ subdirectory with supported > configurations by the avs-driver. Note: it is independent of recently > provided "Driver code and PCM operations" series [1], that is, code > found here should not collide with it. Hello, Friendly ping as PCM series got merged but this one looks orphaned :( Patches addressing fls() issues reported by bots have been sent as separate series [1]. [1]: https://lore.kernel.org/lkml/20220525144844.1571705-1-amadeuszx.slawinski@linux.intel.com/ Regards, Czarek
On Thu, May 26, 2022 at 12:14:09PM +0200, Cezary Rojewski wrote: > Friendly ping as PCM series got merged but this one looks orphaned :( > Patches addressing fls() issues reported by bots have been sent as separate > series [1]. Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed. Sending content free pings adds to the mail volume (if they are seen at all) which is often the problem and since they can't be reviewed directly if something has gone wrong you'll have to resend the patches anyway, so sending again is generally a better approach though there are some other maintainers who like them - if in doubt look at how patches for the subsystem are normally handled.
On Wed, 11 May 2022 18:23:49 +0200, Cezary Rojewski wrote: > This series focuses on populating boards/ subdirectory with supported > configurations by the avs-driver. Note: it is independent of recently > provided "Driver code and PCM operations" series [1], that is, code > found here should not collide with it. > > Series starts with a small change that adds a helper to sound pcm > header, allowing for retrieving string naming a direction without the > need of substream pointer. Said helper is used by codec driver code that > follows it but I believe it's generic and helpful enough that it can be > called an independent addition to the sound core. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/14] ALSA: Add snd_pcm_direction_name() helper commit: 90b12a88b710cdc80c00552dfbd589228978bffe [02/14] ASoC: codecs: Add HD-Audio codec driver commit: b5df2a7dca1cc6c66eee0005c92094855dc2028c [03/14] ASoC: Intel: avs: Add HDAudio machine board commit: 97030a43371ea29d65f332d288eb73e8f7bdb3a9 [04/14] ASoC: Intel: avs: Add DMIC machine board commit: 6575e5cae7525b07d0b5fbd7d42323363919a867 [05/14] ASoC: Intel: avs: Add I2S-test machine board commit: e39acc4cfd9250e7b8ec01897570f3009659c3d6 [06/14] ASoC: Intel: avs: Add rt274 machine board commit: e2a4cbf277c4561d01f1aafa3cfafe46bf3feec7 [07/14] ASoC: Intel: avs: Add rt286 machine board commit: 1d395ee2e19b33a1008acfc7af186f2851b63d01 [08/14] ASoC: Intel: avs: Add rt298 machine board commit: 88429ab16df4cd4a1a77d45b90ec95cf62cc22d1 [09/14] ASoC: Intel: avs: Add rt5682 machine board commit: 748102786b3ce0bf402c2dc42386cbfaab71ac39 [10/14] ASoC: Intel: avs: Add nau8825 machine board commit: 32ee40b5590081a6b38a55e4ab16b47085f93afe [11/14] ASoC: Intel: avs: Add ssm4567 machine board commit: 69ea14efe99b533652255b07a9736a9856f50ea5 [12/14] ASoC: Intel: avs: Add max98357a machine board commit: 282c8f8de72f95325225d94caef61f3cc96401da [13/14] ASoC: Intel: avs: Add max98373 machine board commit: 223a0a945821b96f4ccd9940ee975499706e1794 [14/14] ASoC: Intel: avs: Add da7219 machine board commit: 6b5b0d6f36dd45e22f1710e8bcd97f28b4ba41f5 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