Re: [PATCH 2/2] midi streaming substream names from jack names A number of devices have named substreams which are hard to remember / decypher from <device> MIDI n names. Eg. Korg puts a pass through on one substream and iConnectivity devices name the connections.

From: George Harker
Date: Fri Feb 26 2021 - 16:37:44 EST

Next message: Paul Menzel: "Re: [PATCH] iommu/amd: Fix event counter availability check"
Previous message: syzbot: "Re: KASAN: use-after-free Read in __cpuhp_state_remove_instance"
In reply to: George Harker: "[PATCH 2/2] midi streaming substream names from jack names A number of devices have named substreams which are hard to remember / decypher from <device> MIDI n names. Eg. Korg puts a pass through on one substream and iConnectivity devices name the connections."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Thanks for the feedback, addressed in the two patches. I’m not sure why it pulled the body up into the title.I’m sorry about that. I can resubmit if that needs fixing.

George

Next message: Paul Menzel: "Re: [PATCH] iommu/amd: Fix event counter availability check"
Previous message: syzbot: "Re: KASAN: use-after-free Read in __cpuhp_state_remove_instance"
In reply to: George Harker: "[PATCH 2/2] midi streaming substream names from jack names A number of devices have named substreams which are hard to remember / decypher from <device> MIDI n names. Eg. Korg puts a pass through on one substream and iConnectivity devices name the connections."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]