From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Vinod Koul <vinod.koul@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
linux-serial@vger.kernel.org, dmaengine@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>
Subject: Re: [PATCH] serial: atmel: add missing dmaengine header
Date: Thu, 16 Oct 2014 15:48:18 +0200 [thread overview]
Message-ID: <543FCCA2.20003@atmel.com> (raw)
In-Reply-To: <20141016085635.GD1638@intel.com>
On 16/10/2014 10:56, Vinod Koul :
> On Thu, Oct 16, 2014 at 11:10:59AM +0200, Greg Kroah-Hartman wrote:
>> On Thu, Oct 16, 2014 at 01:09:57PM +0530, Vinod Koul wrote:
>>> The atmel serial driver uses dmaengine APIs but never included the dmaengine
>>> header as it was getting inculded thru one of driver headers.
>>>
>>> commit 3d588f83e4d6a5230d9094b97d38621cbaa9a972 - "dmaengine: dw: split
>>> dma-dw.h to platform and private parts" broke this as it moved headers
>>> around. Fix this by doing the right thing to include the dmaengine header
>>>
>>> Reported-by: kbuild test robot <fengguang.wu@intel.com>
>>> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
>>> ---
>>> Greg, since this is path which broke this is sitting in my next, would it be
>>> okay to carry this thru dmaengine tree as get it merged in current window.
>>> Planning to send pull request in day or so to Linus
>>
>> Sure, that's fine with me:
>>
>> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Thanks :)
>
> Applied, and pushed now
Vinod, thanks a lot for having handled this issue.
For the record even if it's too late:
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Bye,
--
Nicolas Ferre
prev parent reply other threads:[~2014-10-16 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 7:39 [PATCH] serial: atmel: add missing dmaengine header Vinod Koul
2014-10-16 8:42 ` Andy Shevchenko
2014-10-16 8:11 ` Vinod Koul
2014-10-16 9:10 ` Greg Kroah-Hartman
2014-10-16 8:56 ` Vinod Koul
2014-10-16 13:48 ` Nicolas Ferre [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=543FCCA2.20003@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-serial@vger.kernel.org \
--cc=vinod.koul@intel.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.