linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] mmc: arasan: Add driver for Arasan SDHCI
Date: Tue, 12 Nov 2013 09:53:34 +0100	[thread overview]
Message-ID: <5281EC8E.90501@monstr.eu> (raw)
In-Reply-To: <b3f788b3-dfc3-422e-9a74-b796c0fd3207@DB8EHSMHS004.ehs.local>

Hi Chris,

On 11/06/2013 10:41 PM, S?ren Brinkmann wrote:
> Hi Chris,
> 
> any comments from your side? Could you consider applying it to your
> tree, please?

any update on this one?

What's the naming convention we should follow?

Is sdhci-of-arasan.c OK? Or should we use sdhci-arasan.c instead?

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131112/fe6acd8f/attachment.sig>

  reply	other threads:[~2013-11-12  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 16:38 [PATCH v2 1/2] mmc: arasan: Add driver for Arasan SDHCI Soren Brinkmann
2013-10-30 16:38 ` [PATCH v2 2/2] arm: dt: zynq: Add SDHCI nodes Soren Brinkmann
2013-10-30 23:42 ` [PATCH v2 1/2] mmc: arasan: Add driver for Arasan SDHCI Rob Herring
2013-11-06 21:41 ` Sören Brinkmann
2013-11-12  8:53   ` Michal Simek [this message]
2013-11-26 23:22 ` Chris Ball
2013-11-26 23:39   ` Sören Brinkmann
2013-11-27  5:28     ` Michal Simek

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=5281EC8E.90501@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=linux-arm-kernel@lists.infradead.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).