devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
	<kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: [PATCH] of: Add vendor prefix for Energy Micro
Date: Tue, 25 Mar 2014 20:59:50 +0100	[thread overview]
Message-ID: <20140325195950.GB15793@pengutronix.de> (raw)
In-Reply-To: <CAL_Jsq+TVKywqbQ4vePQWjgbZ4Zc_d_CUrx6R33-pHtxVtsAzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, Mar 25, 2014 at 11:51:33AM -0500, Rob Herring wrote:
> On Tue, Mar 25, 2014 at 9:11 AM, Uwe Kleine-König
> <u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> wrote:
> > There are already patches floating around to add
> > energymicro,efm32-{i2c,serial,spi} as compatible strings.
> 
> "Patches floating around" is not a very convincing argument why
> "silabs" should not just be used instead. I have no problem taking
> this, but if changing to silabs is possible, we may want to do that.
I think energymicro is still the right prefix, because back when efm32
was created it was still Energy Micro. Or am I wrong here?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-03-25 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 14:11 [PATCH] of: Add vendor prefix for Energy Micro Uwe Kleine-König
     [not found] ` <1395756677-6166-1-git-send-email-u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-03-25 16:35   ` Mark Rutland
2014-03-25 16:51   ` Rob Herring
     [not found]     ` <CAL_Jsq+TVKywqbQ4vePQWjgbZ4Zc_d_CUrx6R33-pHtxVtsAzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-25 19:59       ` Uwe Kleine-König [this message]
     [not found]         ` <20140325195950.GB15793-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-03-31 22:03           ` Uwe Kleine-König
     [not found]             ` <20140331220334.GB6045-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-03-31 23:21               ` Wolfram Sang
2014-04-01 12:10               ` Rob Herring
2014-07-23 20:22   ` Uwe Kleine-König
     [not found]     ` <1406146969-26279-1-git-send-email-u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-07-24 10:38       ` Mark Rutland
2014-09-26 16:34         ` Rob Herring

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=20140325195950.GB15793@pengutronix.de \
    --to=u.kleine-koenig-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).