Linux cryptographic layer development
 help / color / mirror / Atom feed
From: James Hsiao <jhsiao@amcc.com>
To: Sebastian Andrzej Siewior <linux-crypto@ml.breakpoint.cc>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] AMCC Crypto4xx Device Driver v2
Date: Wed, 29 Oct 2008 16:05:24 -0700	[thread overview]
Message-ID: <1225321524.4841.58.camel@jhsiao-usb> (raw)
In-Reply-To: <20081029131428.GA13501@Chamillionaire.breakpoint.cc>

I think the patch format in the email is incorrect, so the one go to
linux-crypto was filtered out. And the one directly to Kim was received
and Kim kindly reviewed....

Thanks for review.

James

On Wed, 2008-10-29 at 14:14 +0100, Sebastian Andrzej Siewior wrote:
> * James Hsiao | 2008-10-27 18:55:32 [-0700]:
> >Kim suggest us submit this to linuxppc-dev for more review.
> so do I
> 
> >> 
> >> diff --git a/arch/powerpc/boot/dts/kilauea.dts b/arch/powerpc/boot/dts/kilauea.dts
> >> index dececc4..58b48a0 100644
> >> --- a/arch/powerpc/boot/dts/kilauea.dts
> >> +++ b/arch/powerpc/boot/dts/kilauea.dts
> >> @@ -1,4 +1,4 @@
> >> -/*
> >> +/* 
> >>   * Device Tree Source for AMCC Kilauea (405EX)
> >>   *
> Usually we are removing leading/trailing blanks. Not the other way
> around. 
> I haven't seen this change in the submit at Date: Fri, 19 Sep 2008
> 16:46:43 -0700. Is this an updated version or does my mailbox leak
> emails?
> 
> Sebastian


  reply	other threads:[~2008-10-29 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1225158336-8777-1-git-send-email-jhsiao@amcc.com>
2008-10-28  1:55 ` [PATCH] AMCC Crypto4xx Device Driver v2 James Hsiao
2008-10-28 22:49   ` Kim Phillips
2008-10-29 13:14   ` Sebastian Andrzej Siewior
2008-10-29 23:05     ` James Hsiao [this message]
     [not found] <1224189246-11440-1-git-send-email-jhsiao@amcc.com>
     [not found] ` <0CA0A16855646F4FA96D25A158E299D69CF4CB@SDCEXCHANGE01.ad.amcc.com>
2008-10-20 21:14   ` Kim Phillips

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=1225321524.4841.58.camel@jhsiao-usb \
    --to=jhsiao@amcc.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@ml.breakpoint.cc \
    --cc=linux-crypto@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