linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bcousson@baylibre.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information
Date: Wed, 21 Aug 2013 15:31:11 +0200	[thread overview]
Message-ID: <5214C11F.8090808@baylibre.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1308210012420.6426@utopia.booyaka.com>

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

  reply	other threads:[~2013-08-21 13:31 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 [this message]
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
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=5214C11F.8090808@baylibre.com \
    --to=bcousson@baylibre.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).