From: Vinod <vkoul@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Frank Mori Hess <fmh6jj@gmail.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
r.baldyga@hackerion.com, Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Linux Samsung SOC <linux-samsung-soc@vger.kernel.org>
Subject: Re: Revert "dmaengine: pl330: add DMA_PAUSE feature"
Date: Tue, 29 May 2018 12:39:15 +0530 [thread overview]
Message-ID: <20180529070915.GF5666@vkoul-mobl> (raw)
In-Reply-To: <20180529051745eucas1p2ee6ec3e34f075d255c87f8f54a626784~zBcpaqmAb1928519285eucas1p2H@eucas1p2.samsung.com>
On 29-05-18, 07:17, Marek Szyprowski wrote:
> Hi Vinod,
>
> On 2018-05-18 09:21, Vinod wrote:
> > On 18-05-18, 08:28, Marek Szyprowski wrote:
> >> Hi Vinod,
> >>
> >> Okay, I see that in theory, there are some tricky bits in implementing DMA
> >> support in UART drivers. On the other hand there are already drivers
> >> with seems
> >> to be working fine. This discussion is about revert of the feature
> >> present in
> >> pl330 driver, which is required by other in-kernel driver without proper
> >> fix to
> >> them.
> >>
> >> Can we drop it for now and discuss what and how should be implemented to
> >> make
> >> everyone happy, without any regressions?
> > Sure am dropping the revert, we can always bring it back if it is required
>
> This revert is still in your -next branch. Do you plan to update it as well?
I dont send it to linus and merge topic/* into for-linus and send. It gets
updated on rebase on -rc1.
--
~Vinod
next prev parent reply other threads:[~2018-05-29 7:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 21:50 [PATCH] Revert "dmaengine: pl330: add DMA_PAUSE feature" Frank Mori Hess
2018-05-02 4:32 ` Vinod Koul
2018-05-02 14:37 ` Frank Mori Hess
2018-05-03 9:01 ` Vinod Koul
2018-05-03 16:35 ` Vinod Koul
[not found] ` <CGME20180508090407eucas1p13713284c2d3f5aa5c66f8d136be683c1@eucas1p1.samsung.com>
2018-05-08 9:04 ` Marek Szyprowski
2018-05-08 14:36 ` Frank Mori Hess
2018-05-09 6:59 ` Vinod Koul
2018-05-09 13:19 ` Marek Szyprowski
2018-05-09 17:48 ` Frank Mori Hess
2018-05-10 8:31 ` Marek Szyprowski
2018-05-10 16:04 ` Frank Mori Hess
2018-05-11 12:57 ` Marek Szyprowski
2018-05-11 15:57 ` Frank Mori Hess
2018-05-15 6:21 ` Vinod
2018-05-15 12:24 ` Marek Szyprowski
2018-05-15 13:45 ` Vinod
2018-05-15 15:50 ` Frank Mori Hess
2018-05-17 4:19 ` Vinod Koul
2018-05-17 16:20 ` Frank Mori Hess
2018-05-17 17:22 ` Lars-Peter Clausen
2018-05-18 19:01 ` Frank Mori Hess
2018-05-18 4:03 ` Vinod
2018-05-18 6:28 ` Marek Szyprowski
2018-05-18 7:21 ` Vinod
2018-05-29 5:17 ` Marek Szyprowski
2018-05-29 7:09 ` Vinod [this message]
2018-05-18 18:56 ` Frank Mori Hess
2018-05-21 9:16 ` Vinod Koul
2018-05-22 0:56 ` Frank Mori Hess
2018-05-22 3:37 ` Vinod Koul
2018-05-22 14:27 ` Frank Mori Hess
2018-05-23 5:39 ` Vinod
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=20180529070915.GF5666@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fmh6jj@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=r.baldyga@hackerion.com \
/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).