From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: randconfig errors
Date: Wed, 20 Feb 2013 12:06:35 +0530 [thread overview]
Message-ID: <20130220063635.GE23302@intel.com> (raw)
In-Reply-To: <201302152012.04128.arnd@arndb.de>
On Fri, Feb 15, 2013 at 08:12:03PM +0000, Arnd Bergmann wrote:
> On Friday 15 February 2013, Matt Porter wrote:
> > I'd be happy to see at least the compat() patch be picked up. Chris had
> > to drop the omap_hsmmc dt dmaengine patches until that one is merged. I'm
> > not sure whose tree that one should go through at this point...perhaps
> > via Chris' tree now?
>
> It really should have been in the crypto tree before Mark's patches
> to use them, but if Chris is still considering the the hsmmc dt
> patches for 3.9, including them there is probably the best way forward.
>
> I would expect him to say no them at this point though, and in that
> case, I think it should be either the slave-dma tree or the arm-soc
> tree.
Do you want me to add the compat() patch? I had acked it sometime back
I was hoping to send the PULL request in a day or two... Pls let me know...
--
~Vinod
next prev parent reply other threads:[~2013-02-20 6:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 17:25 randconfig errors Rob Herring
2013-02-15 18:00 ` Arnd Bergmann
2013-02-15 20:11 ` Mike Turquette
2013-02-15 20:28 ` Troy Kisky
2013-02-22 9:29 ` Arnd Bergmann
2013-02-15 18:22 ` Marc Zyngier
2013-02-15 18:47 ` Marc Zyngier
2013-02-15 19:16 ` Christoffer Dall
2013-02-15 19:22 ` Marc Zyngier
2013-02-15 19:24 ` Christoffer Dall
[not found] ` <c01a8ed845054b9d9cbddb341bac5f0e@DLEE74.ent.ti.com>
2013-02-15 19:45 ` Matt Porter
2013-02-15 20:12 ` Arnd Bergmann
2013-02-15 20:25 ` Chris Ball
2013-02-20 6:36 ` Vinod Koul [this message]
2013-02-20 9:53 ` Arnd Bergmann
2013-02-21 10:38 ` Shawn Guo
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=20130220063635.GE23302@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).