mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: "Matt Porter" <mporter@konsulko.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Linux OMAP List" <linux-omap@vger.kernel.org>,
	"Linux ARM Kernel List" <linux-arm-kernel@lists.infradead.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: enable aes and sham
Date: Fri, 6 Mar 2015 08:56:41 -0800	[thread overview]
Message-ID: <20150306165641.GQ13520@atomide.com> (raw)
In-Reply-To: <CAOCHtYisxjpQM4zvotNxhj3KaYrqb3cgCbTXPXphB1ZV2jCZ8w@mail.gmail.com>

* Robert Nelson <robertcnelson@gmail.com> [150225 11:13]:
> On Wed, Feb 25, 2015 at 12:52 PM, Matt Porter <mporter@konsulko.com> wrote:
> > Beaglebone Black doesn't have AES and SHAM enabled like the
> > original Beaglebone White dts. This breaks applications that
> > leverage the crypto blocks so fix this by enabling these nodes
> > in the am335x-bone-common.dtsi. With this change, enabling the
> > nodes in am335x-bone.dts is no longer required so remove them.
> >
> > Signed-off-by: Matt Porter <mporter@konsulko.com>
> 
> Looks good! Wonder why didn't we do this sooner! ;)
> 
> Acked-by: Robert Nelson <robertcnelson@gmail.com>

Applying both into omap-for-v4.0/fixes thanks.

Tony

      reply	other threads:[~2015-03-06 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 18:52 Matt Porter
2015-02-25 19:09 ` Robert Nelson
2015-03-06 16:56   ` Tony Lindgren [this message]

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=20150306165641.GQ13520@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mporter@konsulko.com \
    --cc=robertcnelson@gmail.com \
    --cc=robh+dt@kernel.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

Powered by JetHome