geoffrey wrote:I would hope there is a good chance that it would be merged, but I am guessing that the ALSA devs would probably like to hear from a few people reporting that it works first (I don't know; I haven't ever done this before).
Good work, thanks a lot!
I'm not an expert on linux kernel development, but I think in general it goes like this, for audio/sound drivers:
- subscribe to alsa-devel mailinglist (if you haven't subscribed already).
- post your patch(es) to alsa-devel mailinglist for review, remember to add your Signed-off-by line. You can use for example "git-send-email" tool to post the patches to the ml.
- wait for other developers to review your patch(es).
- work with the other developers, and address all the requests for changes/improvements, and provide comments if there are any questions.
- re-send new versions of the patch(es) with the fixes/improvements included.
- wait for the patches to get ACK'ed by other developers/maintainers.
- repeat the previous steps as needed
- Once the patches are fully ACKed/reviewed, the alsa/sound maintainer (Takashi Iwai, iirc) will then apply the patch(es) to the patch queue / git tree which will be sent to Linus for inclusion in upstream Linux kernel during the next merge window.