From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Long Cheng <long.cheng@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
Jiri Slaby <jslaby@suse.com>, Sean Wang <sean.wang@mediatek.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, srv_heupstream@mediatek.com,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
YT Shen <yt.shen@mediatek.com>
Subject: Re: [PATCH v2 0/4] add uart DMA function
Date: Wed, 5 Dec 2018 19:50:42 +0100 [thread overview]
Message-ID: <20181205185042.GA27295@kroah.com> (raw)
In-Reply-To: <20181205163133.GQ2847@vkoul-mobl>
On Wed, Dec 05, 2018 at 10:01:33PM +0530, Vinod Koul wrote:
> Hi Greg,
>
> On 05-12-18, 11:03, Greg Kroah-Hartman wrote:
> > On Wed, Dec 05, 2018 at 04:42:56PM +0800, Long Cheng wrote:
> > > In Mediatek SOCs, the uart can support DMA function.
> > > Base on DMA engine formwork, we add the DMA code to support uart. And put the code under drivers/dma.
> > >
> > > This series contains document bindings, Kconfig to control the function enable or not,
> > > device tree including interrupt and dma device node, the code of UART DM
> >
> > I've queued up patches 1 and 3 from this series in my tty tree, thanks.
>
> Do you mind not taking patch 2, I would like that to go thru dmaengine
> tree
Like I said, I only took patches 1 and 3...
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, YT Shen <yt.shen@mediatek.com>,
srv_heupstream@mediatek.com, Sean Wang <sean.wang@mediatek.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
dmaengine@vger.kernel.org, Long Cheng <long.cheng@mediatek.com>,
linux-mediatek@lists.infradead.org, linux-serial@vger.kernel.org,
Jiri Slaby <jslaby@suse.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] add uart DMA function
Date: Wed, 5 Dec 2018 19:50:42 +0100 [thread overview]
Message-ID: <20181205185042.GA27295@kroah.com> (raw)
In-Reply-To: <20181205163133.GQ2847@vkoul-mobl>
On Wed, Dec 05, 2018 at 10:01:33PM +0530, Vinod Koul wrote:
> Hi Greg,
>
> On 05-12-18, 11:03, Greg Kroah-Hartman wrote:
> > On Wed, Dec 05, 2018 at 04:42:56PM +0800, Long Cheng wrote:
> > > In Mediatek SOCs, the uart can support DMA function.
> > > Base on DMA engine formwork, we add the DMA code to support uart. And put the code under drivers/dma.
> > >
> > > This series contains document bindings, Kconfig to control the function enable or not,
> > > device tree including interrupt and dma device node, the code of UART DM
> >
> > I've queued up patches 1 and 3 from this series in my tty tree, thanks.
>
> Do you mind not taking patch 2, I would like that to go thru dmaengine
> tree
Like I said, I only took patches 1 and 3...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-05 18:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 8:42 [PATCH v2 0/4] add uart DMA function Long Cheng
2018-12-05 8:42 ` Long Cheng
2018-12-05 10:03 ` Greg Kroah-Hartman
2018-12-05 10:03 ` Greg Kroah-Hartman
2018-12-05 16:31 ` Vinod Koul
2018-12-05 16:31 ` Vinod Koul
2018-12-05 18:50 ` Greg Kroah-Hartman [this message]
2018-12-05 18:50 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2018-12-05 8:42 [v2,1/4] dt-bindings: dma: uart: add uart dma bindings Long Cheng
2018-12-05 8:42 ` [PATCH v2 1/4] " Long Cheng
2018-12-05 8:42 ` Long Cheng
2018-12-05 8:42 [v2,2/4] dmaengine: mtk_uart_dma: add Mediatek uart DMA support Long Cheng
2018-12-05 8:42 ` [PATCH v2 2/4] " Long Cheng
2018-12-05 8:42 ` Long Cheng
2018-12-05 8:42 [v2,3/4] serial: 8250-mtk: add " Long Cheng
2018-12-05 8:42 ` [PATCH v2 3/4] " Long Cheng
2018-12-05 8:42 ` Long Cheng
2018-12-05 8:43 [v2,4/4] arm: dts: mt2701: add uart APDMA to device tree Long Cheng
2018-12-05 8:43 ` [PATCH v2 4/4] " Long Cheng
2018-12-05 8:43 ` Long Cheng
2018-12-05 21:07 [v2,2/4] dmaengine: mtk_uart_dma: add Mediatek uart DMA support Sean Wang
2018-12-05 21:07 ` [PATCH v2 2/4] " Sean Wang
2018-12-05 21:07 ` Sean Wang
2018-12-06 9:55 [v2,2/4] " Long Cheng
2018-12-06 9:55 ` [PATCH v2 2/4] " Long Cheng
2018-12-06 9:55 ` Long Cheng
2018-12-06 21:22 [v2,2/4] " Sean Wang
2018-12-06 21:22 ` [PATCH v2 2/4] " Sean Wang
2018-12-06 21:22 ` Sean Wang
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=20181205185042.GA27295@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=long.cheng@mediatek.com \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=vkoul@kernel.org \
--cc=yingjoe.chen@mediatek.com \
--cc=yt.shen@mediatek.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 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.