Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>
Cc: ext Herbert Xu <herbert@gondor.hengli.com.au>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] omap-sham: OMAP macros corrected
Date: Mon, 10 May 2010 10:03:29 -0700	[thread overview]
Message-ID: <20100510170328.GD16460@atomide.com> (raw)
In-Reply-To: <4BE800F3.2070602@nokia.com>

* Dmitry Kasatkin <dmitry.kasatkin@nokia.com> [100510 05:45]:
> 
> On 10/05/10 15:14, ext Herbert Xu wrote:
> > On Mon, May 10, 2010 at 03:07:55PM +0300, Dmitry Kasatkin wrote:
> >   
> >> Signed-off-by: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>
> >> ---
> >>  arch/arm/mach-omap2/devices.c |    4 ++--
> >>  1 files changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> >> index beac46c..79dbf04 100644
> >> --- a/arch/arm/mach-omap2/devices.c
> >> +++ b/arch/arm/mach-omap2/devices.c
> >> @@ -456,7 +456,7 @@ static inline void omap_init_mcspi(void) {}
> >>  
> >>  #if defined(CONFIG_CRYPTO_DEV_OMAP_SHAM) || defined(CONFIG_CRYPTO_DEV_OMAP_SHAM_MODULE)
> >>  
> >> -#ifdef CONFIG_ARCH_OMAP24XX
> >> +#ifdef CONFIG_ARCH_OMAP2
> >>  static struct resource omap2_sham_resources[] = {
> >>  	{
> >>  		.start	= OMAP24XX_SEC_SHA1MD5_BASE,
> >> @@ -474,7 +474,7 @@ static int omap2_sham_resources_sz = ARRAY_SIZE(omap2_sham_resources);
> >>  #define omap2_sham_resources_sz		0
> >>  #endif
> >>  
> >> -#ifdef CONFIG_ARCH_OMAP34XX
> >> +#ifdef CONFIG_ARCH_OMAP3
> >>  static struct resource omap3_sham_resources[] = {
> >>  	{
> >>  		.start	= OMAP34XX_SEC_SHA1MD5_BASE,
> >>     
> > Hi Tony:
> >
> > If I add this patch to cryptodev, is this going to cause any
> > problems for you?
> >
> > Thbanks,
> >   
> Hi,
> 
> I should not be any problem, because it indeed needs to be like that.

Yeah please go ahead and add it. If we run into merge problems with
devices.c, we move some patches into omap for-next branch.

Acked-by: Tony Lindgren <tony@atomide.com>

  reply	other threads:[~2010-05-10 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 12:07 [PATCH 1/1] omap-sham: OMAP macros corrected Dmitry Kasatkin
2010-05-10 12:14 ` Herbert Xu
2010-05-10 12:49   ` Dmitry Kasatkin
2010-05-10 17:03     ` Tony Lindgren [this message]
2010-05-14  4:46       ` Herbert Xu

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=20100510170328.GD16460@atomide.com \
    --to=tony@atomide.com \
    --cc=dmitry.kasatkin@nokia.com \
    --cc=herbert@gondor.hengli.com.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-omap@vger.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