All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Chris Ball <chris@printf.net>,
	Seungwon Jeon <tgih.jun@samsung.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH 1/7] mmc: core add the property for hs200
Date: Tue, 21 Jan 2014 14:36:12 +0100	[thread overview]
Message-ID: <201401211436.12279.arnd@arndb.de> (raw)
In-Reply-To: <52DE6610.4030702@samsung.com>

On Tuesday 21 January 2014, Jaehoon Chung wrote:
> On 01/21/2014 09:12 PM, Ulf Hansson wrote:
> > On 21 January 2014 11:30, Arnd Bergmann <arnd@arndb.de> wrote:
> >> On Tuesday 21 January 2014 19:16:54 Jaehoon Chung wrote:
> >>
> >> Unfortunately, the names are not particularly intuitive (the caps2
> >> part in particular), but it's probably better to stick with that
> >> now.
> > 
> > I would prefer to remove "caps2" from the property name.
> > 
> > Going forward and cleaning up all the non needed caps flags, could
> > mean we may want to move caps2 flags into caps flags, I guess. This
> > would not be suitable if we decide to name the property as above.
> 
> Agreed,caps2 flags can be changed in future.
> I will remove the "caps2" from name.
> And i will add the document in binding/mmc/mmc.txt at next patch.
> 

In general, we have to be very careful changing these things, so we don't
break existing dts files booting with newer kernels.

In this particular case, I think we're fine, since the hs200 properties
are fairly new and haven't made it into any dts files so far.

	Arnd

      reply	other threads:[~2014-01-21 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 10:16 [PATCH 1/7] mmc: core add the property for hs200 Jaehoon Chung
2014-01-21 10:30 ` Arnd Bergmann
2014-01-21 12:12   ` Ulf Hansson
2014-01-21 12:20     ` Jaehoon Chung
2014-01-21 13:36       ` Arnd Bergmann [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=201401211436.12279.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=chris@printf.net \
    --cc=g.liakhovetski@gmx.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tgih.jun@samsung.com \
    --cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.