summaryrefslogtreecommitdiff
path: root/drivers/pci/controller/dwc
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2023-10-11 10:39:01 +0100
committerDavid S. Miller <davem@davemloft.net>2023-10-11 10:39:01 +0100
commitbbb63db3b0ecb200b33bf172ffb93ef0e4472cee (patch)
treed97b522c17e49a95f1a5abcfccfbf5ef69e7e151 /drivers/pci/controller/dwc
parent5247dbf16cee4e83eb89e4d3b87bd5e79c5d1655 (diff)
parent4688ecb1385f95d3a687286304710723260ad125 (diff)
Merge branch 'skb_segment-testing'
Willem de Bruijn says: ==================== add skb_segment kunit coverage As discussed at netconf last week. Some kernel code is exercised in many different ways. skb_segment is a prime example. This ~350 line function has 49 different patches in git blame with 28 different authors. When making a change, e.g., to fix a bug in one specific use case, it is hard to establish through analysis alone that the change does not break the many other paths through the code. It is impractical to exercise all code paths through regression testing from userspace. Add the minimal infrastructure needed to add KUnit tests to networking, and add code coverage for this function. Patch 1 adds the infra and the first simple test case: a linear skb Patch 2 adds variants with frags[] Patch 3 adds variants with frag_list skbs ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/pci/controller/dwc')
0 files changed, 0 insertions, 0 deletions