From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: arm-soc samsung patches blocked on dmaengine patches
Date: Fri, 4 Nov 2011 14:00:43 +0100 [thread overview]
Message-ID: <201111041400.44486.arnd@arndb.de> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Vinod Koul <vinod.koul@intel.com>, Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: arm-soc samsung patches blocked on dmaengine patches
Date: Fri, 4 Nov 2011 14:00:43 +0100 [thread overview]
Message-ID: <201111041400.44486.arnd@arndb.de> (raw)
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
next reply other threads:[~2011-11-04 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 13:00 Arnd Bergmann [this message]
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:06 ` Koul, Vinod
2011-11-04 13:17 ` Kukjin Kim
2011-11-04 13:17 ` Kukjin Kim
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=201111041400.44486.arnd@arndb.de \
--to=arnd@arndb.de \
--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.