public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Aryan Srivastava <Aryan.Srivastava@alliedtelesis.co.nz>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
	"sebastian.hesselbarth@gmail.com"
	<sebastian.hesselbarth@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: mvebu: Add device tree for ATL-x530 Board
Date: Tue, 1 Dec 2020 19:22:31 +0100	[thread overview]
Message-ID: <20201201182231.GL2073444@lunn.ch> (raw)
In-Reply-To: <3570cb6d-44e0-3ab5-b464-a013ba1007b1@alliedtelesis.co.nz>

> This is what we've done in our kernel fork. But for upstreaming we 
> wanted to start slow and maybe move things into one or more common .dtsi 
> files if/when needed (in particular there are some models in development 
> now that use different i2c mux and hwmon chips).

O.K. It is not particularly disruptive to refactor later, so lets
start with this.

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2020-12-01 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 22:35 [PATCH v2] ARM: dts: mvebu: Add device tree for ATL-x530 Board Aryan Srivastava
2020-11-30 23:03 ` Andrew Lunn
2020-11-30 23:57   ` Chris Packham
2020-12-01 18:22     ` Andrew Lunn [this message]
2021-04-07 20:40 ` Gregory CLEMENT

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=20201201182231.GL2073444@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Aryan.Srivastava@alliedtelesis.co.nz \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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