Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@animalcreek.com>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: herbert@gondor.apana.org.au, Arnd Bergmann <arnd@arndb.de>,
	Vinod Koul <vinod.koul@intel.com>,
	linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	dmitry.kasatkin@intel.com,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: crypto: omap-sham, omap-aes and dma_request_slave_channel_compat()
Date: Tue, 26 Feb 2013 15:52:05 -0700	[thread overview]
Message-ID: <20130226225205.GA13338@animalcreek.com> (raw)
In-Reply-To: <512D00BE.8090204@canonical.com>

[CC'ing more people & lists.]

On Tue, Feb 26, 2013 at 11:36:46AM -0700, Tim Gardner wrote:
> Whats up with commits 0e87e73f4abe1ada69cf780fe2550c6361a1b53b and
> b4b87a934c30fb91cbdd18ae028acdc361e1cf0f. As far as I can tell,
> dma_request_slave_channel_compat() does not exist in 3.9 as of
> 52caa59ed335616c5254adff7911465a57ed9f14, nor does it exist in
> linux-next as of Feb 26. Am I just being dense ?

Yeah, order got a little messed up.  The problem is known and the
sub-thread talking about it starts about here:

	http://www.spinics.net/lists/arm-kernel/msg225241.html

with the conclusion (AFAICT) that Vinod is to push it:

	http://www.spinics.net/lists/arm-kernel/msg226062.html

> Reverting those 2 commits at least allows the compile complete.

When the dependencies are sorted out, will you revert the revert
or do I need to do something?

Mark
--

       reply	other threads:[~2013-02-26 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <512D00BE.8090204@canonical.com>
2013-02-26 22:52 ` Mark A. Greer [this message]
2013-02-27  5:31   ` crypto: omap-sham, omap-aes and dma_request_slave_channel_compat() Vinod Koul
2013-02-27 21:36     ` Arnd Bergmann
2013-02-28  4:24       ` 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=20130226225205.GA13338@animalcreek.com \
    --to=mgreer@animalcreek.com \
    --cc=arnd@arndb.de \
    --cc=dmitry.kasatkin@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tim.gardner@canonical.com \
    --cc=tony@atomide.com \
    --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