mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Daniel Drake <dsd@laptop.org>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
	Bergmann Arnd <arnd@arndb.de>,
	"devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@linaro.org>,
	Neil Zhang <zhangwm@marvell.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V3 1/3] dts: change Marvell prefix to 'marvell'
Date: Fri, 12 Jul 2013 11:57:33 -0400	[thread overview]
Message-ID: <20130712155733.GZ11908@titan.lakedaemon.net> (raw)
In-Reply-To: <CAMLZHHQGZvDssY-YxQ3ZW8FYhpG-H1-VbokOid33socRSPrMNw@mail.gmail.com>

On Fri, Jul 12, 2013 at 09:10:49AM -0600, Daniel Drake wrote:
> On Thu, Jul 11, 2013 at 5:54 PM, Haojian Zhuang
> <haojian.zhuang@gmail.com> wrote:
> >> Well, Daniel Drake spoke up for OLPC.  Does that count?
> >
> > We don't know they used DT on Marvell MMP2/MMP3. So they don't have DTS file
> > in kernel, we could use both old name & new name in driver.
> 
> You are listed as one of the MMP maintainers in the MAINTAINERS file
> and I have sent you several patches in the few 3 weeks which make
> OLPC's usage of MMP + DT pretty obvious. As a maintainer I believe you
> are supposed to review the patches too. hint hint ;)
> 
> My request to avoid breaking compatibility actually comes as a
> two-prong request.
> 
> I would prefer to see these compatible properties stay the same as it
> seems like changing them has little purpose/benefit - and there *will*
> become a later point where changing them causes major breakage.

I agree with both of you :)  It needs to stabilise quickly, but since
the first inception of Marvell compatible strings was in the mv643xx_eth
driver for powerpc (long before ARM thought it was cool), and they used
"marvell,...", I think we should stick with that.

Which means doing as Haojian now realizes, and having both strings in
the relevant drivers.

This also means we should do a patch for stable v3.5+ appending the
"mrvl,..." string to the drivers that had it removed improperly, as
Daniel discovered.  Daniel, since you are probably most familiar (and
most able to test ;-) ), would you mind putting that patch together?

So we don't have to keep it around forever, we could do as Arnd has
suggested in the past (for an entirely different problem):

	/* assuming it goes in for v3.12 */
	if (WARN_ON(of_device_is_compatible(dev, "mrvl,..."))) {
		dev_info(&dev->dev, "compatible string \"mrvl,...\" being removed in v3.15\n");
		BUG_ON(LINUX_VERSION_CODE >= KERNEL_VERSION(3,15,0));
	}

* I can't find where Arnd's suggestion was, so this hack is completely
my own.

Keep in mind, the above hack is just a suggestion, it makes my skin
crawl just looking at it... I'm open to other ideas.  Or, not doing it
at all.

thx,

Jason.

  reply	other threads:[~2013-07-12 15:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  6:42 [PATCH V3 0/3] bring up pxa988 with DT Neil Zhang
2013-07-09  6:42 ` [PATCH V3 1/3] dts: change Marvell prefix to 'marvell' Neil Zhang
2013-07-09 12:49   ` Jason Cooper
2013-07-10  7:25     ` Neil Zhang
2013-07-10 12:20       ` Jason Cooper
2013-07-10 14:41         ` Daniel Drake
2013-07-10  8:19     ` Haojian Zhuang
2013-07-10 12:24       ` Jason Cooper
2013-07-10 14:08         ` Haojian Zhuang
2013-07-10 21:50           ` Jason Cooper
2013-07-11 23:54             ` Haojian Zhuang
2013-07-12 15:10               ` Daniel Drake
2013-07-12 15:57                 ` Jason Cooper [this message]
2013-07-12 16:05                   ` Daniel Drake
2013-07-12 16:14                     ` Jason Cooper
2013-07-13  0:35                 ` Haojian Zhuang
2013-07-13 14:30                   ` Daniel Drake
2013-07-13 19:56             ` Olof Johansson
2013-07-15  4:39               ` Jason Cooper
2013-07-10 20:50     ` Matt Sealey
2013-07-10 21:49       ` Jason Cooper
2013-07-11 11:20         ` Neil Zhang
2013-07-14 19:29           ` Arnd Bergmann
2013-07-17 13:37             ` Neil Zhang
2013-07-09  6:42 ` [PATCH V3 2/3] clocksource: mmp: support CLOCKSOURCE OF DECLARE Neil Zhang
2013-07-09 16:14   ` Thomas Petazzoni
2013-07-09 21:16     ` Arnd Bergmann
2013-07-10  5:58       ` Haojian Zhuang
2013-07-11 11:23         ` Neil Zhang
2013-07-11 23:51           ` Haojian Zhuang
2013-07-09  6:42 ` [PATCH V3 3/3] ARM: mmp: bring up pxa988 with device tree support Neil Zhang
2013-07-09 22:05   ` Arnd Bergmann
2013-07-11 11:35     ` Neil Zhang

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=20130712155733.GZ11908@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dsd@laptop.org \
    --cc=grant.likely@linaro.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhangwm@marvell.com \
    /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

all inboxes | Powered by JetHome®