user/sven/linux.git/include/net/llc_s_ev.h, branch v5.8

llc*.h: Remove extern from function prototypes

2013-09-21T18:01:38Z

There are a mix of function prototypes with and without extern in the kernel sources. Standardize on not using extern for function prototypes. Function prototypes don't need to be written with extern. extern is assumed by the compiler. Its use is as unnecessary as using auto to declare automatic/local variables in a block. Signed-off-by: Joe Perches Signed-off-by: David S. Miller

[LLC] clean up the ui sending routines and core

2002-09-24T02:19:47Z

OK, now I managed to kill the last remnants of bloated structs from LLC, I feel better now :) Also deleted include/net/llc_{frame,name,state}.h, remnants of the old LLC stack still in the tree.

[LLC] kill sap->{ind,conf}, finally!

2002-09-24T00:04:25Z

With this one the sap->ind and ->conf callbacks are gone, now the core is tightly integrated with the socket layer (PF_LLC) and the datalink_protos are mostly working like when the old LLC stack was in the kernel, i.e. without special receiving routines for IPX in 802.2 mode, now I have to work on the UI sending routines to kill more stupid structs.

[LLC] move reason to the {station,sap,conn}_ev structs

2002-09-22T21:30:06Z

Slowly killing the ugly struct forest.

[LLC] remove all tmr ev structs & fix psnap and p8022 wrt ui sending

2002-09-14T01:25:14Z

. No need for the timer_running member on llc_timer, we only need it in one place, and timer_pending is equivalent. One more procom OS generalisation killed. . Move the skb->protocol assignment in llc_build_and_send_pkt routines and llc_ui_send_data to the caller, this is the common practice in Linux networking code (think netif_rx) and required to keep the request functions in psnap and p8022 simple. . Remove the rpt_status (report status) ev members, not used at all, not even in the original procom code. . Convert psnap and p8022 request functions to use llc_ui_build_and_send_ui_pkt, removing all the prim cruft.

LLC: use skb->cb to store the LLC events

2002-08-14T18:13:00Z

. this allows us to kill the shorlived kmalloc/kfree for events in the fast path. . because of this there is no need for the skb member in the event structs . use more labeled elements in the transition tables . simplify llc_sock proc routine . more kernedoc style comments . . remove unused defines in llc_main.h . create llc_set_backlog_type and llc_backlog_type .

net/llc/*.c

2002-05-30T21:36:32Z

Forward port of LLC from 2.4 to 2.5. This is the forward port of the LLC stack released by Procom Inc. for Linux 2.0.30, I have heavily modified it to make it similar to other Linux network stacks, using of struct sk_buff to represent in-transit packets and doing massive code cleanups. Jay Schullist contributed support for BSD Sockets, as the original code had only a simple in kernel API for use by upper layer protocols, such as the NetBEUI stack also provided by Procom for 2.0.30. This code is basically what I had previously submitted to Alan Cox for his 2.4-ac series and that is even shipped in source form, in the Red Hat 7.3 kernel package, plus cleanups wrt standard syntax for labeled elements and further use of this C construct to make the code more resilient to editing mistakes, using the compiler to further check the source code. TODO: Make it completely SMP safe, as the reports of successful usage up to now and the testing is done on UP. Completely remove the old LLC code in the kernel, that is still there for things like Appletalk, IPX, etc to use, also check that all these protocols work correctly with this new LLC stack. This code is already being used in the linux-sna project and Jay Schullist has been developing support for things like DLSw and other protocols that works on top of 802.2. I'll be releasing patches with the NetBEUI stack and updated samba-2.0.6 patches for use with NetBEUI and this LLC stack in the future. But the NetBEUI code is available already in my kernel.org ftp area at: ftp://ftp.kernel.org/pub/linux/kernel/people/acme. Please report problems to me or the linux-sna mailing list, instructions on how to subscribe are available at http://www.linux-sna.org website.