From: Kukjin Kim <kgene.kim@samsung.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Kukjin Kim <kgene.kim@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: arm-soc samsung patches blocked on dmaengine patches
Date: Fri, 04 Nov 2011 22:17:42 +0900 [thread overview]
Message-ID: <4EB3E5F6.7060705@samsung.com> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A446301087AA53D66@bgsmsx502.gar.corp.intel.com>
On 11/04/11 22:06, Koul, Vinod wrote:
>> Hi Vinod and Kukjin,
>>
>> Right now, all the patches from the arm-soc tree are merged into 3.2, but the
>> samsung/cleanup and samsung/devel series are missing because they depend on
>> patches in the dmaengine tree. I'm not sure about the status of that tree,
>> but I didn't see a pull request for them yet.
>>
>> Should I just submit the samsung tree with the dmaengine patches included,
>> or keep waiting?
>>
> Arnd,
>
> I have already sent pull request to Linus on Monday[1], still waiting for
> these to get merged
>
Arnd,
So I think you can send them to Linus.
And as a note, I sent next-samsung-devel-4 which includes supporting
EXYNOS4 DT and reorganization mach-exynos and something to you. I hope
you can pick them up with others too. If any problems, please let me know.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-11-04 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 13:00 arm-soc samsung patches blocked on dmaengine patches Arnd Bergmann
2011-11-04 13:06 ` Koul, Vinod
2011-11-04 13:17 ` Kukjin Kim [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=4EB3E5F6.7060705@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox