linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Renesas R-Car DMAC fixes
Date: Fri, 13 Feb 2015 08:39:13 +0000	[thread overview]
Message-ID: <20150213082712.GO21387@intel.com> (raw)
In-Reply-To: <1422576013-7846-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

On Fri, Feb 13, 2015 at 04:51:01AM +0200, Laurent Pinchart wrote:
> Hi Vinod,
> 
> On Thursday 12 February 2015 14:59:36 Vinod Koul wrote:
> > On Fri, Jan 30, 2015 at 02:00:07AM +0200, Laurent Pinchart wrote:
> > > Hello,
> > > 
> > > Here are a couple of fixes for the rcar-dmac driver. They're based on the
> > > next branch of the dmaengine tree.
> > > 
> > > The first four patches fix driver bugs, while the last two work around two
> > > hardware issues. Patch 5 works around a documented errata, while patch 6
> > > handles a data corruption issue that was noticed during test but not yet
> > > confirmed to be a hardware bug by Renesas. When more information about the
> > > issue will be available a better fix could possibly be developed.
> > > 
> > > The patches are available at
> > > 
> > > 	git://linuxtv.org/pinchartl/fbdev.git dma/upstream
> > > 
> > > Vinod, is there still time for a v3.20 pull request ?
> > 
> > Since this is fixes I was trying to merge them before I send to Linus in
> > next few days, but this fails to apply for me :(
> > 
> > I have merged everything into my for-linus which will be sent to him. Or you
> > can send later and we can get this into fixes
> 
> I've rebased my branch on your for-linus branch and pushed the result to
> 
> 	git://linuxtv.org/pinchartl/fbdev.git dma/upstream
Since I had to modify my branch, i ended up cherrypicking. So all these are
in my queue now.

Thanks

-- 
~Vinod


      parent reply	other threads:[~2015-02-13  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 23:59 [PATCH v2 0/6] Renesas R-Car DMAC fixes Laurent Pinchart
2015-02-12  9:41 ` Vinod Koul
2015-02-13  2:51 ` Laurent Pinchart
2015-02-13  8:39 ` Vinod Koul [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=20150213082712.GO21387@intel.com \
    --to=vinod.koul@intel.com \
    --cc=linux-sh@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).