The previous ERTM implementation had a handler for each frame type, and each handler had to figure out what the current state was and handle each frame accordingly. This implementation has a state machine that chooses an execution path first based on the receive or transmit state, then each state has handlers for the frame types. This is easier to match up with the spec, which is defined similarly. Signed-off-by: Mat Martineau <mathewm@xxxxxxxxxxxxxx> --- Refer to https://www.codeaurora.org/gitweb/quic/bluetooth/?p=bluetooth-next.git;a=commit;h=bf897e8a45c3eefbb72e5057b0512f4392bffdba -- Mat Martineau Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
