From: Marek Vasut <marex@denx.de>
To: Sonic Zhang <sonic.adi@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org,
adi-buildroot-devel@lists.sourceforge.net,
Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH v2] crypt: bfin_crc: access crc registers by readl and writel functions
Date: Thu, 10 Apr 2014 10:01:34 +0200 [thread overview]
Message-ID: <201404101001.34907.marex@denx.de> (raw)
In-Reply-To: <1397111456-17371-1-git-send-email-sonic.adi@gmail.com>
On Thursday, April 10, 2014 at 08:30:56 AM, Sonic Zhang wrote:
> From: Sonic Zhang <sonic.zhang@analog.com>
>
> Move architecture independant crc header file out of the blackfin folder.
>
>
> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> ---
> v2-changes:
> - avoid combine the IO accessors into each other
> - use readl/writel other than ioread32/iowrite32
Reviewed-by: Marek Vasut <marex@denx.de>
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-10 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 6:30 [PATCH v2] crypt: bfin_crc: access crc registers by readl and writel functions Sonic Zhang
2014-04-10 8:01 ` Marek Vasut [this message]
2014-04-14 4:21 ` Sonic Zhang
2014-04-16 13:48 ` 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=201404101001.34907.marex@denx.de \
--to=marex@denx.de \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=sonic.adi@gmail.com \
--cc=sonic.zhang@analog.com \
/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).