All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felix Brack <fb@ltec.ch>
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	bcousson@baylibre.com, mpfj@newflow.co.uk, mark.rutland@arm.com,
	robh+dt@kernel.org, linux@armlinux.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: am33xx: Remove unnecessary properties
Date: Fri, 14 Dec 2018 07:18:25 -0800	[thread overview]
Message-ID: <20181214151825.GU6707@atomide.com> (raw)
In-Reply-To: <89710fa1-38a9-1628-0651-003332780483@ltec.ch>

* Felix Brack <fb@ltec.ch> [181214 15:12]:
> Hi Tony,
> 
> On 11.12.2018 17:43, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [181211 16:36]:
> >> * Felix Brack <fb@ltec.ch> [181210 05:25]:
> >>> Remove the unnecessary properties #address-cells and #size-cells
> >>> of node pinmux as there are no child-nodes with property reg.
> >>
> >> Applying into omap-for-v4.21/dt thanks.
> > 
> > Actually this currently conflicts with the pending
> > am33xx l4 ti-sysc changes, so let's wait on this
> > one to avoid causing merge conflicts between
> > branches.
> >
> Okay, I see. The changes introduced by my patch would then affect the
> new file am33xx-l4.dtsi instead of am33xx.dtsi

Yup, and I wanted to keep the am33xx-l4.dtsi in a separate
branch from the rest of the dts changes.

> > So dropping for now.
> >
> Will you "apply" my patch once the am33xx l4 ti-sysc changes are applied
> or do you expect me to send V2 patch (to be applied to the new
> am33xx-l4.dtsi) ?

I'd prefer you to send an updated version against
Linux next as the am33xx-l4.dtsi changes have been
in next for a while now. It is unlikely at this point
that they would not get merged, but I'd rather wait
a bit before applying to avoid mixing the two otherwise
independent branches :)

Regards,

Tony

      reply	other threads:[~2018-12-14 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 13:24 [PATCH] ARM: dts: am33xx: Remove unnecessary properties Felix Brack
2018-12-11 16:36 ` Tony Lindgren
2018-12-11 16:43   ` Tony Lindgren
2018-12-14 15:11     ` Felix Brack
2018-12-14 15:18       ` Tony Lindgren [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=20181214151825.GU6707@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fb@ltec.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mpfj@newflow.co.uk \
    --cc=robh+dt@kernel.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.