From: David Miller <davem@davemloft.net>
To: ajitk@serverengines.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] be2net: Workaround to fix a bug in Rx Completion processing.
Date: Wed, 30 Sep 2009 16:37:27 -0700 (PDT) [thread overview]
Message-ID: <20090930.163727.180617737.davem@davemloft.net> (raw)
In-Reply-To: <20090930090656.GA5215@serverengines.com>
From: Ajit Khaparde <ajitk@serverengines.com>
Date: Wed, 30 Sep 2009 14:37:06 +0530
> vtp bit in RX completion descriptor could be wrongly set in
> some skews of BladEngine. Ignore this bit if vtm is not set.
> This patch is against the net-next-2.6 tree.
>
> Signed-off-by: Ajit Khaparde <ajitk@serverengines.com>
This doesn't apply.
Until I start taking new feature patches, net-next-2.6 is just
going to be a stale GIT tree based upon Linus's tree at some
point in time long ago.
net-2.6 is far in front of that, and actually since this is a bug
fix you really should be sending me this patch against that.
prev parent reply other threads:[~2009-09-30 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 9:07 [PATCH net-next-2.6] be2net: Workaround to fix a bug in Rx Completion processing Ajit Khaparde
2009-09-30 23:37 ` 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=20090930.163727.180617737.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajitk@serverengines.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).