From: Neil Horman <nhorman@tuxdriver.com>
To: mroos@linux.ee
Cc: David Miller <davem@davemloft.net>,
steffen@klassert.de, netdev@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: bisected regression: 3c59x corrupts packets in 3.17-rc5
Date: Wed, 17 Sep 2014 08:56:40 -0400 [thread overview]
Message-ID: <20140917125640.GA4213@localhost.localdomain> (raw)
In-Reply-To: <alpine.LRH.2.11.1409171529350.26961@adalberg.ut.ee>
On Wed, Sep 17, 2014 at 03:43:54PM +0300, mroos@linux.ee wrote:
> > Shit, you're right, sorry about that. Its odd, I'm running it here, and its not
> > causing problems, but thats obviously wrong. Meelis, please add the above fix
> > to your test and confirm that it sovles the problem. If you could keep the
> > previous patch in place too that would be great, as we should probably add the
> > dma error checking anyway.
> >
> >
> > [PATCH] 3c59x: Fix bad offset spec in skb_frag_dma_map
>
> Tested 2 variants: only this patch (backported to old state) and both
> patches together.
>
> Both work fine.
>
Thank you, Meelis. Dave, I'll propose these patches officially in just a bit
sorry for the
> --
> Meelis Roos (mroos@linux.ee)
>
next prev parent reply other threads:[~2014-09-17 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 23:14 bisected regression: 3c59x corrupts packets in 3.17-rc5 Meelis Roos
2014-09-16 10:17 ` Neil Horman
2014-09-16 10:32 ` Meelis Roos
2014-09-16 14:31 ` Neil Horman
2014-09-16 14:32 ` [RFC PATCH] 3c59x: Add dma error checking and recovery Neil Horman
2014-09-16 20:29 ` bisected regression: 3c59x corrupts packets in 3.17-rc5 David Miller
2014-09-17 10:27 ` Neil Horman
2014-09-17 12:43 ` mroos
2014-09-17 12:56 ` Neil Horman [this message]
2014-09-17 13:04 ` [PATCH 1/2] 3c59x: Add dma error checking and recovery Neil Horman
2014-09-17 13:04 ` [PATCH 2/2] 3c59x: Fix bad offset spec in skb_frag_dma_map Neil Horman
2014-09-19 20:29 ` David Miller
2014-09-19 20:29 ` [PATCH 1/2] 3c59x: Add dma error checking and recovery David Miller
2014-09-20 1:19 ` Neil Horman
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=20140917125640.GA4213@localhost.localdomain \
--to=nhorman@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=netdev@vger.kernel.org \
--cc=steffen@klassert.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.