From: Tim Gardner <tim.gardner@canonical.com>
To: mgreer@animalcreek.com
Cc: herbert@gondor.hengli.com.au, dmitry.kasatkin@intel.com,
linux-kernel@vger.kernel.org
Subject: crypto: omap-sham, omap-aes and dma_request_slave_channel_compat()
Date: Tue, 26 Feb 2013 11:36:46 -0700 [thread overview]
Message-ID: <512D00BE.8090204@canonical.com> (raw)
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 ?
Reverting those 2 commits at least allows the compile complete.
rtg
--
Tim Gardner tim.gardner@canonical.com
next reply other threads:[~2013-02-26 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 18:36 Tim Gardner [this message]
2013-02-26 22:52 ` crypto: omap-sham, omap-aes and dma_request_slave_channel_compat() Mark A. Greer
2013-02-27 5:31 ` 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=512D00BE.8090204@canonical.com \
--to=tim.gardner@canonical.com \
--cc=dmitry.kasatkin@intel.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mgreer@animalcreek.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;
as well as URLs for NNTP newsgroup(s).