From: Allen Pais <allen.lkml@gmail.com>
To: davem@davemloft.net
Cc: gerrit@erg.abdn.ac.uk, kuba@kernel.org, edumazet@google.com,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
johannes@sipsolutions.net, alex.aring@gmail.com,
stefan@datenfreihafen.org, santosh.shilimkar@oracle.com,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, Allen Pais <apais@linux.microsoft.com>
Subject: [net-next v4 0/8]net: convert tasklets to use new tasklet_setup API
Date: Tue, 3 Nov 2020 14:48:15 +0530 [thread overview]
Message-ID: <20201103091823.586717-1-allen.lkml@gmail.com> (raw)
From: Allen Pais <apais@linux.microsoft.com>
Commit 12cc923f1ccc ("tasklet: Introduce new initialization API")'
introduced a new tasklet initialization API. This series converts
all the net/* drivers to use the new tasklet_setup() API
The following series is based on net-next (9faebeb2d)
v3:
introduce qdisc_from_priv, suggested by Eric Dumazet.
v2:
get rid of QDISC_ALIGN()
v1:
fix kerneldoc
Allen Pais (8):
net: dccp: convert tasklets to use new tasklet_setup() API
net: ipv4: convert tasklets to use new tasklet_setup() API
net: mac80211: convert tasklets to use new tasklet_setup() API
net: mac802154: convert tasklets to use new tasklet_setup() API
net: rds: convert tasklets to use new tasklet_setup() API
net: sched: convert tasklets to use new tasklet_setup() API
net: smc: convert tasklets to use new tasklet_setup() API
net: xfrm: convert tasklets to use new tasklet_setup() API
include/net/pkt_sched.h | 5 +++++
net/dccp/timer.c | 12 ++++++------
net/ipv4/tcp_output.c | 8 +++-----
net/mac80211/ieee80211_i.h | 4 ++--
net/mac80211/main.c | 14 +++++---------
net/mac80211/tx.c | 5 +++--
net/mac80211/util.c | 5 +++--
net/mac802154/main.c | 8 +++-----
net/rds/ib_cm.c | 14 ++++++--------
net/sched/sch_atm.c | 8 ++++----
net/smc/smc_cdc.c | 6 +++---
net/smc/smc_wr.c | 14 ++++++--------
net/xfrm/xfrm_input.c | 7 +++----
13 files changed, 52 insertions(+), 58 deletions(-)
--
2.25.1
next reply other threads:[~2020-11-03 9:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 9:18 Allen Pais [this message]
2020-11-03 9:18 ` [net-next v4 1/8] net: dccp: convert tasklets to use new tasklet_setup() API Allen Pais
2020-11-03 9:18 ` [net-next v4 2/8] net: ipv4: " Allen Pais
2020-11-03 9:18 ` [net-next v4 3/8] net: mac80211: " Allen Pais
2020-11-03 9:18 ` [net-next v4 4/8] net: mac802154: " Allen Pais
2020-11-03 9:18 ` [net-next v4 5/8] net: rds: " Allen Pais
2020-11-06 0:47 ` Jakub Kicinski
2020-11-03 9:18 ` [net-next v4 6/8] net: sched: " Allen Pais
2020-11-03 9:18 ` [net-next v4 7/8] net: smc: " Allen Pais
2020-11-06 0:49 ` Jakub Kicinski
2020-11-06 6:32 ` Karsten Graul
2020-11-03 9:18 ` [net-next v4 8/8] net: xfrm: " Allen Pais
2020-11-06 0:48 ` Jakub Kicinski
2020-11-06 13:25 ` Steffen Klassert
2020-11-07 18:47 ` [net-next v4 0/8]net: convert tasklets to use new tasklet_setup API Jakub Kicinski
2020-11-09 6:38 ` Allen Pais
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201103091823.586717-1-allen.lkml@gmail.com \
--to=allen.lkml@gmail.com \
--cc=alex.aring@gmail.com \
--cc=apais@linux.microsoft.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerrit@erg.abdn.ac.uk \
--cc=herbert@gondor.apana.org.au \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=stefan@datenfreihafen.org \
--cc=steffen.klassert@secunet.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).