From: lokeshvutla@ti.com (Lokesh Vutla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information
Date: Thu, 22 Aug 2013 14:24:01 +0530 [thread overview]
Message-ID: <5215D1A9.4000508@ti.com> (raw)
In-Reply-To: <5215CCFE.6040500@baylibre.com>
Hi Benoit,
On Thursday 22 August 2013 02:04 PM, Benoit Cousson wrote:
> Hi Lokesh,
>
> On 22/08/2013 05:50, Lokesh Vutla wrote:
>> Hi Benoit,
>> On Wednesday 21 August 2013 07:11 PM, Benoit Cousson wrote:
>>> Hi Mark,
>>>
>>> In fact I cannot even apply these patches since they are referring the the edma controller node that does not seem to be there in 3.11-rc6.
>>>
>>> Is this EDMA series supposed to be merged for 3.12? If this is the case, where can I find a reference GIT for it?
>> The following EDMA support dt patch series from Joel is needed :
>> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg92176.html
>> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg92177.html
>
> Thanks, it works a little bit better with these patches :-)
>
> What about the EDMA driver? Is this already in mainline or planned for 3.12?
Its already in mainline..:)
Thanks and regards,
Lokesh
>
> Thanks,
> Benoit
>
>>
>> Thanks and Regards,
>> Lokesh
>>>
>>> Thanks,
>>> Benoit
>>>
>>> On 21/08/2013 15:31, Benoit Cousson wrote:
>>>> Hi Paul,
>>>>
>>>> On 21/08/2013 02:13, Paul Walmsley wrote:
>>>>> Hi Beno?t,
>>>>>
>>>>> On Wed, 17 Jul 2013, Mark A. Greer wrote:
>>>>>
>>>>>> From: "Mark A. Greer" <mgreer@animalcreek.com>
>>>>>>
>>>>>> Long overdue patches to add the device tree updates and
>>>>>> documentation for the SHAM and AES modules on the am33xx.
>>>>>> The supporting code is already in the mainline kernel.
>>>>>>
>>>>>> This series is based on the current mainline kernel,
>>>>>> c0d15cc (linked-list: Remove __list_for_each).
>>>>>>
>>>>>> Changes from v1:
>>>>>> - Added missing '};' as pointed out by Lokesh Vutla
>>>>>> <lokeshvutla@ti.com>
>>>>>
>>>>> I guess you should take these patches?
>>>>
>>>> You're right, I should, I've just never seen them :-(
>>>> Thanks for the pointer.
>>>>
>>>> Mark,
>>>>
>>>> After a quick search on Google, I did not see any comment on these
>>>> patches. Did you get any review so far?
>>>>
>>>> Thanks,
>>>> Benoit
>>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>>> the body of a message to majordomo at vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
next prev parent reply other threads:[~2013-08-22 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 16:23 [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information Mark A. Greer
2013-07-17 16:23 ` [PATCH v2 1/2] ARM: dts: Add SHAM data and documentation for AM33XX Mark A. Greer
2013-08-22 14:08 ` Mark Rutland
2013-07-17 16:23 ` [PATCH v2 2/2] ARM: dts: Add AES " Mark A. Greer
2013-08-21 0:13 ` [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information Paul Walmsley
2013-08-21 13:31 ` Benoit Cousson
2013-08-21 13:41 ` Benoit Cousson
2013-08-21 20:31 ` Mark A. Greer
2013-08-22 3:50 ` Lokesh Vutla
2013-08-22 8:34 ` Benoit Cousson
2013-08-22 8:54 ` Lokesh Vutla [this message]
2013-08-22 21:24 ` Mark A. Greer
2013-08-23 16:53 ` Joel Fernandes
2013-08-21 20:40 ` Mark A. Greer
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=5215D1A9.4000508@ti.com \
--to=lokeshvutla@ti.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).