From: Alexander Lobakin <alobakin@dlink.ru>
To: David Miller <davem@davemloft.net>
Cc: ecree@solarflare.com, jiri@mellanox.com, edumazet@google.com,
idosch@mellanox.com, pabeni@redhat.com, petrm@mellanox.com,
sd@queasysnail.net, f.fainelli@gmail.com,
jaswinder.singh@linaro.org, manishc@marvell.com,
GR-Linux-NIC-Dev@marvell.com, johannes.berg@intel.com,
emmanuel.grumbach@intel.com, luciano.coelho@intel.com,
linuxwifi@intel.com, kvalo@codeaurora.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: core: allow fast GRO for skbs with Ethernet header in head
Date: Fri, 15 Nov 2019 10:52:59 +0300 [thread overview]
Message-ID: <4cff3016dcc4fc63e23d5c0de6f81bd8@dlink.ru> (raw)
In-Reply-To: <20191114.234958.1198680245198023054.davem@davemloft.net>
David Miller wrote 15.11.2019 10:49:
> From: Alexander Lobakin <alobakin@dlink.ru>
> Date: Fri, 15 Nov 2019 10:36:08 +0300
>
>> Please let me know if I must send v2 of this patch with corrected
>> description before getting any further reviews.
>
> I would say that you do, thanks for asking.
>
> The more details and information in the commit message, the better.
Thank you, I'll publish v2 soon to clarify all the possible
misunderstandings.
Regards,
ᚷ ᛖ ᚢ ᚦ ᚠ ᚱ
prev parent reply other threads:[~2019-11-15 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 12:28 [PATCH net-next] net: core: allow fast GRO for skbs with Ethernet header in head Alexander Lobakin
2019-11-15 1:25 ` David Miller
2019-11-15 7:36 ` Alexander Lobakin
2019-11-15 7:49 ` David Miller
2019-11-15 7:52 ` Alexander Lobakin [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=4cff3016dcc4fc63e23d5c0de6f81bd8@dlink.ru \
--to=alobakin@dlink.ru \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=edumazet@google.com \
--cc=emmanuel.grumbach@intel.com \
--cc=f.fainelli@gmail.com \
--cc=idosch@mellanox.com \
--cc=jaswinder.singh@linaro.org \
--cc=jiri@mellanox.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@mellanox.com \
--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).