From: Florian Westphal <fw@strlen.de>
To: Marco Elver <elver@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, johannes@sipsolutions.net,
akpm@linux-foundation.org, a.nogikh@gmail.com,
edumazet@google.com, andreyknvl@google.com, dvyukov@google.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, idosch@idosch.org, fw@strlen.de,
willemb@google.com
Subject: Re: [PATCH v6 0/3] net, mac80211, kernel: enable KCOV remote coverage collection for 802.11 frame handling
Date: Wed, 25 Nov 2020 17:44:46 +0100 [thread overview]
Message-ID: <20201125164446.GC2730@breakpoint.cc> (raw)
In-Reply-To: <20201125162455.1690502-1-elver@google.com>
Marco Elver <elver@google.com> wrote:
[..]
> v6:
> * Revert usage of skb extensions due to potential memory leak. Patch 2/3 is now
> idential to that in v2.
> * Patches 1/3 and 3/3 are otherwise identical to v5.
The earlier series was already applied to net-next, so you need to
rebase on top of net-next and include a revert of the patch that added
the kcov skb extension.
Also, please indicate the git tree that you want this applied to in the
subject.
next prev parent reply other threads:[~2020-11-25 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 16:24 [PATCH v6 0/3] net, mac80211, kernel: enable KCOV remote coverage collection for 802.11 frame handling Marco Elver
2020-11-25 16:24 ` [PATCH v6 1/3] kernel: make kcov_common_handle consider the current context Marco Elver
2020-11-25 16:24 ` [PATCH v6 2/3] net: store KCOV remote handle in sk_buff Marco Elver
2020-11-25 16:24 ` [PATCH v6 3/3] mac80211: add KCOV remote annotations to incoming frame processing Marco Elver
2020-11-25 16:44 ` Florian Westphal [this message]
2020-11-25 16:45 ` [PATCH v6 0/3] net, mac80211, kernel: enable KCOV remote coverage collection for 802.11 frame handling Jakub Kicinski
2020-11-25 16:50 ` Marco Elver
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=20201125164446.GC2730@breakpoint.cc \
--to=fw@strlen.de \
--cc=a.nogikh@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=idosch@idosch.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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).