From: drEagle <drEagle@DOUKKI.NET>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 1/1] ARM: kirkwood: add mvsdio driver
Date: Fri, 25 Jul 2014 18:36:35 +0200 [thread overview]
Message-ID: <53D28793.2020003@DOUKKI.NET> (raw)
In-Reply-To: <53D26ECE.2050104@denx.de>
Hi Stefan,
On 25/07/2014 16:50, Stefan Roese wrote:
> On 25.07.2014 15:27, Gerald Kerma wrote:
>> This patch add Marvell kirkwood MVSDIO/MMC driver
>> and enable it for Sheevaplugs and OpenRD boards.
>>
>> Signed-off-by: Gerald Kerma <drEagle@doukki.net>
>
> Please don't send this patch as base64 encoded. It makes it impossible to apply this patch or run checkpatch on it.
I use git send-email and I have used the default encoding [UTF-8], what is the preferred format that I may specify ?
> Did you run it though checkpatch btw?
yes, the results given is :
total: 0 errors, 0 warnings, 0 checks, 744 lines checked
Same for the coming v6 on 730 lines checked.
> I suggest to rename the driver to mvebu_mmc.c instead. This MVEBU is the generally agreed upon abbreviation for Marvell SoC's (Orion, Kirkwood, Armada XP, 370 ...).
Done,
> Doesn't it make sense to move this code to init / enable the MMC driver into the arch/cpu/... SoC code? Instead of adding it to all the board specific files?
Good idea
> Here we have this code again. I suggest to move it to the kirkwood cpu.c file instead.
Done
I'll check and send a new version (v6).
Do I rename the patch header ?
Enjoy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 538 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140725/6f1b70de/attachment.pgp>
next prev parent reply other threads:[~2014-07-25 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 13:27 [U-Boot] [PATCH v5 1/1] ARM: kirkwood: add mvsdio driver Gerald Kerma
2014-07-25 14:50 ` Stefan Roese
2014-07-25 16:36 ` drEagle [this message]
2014-07-25 17:01 ` drEagle
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=53D28793.2020003@DOUKKI.NET \
--to=dreagle@doukki.net \
--cc=u-boot@lists.denx.de \
/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