Already checked in ethdev now.
Signed-off-by: Stephen Hemminger
---
drivers/net/dpaa2/dpaa2_ethdev.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/net/dpaa2/dpaa2_ethdev.c b/drivers/net/dpaa2/dpaa2_ethdev.c
index a9bce854c3..8624bba0ce 100644
--- a/drivers/net/dpaa2/
Already checked in ethdev now.
Signed-off-by: Stephen Hemminger
---
drivers/net/enetfec/enet_ethdev.c | 16 ++--
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git a/drivers/net/enetfec/enet_ethdev.c
b/drivers/net/enetfec/enet_ethdev.c
index 91c0f60490..9835532595 100644
-
Already checked in ethdev now.
Signed-off-by: Stephen Hemminger
---
drivers/net/virtio/virtio_rxtx.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/net/virtio/virtio_rxtx.c b/drivers/net/virtio/virtio_rxtx.c
index b67f063b31..6ae3a6eb12 100644
--- a/drivers/net/virtio/vir
Recent zxdh driver review raised the question of why should
drivers have to check rx_conf for deferred start support.
This can be better handled across all drivers at ethdev level.
v2 - annotate now unused conf pointer in enetfec
Stephen Hemminger (5):
ethdev: check that device supports deferre
This check is now done in ethdev layer.
Signed-off-by: Stephen Hemminger
---
drivers/net/dpaa/dpaa_ethdev.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/net/dpaa/dpaa_ethdev.c b/drivers/net/dpaa/dpaa_ethdev.c
index e8d34e5898..ce48f0 100644
--- a/drivers/net/dpaa/dp
The check for supporting deferred start should be handled at
the ethdev level for all devices.
Signed-off-by: Stephen Hemminger
---
lib/ethdev/rte_ethdev.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
index 6413c54e3b..7768058f
* follow up of a discussion with Robin Jarry
* since 3.12 invalid escape sequences generate SyntaxWarning
* in the future, these invalid sequences will generate SyntaxError
* therefore changed syntax to raw string notation.
Link: https://inbox.dpdk.org/dev/d6amqxrsg8e7.33baorrhrh...@redhat.com/
Li
* follow up of a discussion with Robin Jarry
* since 3.12 invalid escape sequences generate SyntaxWarning
* in the future, these invalid sequences will generate SyntaxError
* therefore changed syntax to raw string notation.
Link: https://inbox.dpdk.org/dev/d6amqxrsg8e7.33baorrhrh...@redhat.com/
Li
Hello,
This series clears out Python syntax warnings; it follows from a discussion with
Robin Jarry. Being one-liners, they are backported to stable.
Below are all occurences of the re module in the code base. Where it was due,
the string have been escaped.
Thank you,
```
$ git grep -Pn '[^\w_]
9 matches
Mail list logo