From: David Miller <davem@davemloft.net>
To: sd@queasysnail.net
Cc: netdev@vger.kernel.org, aduyck@mirantis.com
Subject: Re: [PATCH net-next] drivers/net: fixup comments after "Future-proof tunnel offload handlers"
Date: Mon, 11 Jul 2016 13:42:31 -0700 (PDT) [thread overview]
Message-ID: <20160711.134231.1498580109722226744.davem@davemloft.net> (raw)
In-Reply-To: <a1439b9645eec067ebe03a4e2d5228ed78f0e85e.1468235257.git.sd@queasysnail.net>
From: Sabrina Dubroca <sd@queasysnail.net>
Date: Mon, 11 Jul 2016 13:12:28 +0200
> Some comments weren't updated to reflect the renaming of ndo's and the
> change of arguments.
>
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Applied, thanks Sabrina.
prev parent reply other threads:[~2016-07-11 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 11:12 [PATCH net-next] drivers/net: fixup comments after "Future-proof tunnel offload handlers" Sabrina Dubroca
2016-07-11 16:03 ` Alexander Duyck
2016-07-11 20:42 ` David Miller [this message]
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=20160711.134231.1498580109722226744.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aduyck@mirantis.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).