From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, rashmi.narasimhan@oracle.com,
david.stevens@oracle.com
Subject: Re: [PATCH net-next] sunvnet: Initialize network_header and transport_header in vnet_rx_one()
Date: Mon, 18 Jan 2016 17:22:19 -0500 [thread overview]
Message-ID: <20160118222219.GC12034@oracle.com> (raw)
In-Reply-To: <20160118.172022.2052673337766512747.davem@davemloft.net>
On (01/18/16 17:20), David Miller wrote:
> > Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
>
> If this is a bug fix, why are you targetting net-next?
It is a bug fix, but I was not sure if it should go into net or net-next,
so I erred on the side of caution.
--Sowmini
next prev parent reply other threads:[~2016-01-20 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 21:12 [PATCH net-next] sunvnet: Initialize network_header and transport_header in vnet_rx_one() Sowmini Varadhan
2016-01-18 22:20 ` David Miller
2016-01-18 22:22 ` Sowmini Varadhan [this message]
2016-01-19 19:48 ` David Miller
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=20160118222219.GC12034@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=david.stevens@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=rashmi.narasimhan@oracle.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).