netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: antonz@parallels.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] atl1: fix kernel panic in case of DMA errors
Date: Fri, 13 Apr 2012 13:35:59 -0400 (EDT)	[thread overview]
Message-ID: <20120413.133559.1074868352058413273.davem@davemloft.net> (raw)
In-Reply-To: <1334160903-988902-1-git-send-email-antonz@parallels.com>

From: Tony Zelenoff <antonz@parallels.com>
Date: Wed, 11 Apr 2012 20:15:03 +0400

> Problem:
> There was two separate work_struct structures which share one
> handler. Unfortunately getting atl1_adapter structure from
> work_struct in case of DMA error was done from incorrect
> offset which cause kernel panics.
> 
> Solution:
> The useless work_struct for DMA error removed and
> handler name changed to more generic one.
> 
> Signed-off-by: Tony Zelenoff <antonz@parallels.com>

Applied and queued up for -stable, thanks.

      reply	other threads:[~2012-04-13 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 16:15 [PATCH] atl1: fix kernel panic in case of DMA errors Tony Zelenoff
2012-04-13 17:35 ` 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=20120413.133559.1074868352058413273.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=antonz@parallels.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).