[-next,0/2] allow modules autoloading

Message

Hongbo Li Aug. 21, 2024, 6:19 a.m. UTC

Add macro MODULE_DEVICE_TABLE, so modules could be properly
autoloaded based on the alias from of_device_id table.

Hongbo Li (2):
  sound/soc: allow module autoloading for table db1200_pids
  sound/soc: allow module autoloading for table board_ids

 sound/soc/amd/acp/acp-sof-mach.c | 2 ++
 sound/soc/au1x/db1200.c          | 1 +
 2 files changed, 3 insertions(+)

Comments

Mark Brown Aug. 21, 2024, 1:29 p.m. UTC | #1

On Wed, Aug 21, 2024 at 02:19:53PM +0800, Hongbo Li wrote:
> Add macro MODULE_DEVICE_TABLE, so modules could be properly
> autoloaded based on the alias from of_device_id table.

Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.

As documented in submitting-patches.rst please send patches to the 
maintainers for the code you would like to change.  The normal kernel
workflow is that people apply patches from their inboxes, if they aren't
copied they are likely to not see the patch at all and it is much more
difficult to apply patches.

Mark Brown Aug. 21, 2024, 6:42 p.m. UTC | #2

On Wed, 21 Aug 2024 14:19:53 +0800, Hongbo Li wrote:
> Add macro MODULE_DEVICE_TABLE, so modules could be properly
> autoloaded based on the alias from of_device_id table.
> 
> Hongbo Li (2):
>   sound/soc: allow module autoloading for table db1200_pids
>   sound/soc: allow module autoloading for table board_ids
> 
> [...]

Applied to

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

Thanks!

[1/2] sound/soc: allow module autoloading for table db1200_pids
      commit: 0e9fdab1e8df490354562187cdbb8dec643eae2c
[2/2] sound/soc: allow module autoloading for table board_ids
      commit: 5f7c98b7519a3a847d9182bd99d57ea250032ca1

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

Hongbo Li Aug. 22, 2024, 2:14 a.m. UTC | #3

On 2024/8/21 21:29, Mark Brown wrote:
> On Wed, Aug 21, 2024 at 02:19:53PM +0800, Hongbo Li wrote:
>> Add macro MODULE_DEVICE_TABLE, so modules could be properly
>> autoloaded based on the alias from of_device_id table.
> 
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
> 
> As documented in submitting-patches.rst please send patches to the
> maintainers for the code you would like to change.  The normal kernel
> workflow is that people apply patches from their inboxes, if they aren't
> copied they are likely to not see the patch at all and it is much more
> difficult to apply patches.

Thank you, I'll notice this in later patches.

Thanks,
Hongbo