public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [RFC/PATCH] dmaengine: ensure dmaengine helpers check valid callback
Date: Tue, 10 Apr 2018 18:20:35 +0100	[thread overview]
Message-ID: <1523380835.2654.192.camel@codethink.co.uk> (raw)
In-Reply-To: <1520527545-4515-1-git-send-email-fabrizio.castro@bp.renesas.com>

On Thu, 2018-03-08 at 16:45 +0000, Fabrizio Castro wrote:
> From: Vinod Koul <vinod.koul@intel.com>
> 
> dmaengine has various device callbacks and exposes helper
> functions to invoke these. These helpers should check if channel,
> device and callback is valid or not before invoking them.
> 
> Reported-by: Jon Hunter <jonathanh@nvidia.com>
> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> (cherry picked from commit 757d12e5849be549076901b0d33c60d5f360269c)
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> Signed-off-by: Jianming Qiao <jianming.qiao@bp.renesas.com>
> ---
> Hello Ben,
> 
> we have stumbled upon a problem, and discovered there was this fix
> upstream we would like to backport.
> 
> Do you think this should go through v4.4 LTS first or are you happy
> to take it?

I can apply it now, but if the bug affects 4.4 LTS or other stable
branches without CIP's extra backports then you should also send it to
stable at vger.kernel.org.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2018-04-10 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 16:45 [cip-dev] [RFC/PATCH] dmaengine: ensure dmaengine helpers check valid callback Fabrizio Castro
2018-04-10 17:20 ` Ben Hutchings [this message]
2018-04-10 17:48   ` Fabrizio Castro

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=1523380835.2654.192.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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