All of lore.kernel.org
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: arm64: dts: Add expansion bus to VExpress and Juno
Date: Thu, 14 Apr 2016 14:07:52 +0100	[thread overview]
Message-ID: <570F9628.70106@arm.com> (raw)
In-Reply-To: <1460627546-24230-1-git-send-email-brian.starkey@arm.com>



On 14/04/16 10:52, Brian Starkey wrote:
> The VExpress and Juno development platforms have an external expansion
> bus which can be used for additional hardware (e.g. LogicTile Express
> daughterboards).
> Add this bus to all VExpress CoreTile and Juno device-trees.
>

Sorry for missing it earlier, ARM-SoC guys like to keep arm{32,64}
changes separate. So please move Juno DT changes to separate patch.

-- 
Regards,
Sudeep

WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: Brian Starkey <brian.starkey-5wv7dgnIgG8@public.gmane.org>
Cc: Liviu Dudau <liviu.dudau-5wv7dgnIgG8@public.gmane.org>,
	Lorenzo Pieralisi
	<lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>,
	Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] ARM: arm64: dts: Add expansion bus to VExpress and Juno
Date: Thu, 14 Apr 2016 14:07:52 +0100	[thread overview]
Message-ID: <570F9628.70106@arm.com> (raw)
In-Reply-To: <1460627546-24230-1-git-send-email-brian.starkey-5wv7dgnIgG8@public.gmane.org>



On 14/04/16 10:52, Brian Starkey wrote:
> The VExpress and Juno development platforms have an external expansion
> bus which can be used for additional hardware (e.g. LogicTile Express
> daughterboards).
> Add this bus to all VExpress CoreTile and Juno device-trees.
>

Sorry for missing it earlier, ARM-SoC guys like to keep arm{32,64}
changes separate. So please move Juno DT changes to separate patch.

-- 
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: Brian Starkey <brian.starkey@arm.com>
Cc: Liviu Dudau <liviu.dudau@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: arm64: dts: Add expansion bus to VExpress and Juno
Date: Thu, 14 Apr 2016 14:07:52 +0100	[thread overview]
Message-ID: <570F9628.70106@arm.com> (raw)
In-Reply-To: <1460627546-24230-1-git-send-email-brian.starkey@arm.com>



On 14/04/16 10:52, Brian Starkey wrote:
> The VExpress and Juno development platforms have an external expansion
> bus which can be used for additional hardware (e.g. LogicTile Express
> daughterboards).
> Add this bus to all VExpress CoreTile and Juno device-trees.
>

Sorry for missing it earlier, ARM-SoC guys like to keep arm{32,64}
changes separate. So please move Juno DT changes to separate patch.

-- 
Regards,
Sudeep

  reply	other threads:[~2016-04-14 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  9:52 [PATCH v2] ARM: arm64: dts: Add expansion bus to VExpress and Juno Brian Starkey
2016-04-14  9:52 ` Brian Starkey
2016-04-14  9:52 ` Brian Starkey
2016-04-14 13:07 ` Sudeep Holla [this message]
2016-04-14 13:07   ` Sudeep Holla
2016-04-14 13:07   ` Sudeep Holla

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=570F9628.70106@arm.com \
    --to=sudeep.holla@arm.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.