From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
ssantosh@kernel.org
Subject: Re: [PATCH 0/2] ARM: dts: amx3xx: add emif interrupt info
Date: Thu, 1 Mar 2018 10:22:51 -0800 [thread overview]
Message-ID: <20180301182251.GH62820@atomide.com> (raw)
In-Reply-To: <1519657500-15490-1-git-send-email-t-kristo@ti.com>
* Tero Kristo <t-kristo@ti.com> [180226 07:06]:
> Hi,
>
> Adding these two patches per the addition of required interrupt property
> under emif node.
>
> See: https://patchwork.kernel.org/patch/10217053/
Applying both into omap-for-v4.17/dt thanks.
Tony
next prev parent reply other threads:[~2018-03-01 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 15:04 [PATCH 0/2] ARM: dts: amx3xx: add emif interrupt info Tero Kristo
2018-02-26 15:04 ` [PATCH 1/2] ARM: dts: am33xx: " Tero Kristo
2018-02-26 15:05 ` [PATCH 2/2] ARM: dts: am43xx: " Tero Kristo
2018-03-01 18:22 ` Tony Lindgren [this message]
2018-03-06 0:08 ` [PATCH 0/2] ARM: dts: amx3xx: " santosh.shilimkar
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=20180301182251.GH62820@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@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).