devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: "Vokáč Michal" <Michal.Vokac@ysoft.com>,
	"Fabio Estevam" <fabio.estevam@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Andrew Lunn" <andrew@lunn.ch>
Subject: Re: [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards
Date: Thu, 10 Jan 2019 21:57:44 +0800	[thread overview]
Message-ID: <20190110135742.GC30487@dragon> (raw)
In-Reply-To: <CAL_JsqLRX2g1t-8YCqpZ5fd=-MyLPkgy88Gb=6ohEZbxWfS+LA@mail.gmail.com>

On Tue, Jan 08, 2019 at 12:11:50PM -0600, Rob Herring wrote:
> Humm, I thought Shawn had applied to his tree as there were some conflicts.
> 
> Shawn, do you need me to resend?

Sorry.  I was actually dropping the conflicting changes from my tree and
expecting you send the json-schema patch via your tree.  I just applied
your patch to my tree.

@Vokáč,

Please generate your patches against my for-next branch with dt-bindings
being separate patch from dts one.

Shawn

  reply	other threads:[~2019-01-10 13:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 14:42 [PATCH v2] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards Vokáč Michal
2018-12-28 18:20 ` Fabio Estevam
2019-01-08 11:40   ` Vokáč Michal
2018-12-28 23:25 ` Rob Herring
2019-01-08 11:43   ` Vokáč Michal
2019-01-08 14:25     ` Vokáč Michal
2019-01-08 14:53       ` Rob Herring
2019-01-08 14:56     ` Rob Herring
2019-01-08 15:00       ` Vokáč Michal
2019-01-08 16:09         ` Vokáč Michal
2019-01-08 18:11           ` Rob Herring
2019-01-10 13:57             ` Shawn Guo [this message]
2019-01-10 14:06               ` Vokáč Michal

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=20190110135742.GC30487@dragon \
    --to=shawnguo@kernel.org \
    --cc=Michal.Vokac@ysoft.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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 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).