From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: dmaengine: Update + Hand over the at_hdmac driver to Ludovic
Date: Tue, 3 Jan 2017 09:13:54 +0530 [thread overview]
Message-ID: <20170103034353.GC3573@localhost> (raw)
In-Reply-To: <20170102164208.6038-1-nicolas.ferre@atmel.com>
On Mon, Jan 02, 2017 at 05:42:08PM +0100, Nicolas Ferre wrote:
> Hand over the Microchip / Atmel DMA driver handled by at_hdmac driver
> to Ludovic who is responsible for the newer at_xdmac driver as well.
> Also update the entry name and position to follow company changes.
Applied now
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Ludovic Desroches <ludovic.desroches@atmel.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: dmaengine: Update + Hand over the at_hdmac driver to Ludovic
Date: Tue, 3 Jan 2017 09:13:54 +0530 [thread overview]
Message-ID: <20170103034353.GC3573@localhost> (raw)
In-Reply-To: <20170102164208.6038-1-nicolas.ferre@atmel.com>
On Mon, Jan 02, 2017 at 05:42:08PM +0100, Nicolas Ferre wrote:
> Hand over the Microchip / Atmel DMA driver handled by at_hdmac driver
> to Ludovic who is responsible for the newer at_xdmac driver as well.
> Also update the entry name and position to follow company changes.
Applied now
--
~Vinod
next prev parent reply other threads:[~2017-01-03 3:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 16:42 [PATCH] MAINTAINERS: dmaengine: Update + Hand over the at_hdmac driver to Ludovic Nicolas Ferre
2017-01-02 16:42 ` Nicolas Ferre
2017-01-03 3:43 ` Vinod Koul [this message]
2017-01-03 3:43 ` Vinod Koul
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=20170103034353.GC3573@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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.