From: David Miller <davem@davemloft.net>
To: kys@microsoft.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
jasowang@redhat.com, stable@kernel.org
Subject: Re: [PATCH V2 net-next 1/1] hyperv: Properly handle checksum offload
Date: Wed, 30 Apr 2014 13:34:10 -0400 (EDT) [thread overview]
Message-ID: <20140430.133410.981284387859397046.davem@davemloft.net> (raw)
In-Reply-To: <1398873921-20955-1-git-send-email-kys@microsoft.com>
From: "K. Y. Srinivasan" <kys@microsoft.com>
Date: Wed, 30 Apr 2014 09:05:21 -0700
> Do checksum offload only if the client of the driver wants checksum to be
> offloaded.
>
> In V1 version of this patch, I addressed comments from
> Stephen Hemminger <stephen@networkplumber.org> and
> Eric Dumazet <eric.dumazet@gmail.com>.
>
> In this version of the patch I have addressed comments from
> David Miller.
>
> This patch fixes a bug that is exposed in gateway scenarios.
>
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
It does not make any sense to submit a patch for net-next and
also ask for it to be included in -stable.
First of all, -stable submissions are handled by me directly for
networking. Therefore you should not CC: stable on such patches,
instead you ask me politly to include it in my stable submission
queue.
Second of all, if a patch is destined for stable, it should be
submitted for 'net' not 'net-next'.
prev parent reply other threads:[~2014-04-30 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 16:05 K. Y. Srinivasan
2014-04-30 17:34 ` 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=20140430.133410.981284387859397046.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=stable@kernel.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
all inboxes | Powered by JetHome®