From: Greg KH <greg@kroah.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
"'gregkh@suse.de'" <gregkh@suse.de>,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH 1/1] staging: hv: Fix missing functions for net_device_ops (resubmit)
Date: Mon, 2 Aug 2010 18:30:14 -0700 [thread overview]
Message-ID: <20100803013013.GC3814@kroah.com> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF7280E8556B@TK5EX14MBXC121.redmond.corp.microsoft.com>
On Mon, Aug 02, 2010 at 05:46:01PM +0000, Haiyang Zhang wrote:
> From: Haiyang Zhang <haiyangz@microsoft.com>
>
> Subject: staging: hv: Fix missing functions for net_device_ops
> Unlike in older kernels, ether_setup() no longer sets default
Why put the subject in the body of the email? This forces me to edit it
again :(
> functions. We need to put them into net_device_ops. For example,
> eth_change_mtu prevents setting MTU beyond 1500. This is necessary
> because we don't support jumbo frame at this time.
What does this mean? Is it a bug? Just not going as fast as possible?
Something else?
> It affects kernel 2.6.32 and later, which are all versions
> containing Hyper-V drivers.
So is this fixing a bug that needs to be backported to these older
kernels (i.e. the staging tree?) Is this something that is causing
people problems?
Third time's a charm?
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-03 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 17:46 [PATCH 1/1] staging: hv: Fix missing functions for net_device_ops (resubmit) Haiyang Zhang
2010-08-03 1:30 ` Greg KH [this message]
2010-08-03 18:21 ` Haiyang Zhang
2010-08-03 18:43 ` Greg KH
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=20100803013013.GC3814@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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