From: Borislav Petkov <bp@alien8.de>
To: Hayes Wang <hayeswang@realtek.com>
Cc: nic_swsd <nic_swsd@realtek.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 3.16-rc6+: r8169 fresh new irq lock inversion
Date: Thu, 24 Jul 2014 11:05:10 +0200 [thread overview]
Message-ID: <20140724090510.GD19239@pd.tnic> (raw)
In-Reply-To: <0835B3720019904CB8F7AA43166CEEB2510016@RTITMBSV03.realtek.com.tw>
On Thu, Jul 24, 2014 at 09:01:27AM +0000, Hayes Wang wrote:
> I have no idea about why you see the messages. I don't think
> the patches which submitted previously for r8169.c would cause
> the problem. Although I have submitted some patches about IPv6,
> the hw checksum should be off by default. That is, the behavior
> should be the same with the previous one.
Yeah, the culprit might be somewhere else, follow this thread:
https://lkml.kernel.org/r/20140723095327.GA23131@pd.tnic
Thanks for taking a look anyway though.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2014-07-24 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 8:18 3.16-rc6+: r8169 fresh new irq lock inversion Borislav Petkov
2014-07-24 9:01 ` Hayes Wang
2014-07-24 9:05 ` Borislav Petkov [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=20140724090510.GD19239@pd.tnic \
--to=bp@alien8.de \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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