diff options
author | Harald Welte <laforge@gnumonks.org> | 2019-05-20 12:36:09 +0200 |
---|---|---|
committer | Harald Welte <laforge@gnumonks.org> | 2019-05-21 00:31:11 +0200 |
commit | dde2f1d5cfdc715d5bf91bc19d0b14182731dc99 (patch) | |
tree | 00895cbdbda6bcd5ec5af5c5d13c1ba9bf439cc0 /tests | |
parent | 8294368b2341bfd3f03b2383c2bf1e9a68565ba1 (diff) |
cbch: Refactor get_smscb_block() / remove smscb_msg.next_seg
There's no need to keep around a pointer to the next segment
in a SMSCB message. The way how the multiframe structure is
laid out (and how the tb number works), we can use the result
of a modulo-division on the frame number to determine which
of the segments/blocks inside a SMSCB message (page) we have
to transmit.
This also acts as a simplification in preparation of support
for the SMSCB DEFAULT type.
Change-Id: I48faa19fec4a0852e6112ca2faa98960c678d4c5
Related: OS#4013
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions