tty: cumulate and document tty_struct::flow* membersGroup the flow flags under a single struct called flow. The new structcontains 'stopped' and 'tco_stopped' bools which used to be bits in abitf
tty: cumulate and document tty_struct::flow* membersGroup the flow flags under a single struct called flow. The new structcontains 'stopped' and 'tco_stopped' bools which used to be bits in abitfield. The struct also contains the lock protecting them topotentially share the same cache line.Note that commit c545b66c6922b (tty: Serialize tcflow() with other ttyflow control changes) added a padding to the original bitfield. It wasfor the bitfield to occupy a whole 64b word to avoid interferring storeson Alpha (cannot we evaporate this arch with weird implications to Ccode yet?). But it doesn't work as expected as the padding(tty_struct::unused) is aligned to a 8B boundary too and occupies somebytes from the next word.So make it reliable by:1) setting __aligned of the struct -- that aligns the start, and2) making 'unsigned long unused[0]' as the last member of the struct -- pads the end.This is also the perfect time to start the documentation of tty_structwhere all this lives. So we start by documenting what these boolsactually serve for. And why we do all the alignment dances. Only the fewup-to-date information from the Theodore's comment made it into this newKerneldoc comment.Signed-off-by: Jiri Slaby <[email protected]>Cc: "David S. Miller" <[email protected]>Cc: Jakub Kicinski <[email protected]>Cc: Jonathan Corbet <[email protected]>Cc: Arnd Bergmann <[email protected]>Cc: Ulf Hansson <[email protected]>Cc: Heiko Carstens <[email protected]>Cc: Vasily Gorbik <[email protected]>Cc: Christian Borntraeger <[email protected]>Cc: Shawn Guo <[email protected]>Cc: Sascha Hauer <[email protected]>Cc: Vineet Gupta <[email protected]>Cc: "Maciej W. Rozycki" <[email protected]>Link: https://lore.kernel.org/r/[email protected]Signed-off-by: Greg Kroah-Hartman <[email protected]>
show more ...
tty_port: drop last traces of low_latencyThe main purpose of tty_port::low_latency was removed in commita9c3f68f3cd8 (tty: Fix low_latency BUG) back in 2014. It was left inplace for drivers as an
tty_port: drop last traces of low_latencyThe main purpose of tty_port::low_latency was removed in commita9c3f68f3cd8 (tty: Fix low_latency BUG) back in 2014. It was left inplace for drivers as an optional tune knob. But only one driver has beenusing it until the previous commit. So remove this misconceptcompletely, given there are no users.Signed-off-by: Jiri Slaby <[email protected]>Link: https://lore.kernel.org/r/[email protected]Signed-off-by: Greg Kroah-Hartman <[email protected]>
net: caif: Remove unused caif SPI driverWhile chasing in_interrupt() (ab)use in drivers it turned out that thecaif_spi driver has never been in use since the driver was merged 10 yearsago. There
net: caif: Remove unused caif SPI driverWhile chasing in_interrupt() (ab)use in drivers it turned out that thecaif_spi driver has never been in use since the driver was merged 10 yearsago. There never was any matching code which provides a platform device.The driver has not seen any update (asided of treewide changes andcleanups) since 8 years and the maintainers vanished from the planet.So analysing the potential contexts and the (in)correctness ofin_interrupt() usage is just a pointless exercise.Remove the cruft.Signed-off-by: Thomas Gleixner <[email protected]>Signed-off-by: David S. Miller <[email protected]>
docs: networking: convert caif files to ReSTThere are two text files for caif, plus one already convertedfile.Convert the two remaining ones to ReST, create a new index.rstfile for CAIF, adding
docs: networking: convert caif files to ReSTThere are two text files for caif, plus one already convertedfile.Convert the two remaining ones to ReST, create a new index.rstfile for CAIF, adding it to the main networking documentationindex.Signed-off-by: Mauro Carvalho Chehab <[email protected]>Signed-off-by: David S. Miller <[email protected]>
docs: net: convert two README files to ReST formatThere are two README files there with doesn't have a .txtextension nor are at ReST format.In order to help with the docs conversion to ReST, ren
docs: net: convert two README files to ReST formatThere are two README files there with doesn't have a .txtextension nor are at ReST format.In order to help with the docs conversion to ReST, rename thoseand manually convert them to ReST format.As there are lot more to be done for networking to be part ofthe documentation body, for now mark those two files with:orphan:, in order to supress a build warning.Signed-off-by: Mauro Carvalho Chehab <[email protected]>Signed-off-by: Jonathan Corbet <[email protected]>
Documentation/networking/caif: Update documentationUpdate drawing and remove description of old features.Add HSI and USB link layers to the drawing.Reported-by: Joerg Reisenweber <joerg.reisenwe
Documentation/networking/caif: Update documentationUpdate drawing and remove description of old features.Add HSI and USB link layers to the drawing.Reported-by: Joerg Reisenweber <[email protected]>Signed-off-by: Sjur Brændeland <[email protected]>Signed-off-by: David S. Miller <[email protected]>
Fix common misspellingsFixes generated by 'codespell' and manually reviewed.Signed-off-by: Lucas De Marchi <[email protected]>
tree-wide: fix comment/printk typos"gadget", "through", "command", "maintain", "maintain", "controller", "address","between", "initiali[zs]e", "instead", "function", "select", "already","equal",
tree-wide: fix comment/printk typos"gadget", "through", "command", "maintain", "maintain", "controller", "address","between", "initiali[zs]e", "instead", "function", "select", "already","equal", "access", "management", "hierarchy", "registration", "interest","relative", "memory", "offset", "already",Signed-off-by: Uwe Kleine-König <[email protected]>Signed-off-by: Jiri Kosina <[email protected]>
caif-driver: Add CAIF-SPI Protocol driver.This patch introduces the CAIF SPI Protocol Driver forCAIF Link Layer.This driver implements a platform driver to accommodate for aplatform specific SP
caif-driver: Add CAIF-SPI Protocol driver.This patch introduces the CAIF SPI Protocol Driver forCAIF Link Layer.This driver implements a platform driver to accommodate for aplatform specific SPI device. A general platform driver is notpossible as there are no SPI Slave side Kernel API defined.A sample CAIF SPI Platform device can be found in.../Documentation/networking/caif/spi_porting.txtSigned-off-by: Sjur Braendeland <[email protected]>Signed-off-by: David S. Miller <[email protected]>
net-caif: add CAIF documentationDocumentation of the CAIF Protocol.Signed-off-by: Sjur Braendeland <[email protected]>Signed-off-by: David S. Miller <[email protected]>