From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: "i.mazanov@gmail.com" <i.mazanov@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Latest l-o and usb gadget + NFS root problems
Date: Mon, 30 Mar 2009 14:44:34 +0300 [thread overview]
Message-ID: <20090330144434.27f8a30a.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <gqptap$jje$1@ger.gmane.org>
On Mon, 30 Mar 2009 08:47:20 +0200
ext Igor Mazanov <i.mazanov@gmail.com> wrote:
> I got stuck in same problem last week. A reason was napi related
> changes in net/core/dev.c. There is a discussion and workaround too
> in LKML,
>
> Revert "gro: Fix legacy path napi_complete crash", (was: Re: Linux
>
> http://marc.info/?t=123789988400005&r=1&w=2
>
Thanks! Seems to help, much more reliable now :-)
Jarkko
prev parent reply other threads:[~2009-03-30 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 9:40 Latest l-o and usb gadget + NFS root problems Tomi Valkeinen
2009-03-27 10:38 ` Koen Kooi
2009-03-27 11:07 ` Tomi Valkeinen
2009-03-28 14:06 ` Jarkko Nikula
2009-03-30 6:47 ` Igor Mazanov
2009-03-30 11:44 ` Jarkko Nikula [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=20090330144434.27f8a30a.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=i.mazanov@gmail.com \
--cc=linux-omap@vger.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