linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Sekhar Nori <nsekhar@ti.com>, Nishanth Menon <nm@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	linux kernel <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	devicetree <devicetree@vger.kernel.org>,
	Jason Kridner <jkridner@beagleboard.org>
Subject: Re: [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1
Date: Fri, 2 Sep 2016 08:06:49 -0700	[thread overview]
Message-ID: <20160902150648.lgbhxvyapo4p3lg3@atomide.com> (raw)
In-Reply-To: <CAOCHtYiFjB-cuABmCiw96spc-De+qNNQYGrjp-MmNDuH2mJ9Bw@mail.gmail.com>

* Robert Nelson <robertcnelson@gmail.com> [160902 06:52]:
> On Fri, Sep 2, 2016 at 5:41 AM, Sekhar Nori <nsekhar@ti.com> wrote:
> > Instead, it seems to be easier for maintenance and safer overall if the
> > older version has a file of its own which can be kept alone.
> >
> > Also, how about renaming the existing dts to am57xx-beagle-x15-reva2.dts
> > and let the production version be called am57xx-beagle-x15.dts? Surely
> > this will cause some inconvenience to A2 users. But there are few users
> > of those and it might be more intuitive for the majority users if the
> > file for production version is without a specific version string
> > attached. Just a thought though, not sure about it myself either.
> 
> Nak, let's NOT do that to A2 users.
> 
> The am57xx-beagle-x15.dts went mainline in v3.19, u-boot installed on
> devices would need to be updated and this would make bisecting a pain.
> ;)

I agree, let's keep things working without forcing people to update
their u-boot enviroment for the dtb name.

Regards,

Tony

  parent reply	other threads:[~2016-09-02 15:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  9:05 [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon
2016-09-02  9:05 ` [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations Nishanth Menon
2016-09-02 10:18   ` Sekhar Nori
2016-09-02 14:52     ` Nishanth Menon
2016-09-02  9:06 ` [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1 Nishanth Menon
2016-09-02  9:58   ` Tomi Valkeinen
2016-09-02 10:01     ` Nishanth Menon
2016-09-02 11:48       ` Tomi Valkeinen
2016-09-02 10:41   ` Sekhar Nori
2016-09-02 11:18     ` Tomi Valkeinen
2016-09-02 13:52     ` Robert Nelson
2016-09-02 15:01       ` Nishanth Menon
2016-09-02 15:06       ` Tony Lindgren [this message]
2016-09-06 10:10       ` Sekhar Nori
2016-09-06 20:05         ` Tony Lindgren
2016-09-07  5:09           ` Sekhar Nori
2016-09-02  9:14 ` [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon

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=20160902150648.lgbhxvyapo4p3lg3@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jkridner@beagleboard.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).