From: Brian Norris <computersforpeace@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFC 0/7] ARM: dts: Add compatible property to "partitions" node
Date: Mon, 14 Dec 2015 21:43:12 +0000 [thread overview]
Message-ID: <20151214214312.GA86857@google.com> (raw)
In-Reply-To: <CAMuHMdW=wJEoi-+EWAKBjRwb+QFvk=iFur1yFqR=q0f4zwzb2Q@mail.gmail.com>
On Mon, Dec 14, 2015 at 10:20:19PM +0100, Geert Uytterhoeven wrote:
> On Mon, Dec 14, 2015 at 8:46 PM, Brian Norris
> <computersforpeace@gmail.com> wrote:
> > On Mon, Dec 14, 2015 at 08:11:37PM +0100, Geert Uytterhoeven wrote:
> >> As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
> >> property to "partitions" node"), the "partitions" subnode of an SPI
> >> FLASH device node must have a compatible property. The partitions are no
> >> longer detected if it is not present.
> >
> > For all patches:
> >
> > Acked-by: Brian Norris <computersforpeace@gmail.com>
> >
> >> I marked this series as "RFC", as the abovementioned commit is not yet
> >> upstream. Ideally, the users should be fixed first, to avoid breakage.
>
> It breaks bisectability in mainline.
The files you are fixing are not converted in mainline yet, are they?
> > I'd differ on the last sentence. It's more important to straighten out
> > the release features for 4.4 than to make sure that linux-next has
> > perfect DTS files. So I'll submit whenever ready :)
>
> If the DTS changes go in first, bisectability is preserved.
Are you asking me to delay fixing the DT binding until 4.5, just because
your for-next branches can't be fixed? IOW, you want me to release the
bad DT binding for a whole cycle?
Brian
WARNING: multiple messages have this Message-ID (diff)
From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC 0/7] ARM: dts: Add compatible property to "partitions" node
Date: Mon, 14 Dec 2015 13:43:12 -0800 [thread overview]
Message-ID: <20151214214312.GA86857@google.com> (raw)
In-Reply-To: <CAMuHMdW=wJEoi-+EWAKBjRwb+QFvk=iFur1yFqR=q0f4zwzb2Q@mail.gmail.com>
On Mon, Dec 14, 2015 at 10:20:19PM +0100, Geert Uytterhoeven wrote:
> On Mon, Dec 14, 2015 at 8:46 PM, Brian Norris
> <computersforpeace@gmail.com> wrote:
> > On Mon, Dec 14, 2015 at 08:11:37PM +0100, Geert Uytterhoeven wrote:
> >> As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
> >> property to "partitions" node"), the "partitions" subnode of an SPI
> >> FLASH device node must have a compatible property. The partitions are no
> >> longer detected if it is not present.
> >
> > For all patches:
> >
> > Acked-by: Brian Norris <computersforpeace@gmail.com>
> >
> >> I marked this series as "RFC", as the abovementioned commit is not yet
> >> upstream. Ideally, the users should be fixed first, to avoid breakage.
>
> It breaks bisectability in mainline.
The files you are fixing are not converted in mainline yet, are they?
> > I'd differ on the last sentence. It's more important to straighten out
> > the release features for 4.4 than to make sure that linux-next has
> > perfect DTS files. So I'll submit whenever ready :)
>
> If the DTS changes go in first, bisectability is preserved.
Are you asking me to delay fixing the DT binding until 4.5, just because
your for-next branches can't be fixed? IOW, you want me to release the
bad DT binding for a whole cycle?
Brian
WARNING: multiple messages have this Message-ID (diff)
From: Brian Norris <computersforpeace@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Rob Herring <robh+dt@kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-mtd@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH/RFC 0/7] ARM: dts: Add compatible property to "partitions" node
Date: Mon, 14 Dec 2015 13:43:12 -0800 [thread overview]
Message-ID: <20151214214312.GA86857@google.com> (raw)
In-Reply-To: <CAMuHMdW=wJEoi-+EWAKBjRwb+QFvk=iFur1yFqR=q0f4zwzb2Q@mail.gmail.com>
On Mon, Dec 14, 2015 at 10:20:19PM +0100, Geert Uytterhoeven wrote:
> On Mon, Dec 14, 2015 at 8:46 PM, Brian Norris
> <computersforpeace@gmail.com> wrote:
> > On Mon, Dec 14, 2015 at 08:11:37PM +0100, Geert Uytterhoeven wrote:
> >> As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
> >> property to "partitions" node"), the "partitions" subnode of an SPI
> >> FLASH device node must have a compatible property. The partitions are no
> >> longer detected if it is not present.
> >
> > For all patches:
> >
> > Acked-by: Brian Norris <computersforpeace@gmail.com>
> >
> >> I marked this series as "RFC", as the abovementioned commit is not yet
> >> upstream. Ideally, the users should be fixed first, to avoid breakage.
>
> It breaks bisectability in mainline.
The files you are fixing are not converted in mainline yet, are they?
> > I'd differ on the last sentence. It's more important to straighten out
> > the release features for 4.4 than to make sure that linux-next has
> > perfect DTS files. So I'll submit whenever ready :)
>
> If the DTS changes go in first, bisectability is preserved.
Are you asking me to delay fixing the DT binding until 4.5, just because
your for-next branches can't be fixed? IOW, you want me to release the
bad DT binding for a whole cycle?
Brian
next prev parent reply other threads:[~2015-12-14 21:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 19:11 [PATCH/RFC 0/7] ARM: dts: Add compatible property to "partitions" node Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` [PATCH/RFC 1/7] ARM: dt: mvebu: ix4-300d: " Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` [PATCH/RFC 2/7] ARM: shmobile: bockw dts: " Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` [PATCH/RFC 3/7] ARM: shmobile: lager " Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` [PATCH/RFC 4/7] ARM: shmobile: koelsch " Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` [PATCH/RFC 5/7] ARM: shmobile: porter " Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` [PATCH/RFC 6/7] ARM: shmobile: gose " Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` [PATCH/RFC 7/7] ARM: shmobile: silk " Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:11 ` Geert Uytterhoeven
2015-12-14 19:46 ` [PATCH/RFC 0/7] ARM: " Brian Norris
2015-12-14 19:46 ` Brian Norris
2015-12-14 19:46 ` Brian Norris
2015-12-14 21:20 ` Geert Uytterhoeven
2015-12-14 21:20 ` Geert Uytterhoeven
2015-12-14 21:20 ` Geert Uytterhoeven
2015-12-14 21:43 ` Brian Norris [this message]
2015-12-14 21:43 ` Brian Norris
2015-12-14 21:43 ` Brian Norris
2015-12-14 21:45 ` Brian Norris
2015-12-14 21:45 ` Brian Norris
2015-12-14 21:45 ` Brian Norris
2015-12-15 8:01 ` Geert Uytterhoeven
2015-12-15 8:01 ` Geert Uytterhoeven
2015-12-15 8:01 ` Geert Uytterhoeven
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=20151214214312.GA86857@google.com \
--to=computersforpeace@gmail.com \
--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 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.