From: James Hsiao <jhsiao@amcc.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linuxppc-dev@ozlabs.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] AMCC Crypto4xx Device Driver v5
Date: Wed, 28 Jan 2009 09:41:56 -0800 [thread overview]
Message-ID: <1233164516.4809.9.camel@jhsiao-usb> (raw)
In-Reply-To: <20090128035937.GA13157@gondor.apana.org.au>
Hi Herbert,
I will re submit the patch with proper changelog.
I had the change log this way is for the reviewer easy to see the
difference. But, I agree this is not proper for a newly created driver.
Thanks
James
On Wed, 2009-01-28 at 14:59 +1100, Herbert Xu wrote:
> On Mon, Jan 12, 2009 at 11:30:50AM -0800, James Hsiao wrote:
> > This is the 5th submission of AMCC's security driver.
> > - remove aad support in build pd function, since we didn't release any
> > algorithm that use aead yet.
> >
> > - changed some hardcode value to #defines
> >
> > - changed local_irq_disable/enable to spinlock_irq_save/restore
> >
> > - fixed bug in crypto4xx_probe on error exit.
> >
> >
> > Signed-off-by: James Hsiao <jhsiao@amcc.com>
>
> I was going to apply this but you didn't give me a changelog
> that I can throw into the tree without feeling guilty!
>
> Please always attach a proper changelog with each submission
> so I don't have to do this. You can put the changelog elsewhere
> in the email.
>
> Thanks,
next prev parent reply other threads:[~2009-01-28 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 19:30 [PATCH] AMCC Crypto4xx Device Driver v5 James Hsiao
2009-01-28 3:59 ` Herbert Xu
2009-01-28 17:41 ` James Hsiao [this message]
2009-01-28 21:29 ` 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=1233164516.4809.9.camel@jhsiao-usb \
--to=jhsiao@amcc.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).