From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: crypto: omap-sham, omap-aes and dma_request_slave_channel_compat()
Date: Wed, 27 Feb 2013 11:01:09 +0530 [thread overview]
Message-ID: <20130227053109.GA28537@intel.com> (raw)
In-Reply-To: <20130226225205.GA13338@animalcreek.com>
On Tue, Feb 26, 2013 at 03:52:05PM -0700, Mark A. Greer wrote:
> [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?
Yes we had agreed that I will send it.
I have applied this one now, and will send second PULL request to Linus soon.
Arnd,
The second patch of dw_dmac you wnated to send me fails to apply for me. Can you
either rebase or send with your updates with my ack?
Either ways let me know
--
~Vinod
next prev parent reply other threads:[~2013-02-27 5:31 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 ` crypto: omap-sham, omap-aes and dma_request_slave_channel_compat() Mark A. Greer
2013-02-27 5:31 ` Vinod Koul [this message]
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=20130227053109.GA28537@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).