From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bastian Hecht <hechtb@googlemail.com>
Cc: Bastian Hecht <hechtb@gmail.com>,
linux-mtd@lists.infradead.org,
Linux-SH <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 1/2] mtd: sh_flctl: Use memcpy() instead of using a loop
Date: Wed, 18 Jul 2012 12:03:13 +0000 [thread overview]
Message-ID: <1342612993.7530.20.camel@brekeke> (raw)
In-Reply-To: <1341484862-24033-1-git-send-email-hechtb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
On Thu, 2012-07-05 at 12:41 +0200, Bastian Hecht wrote:
> Elemets have been copied "manually" in a loop. Better use memcpy().
>
> Signed-off-by: Bastian Hecht <hechtb@gmail.com>
Pushed both to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-07-18 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 10:41 [PATCH 1/2] mtd: sh_flctl: Use memcpy() instead of using a loop Bastian Hecht
2012-07-05 10:41 ` [PATCH 2/2] mtd: sh_flctl: Only copy OOB data if it is required Bastian Hecht
2012-07-06 0:10 ` [PATCH 1/2] mtd: sh_flctl: Use memcpy() instead of using a loop Simon Horman
2012-07-18 12:03 ` Artem Bityutskiy [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=1342612993.7530.20.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=hechtb@gmail.com \
--cc=hechtb@googlemail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).