From: dan.j.williams@intel.com (Dan Williams)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] async-tx: fix buffer sumbission error handling in ipu_idma.c
Date: Wed, 10 Feb 2010 08:54:26 -0700 [thread overview]
Message-ID: <e9c3a7c21002100754k7737b79cvb13a2b39ad16cc44@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1002101643390.4495@axis700.grange>
On Wed, Feb 10, 2010 at 8:44 AM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> If submitting new buffer failed, a wrong descriptor gets completed and it
> doesn't check, if a callback is at all defined, which can lead to an Oops. Fix
> these bugs and make ipu_update_channel_buffer() void, because it never fails.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Looks like 2.6.33 material. Shall I tag it for -stable as well?
--
Dan
next prev parent reply other threads:[~2010-02-10 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 15:44 [PATCH] async-tx: fix buffer sumbission error handling in ipu_idma.c Guennadi Liakhovetski
2010-02-10 15:54 ` Dan Williams [this message]
2010-02-10 16:32 ` [PATCH v2] " Guennadi Liakhovetski
2010-02-10 17:47 ` Dan Williams
2010-02-10 18:04 ` Uwe Kleine-König
2010-02-10 20:11 ` Guennadi Liakhovetski
2010-02-10 20:37 ` Dan Williams
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=e9c3a7c21002100754k7737b79cvb13a2b39ad16cc44@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).