From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Viresh Kumar <vireshk@kernel.org>,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Mark Brown <broonie@kernel.org>,
Vineet Gupta <vgupta@synopsys.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v7 0/4] Fixes / cleanups in dw_dmac (affects on few subsystems)
Date: Tue, 03 May 2016 16:12:35 +0300 [thread overview]
Message-ID: <1462281155.17131.216.camel@linux.intel.com> (raw)
In-Reply-To: <20160502100133.GI2274@localhost>
On Mon, 2016-05-02 at 15:31 +0530, Vinod Koul wrote:
> On Wed, Apr 27, 2016 at 02:15:36PM +0300, Andy Shevchenko wrote:
> >
> > This patch series (v3: http://www.spinics.net/lists/kernel/msg221530
> > 3.html)
> > contains a number of mostly minor fixes and cleanups for the DW DMA
> > driver. A
> > couple of them affect the DT binding so these may need to be updated
> > to
> > maintain compatibility (old format is still supported though). The
> > rest should
> > be relatively straight-forward.
> Applied, thanks
Thanks!
What is the name of immutable branch / tag the other maintainers can
use? (I'm talking mostly about sata_dwc_460ex series)
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2016-05-03 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 11:15 [PATCH v7 0/4] Fixes / cleanups in dw_dmac (affects on few subsystems) Andy Shevchenko
2016-04-27 11:15 ` [PATCH v7 1/4] dmaengine: dw: platform: check nr_masters to be non-zero Andy Shevchenko
2016-04-27 11:15 ` [PATCH v7 2/4] dmaengine: dw: revisit data_width property Andy Shevchenko
2016-04-27 11:15 ` [PATCH v7 3/4] dmaengine: dw: keep entire platform data in struct dw_dma Andy Shevchenko
2016-04-27 11:15 ` [PATCH v7 4/4] dmaengine: dw: pass platform data via struct dw_dma_chip Andy Shevchenko
2016-04-27 11:17 ` [PATCH v7 0/4] Fixes / cleanups in dw_dmac (affects on few subsystems) Viresh Kumar
2016-05-02 10:01 ` Vinod Koul
2016-05-03 13:12 ` Andy Shevchenko [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=1462281155.17131.216.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tj@kernel.org \
--cc=vgupta@synopsys.com \
--cc=vinod.koul@intel.com \
--cc=vireshk@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 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.