Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
10_fix-manpage.patch | change default device from cua to ttyS0. (see #182660, #364480)=================================================================== | Joao Eriberto Mota Filho <eriberto@debian.org> | no | 2017-10-05 | ||
20_fix-Makefile.patch | install files in right places and add GCC hardening.=================================================================== | Joao Eriberto Mota Filho <eriberto@debian.org> | no | 2017-10-05 | ||
30_fix-statserial.patch | open device non-blocking.=================================================================== | Brian Bassett <brian@butterfly.ml.org> | no | 1999-06-12 | ||
40_fix-FTCBFS.patch | fix a FTCBFS=================================================================== | Helmut Grohne <helmut@subdivi.de> | no | debian | 2018-11-26 | |
50_fix-n_option.patch | Fix print issue if using -n option Originally, if using -n option, the output of result will be cleaned up as soon as the program exit. |
Aristo Chen <wmchen.aristo@gmail.com> | no | |||
60_buffer_size.patch | buffer size There was this warning from the compiler: . gcc -Wall -O3 -fomit-frame-pointer -c statserial.c statserial.c: In function ‘main’: statserial.c:124:48: warning: ‘%s’ directive writing up to 254 bytes into a region of size 224 [-Wformat-overflow=] sprintf(s, "statserial: can't open device `%s'", device); ^~ ~~~~~~ statserial.c:124:5: note: ‘sprintf’ output between 33 and 287 bytes into a destination of size 255 sprintf(s, "statserial: can't open device `%s'", device); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ . Instead of increasing the size of buffer 's', was chosen to decrease the size device name buffer. Applied-Upstream: Reviewed-by: |
no | 2020-05-17 |