From: Andrew Lunn <andrew@lunn.ch>
To: Kostya Porotchkin <kostap@marvell.com>
Cc: "tmn505@gmail.com" <tmn505@gmail.com>,
"jaz@semihalf.com" <jaz@semihalf.com>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
Nadav Haklai <nadavh@marvell.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Stefan Chulski <stefanc@marvell.com>,
"mw@semihalf.com" <mw@semihalf.com>,
Ben Peled <bpeled@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"sebastian.hesselbarth@gmail.com"
<sebastian.hesselbarth@gmail.com>
Subject: Re: [EXT] Re: [PATCH v2 3/4] arm64: dts: cn913x: add device trees for topology B boards
Date: Mon, 21 Dec 2020 14:58:06 +0100 [thread overview]
Message-ID: <20201221135806.GD3107610@lunn.ch> (raw)
In-Reply-To: <DM5PR18MB1452A62565467523075A9F6FCAC00@DM5PR18MB1452.namprd18.prod.outlook.com>
On Mon, Dec 21, 2020 at 06:57:46AM +0000, Kostya Porotchkin wrote:
>
>
> > -----Original Message-----
> > From: Andrew Lunn <andrew@lunn.ch>
> > Sent: Sunday, December 20, 2020 18:35
> > To: Kostya Porotchkin <kostap@marvell.com>
> > Cc: linux-arm-kernel@lists.infradead.org; tmn505@gmail.com;
> > jaz@semihalf.com; gregory.clement@bootlin.com; Nadav Haklai
> > <nadavh@marvell.com>; robh+dt@kernel.org; Stefan Chulski
> > <stefanc@marvell.com>; mw@semihalf.com; Ben Peled
> > <bpeled@marvell.com>; sebastian.hesselbarth@gmail.com
> > Subject: Re: [EXT] Re: [PATCH v2 3/4] arm64: dts: cn913x: add device trees for
> > topology B boards
> >
> > > 1) make the DTS naming match the current SDK code
> >
> > Where do i found the SDK?
> [KP] Unfortunately the last Github published release is 2 years old.
> The new SDK is available only after registration (and accepting the NDA terms) on marvell.com site.
Which leads to the question, why should the mainline kernel be changed
to be compatible with a closed source SDK?
What mainline should not do is break compatibility with
mainline. Which is why i think the existing DTB file needs to keep its
name, and B gets a new file name.
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-21 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 7:55 [PATCH v2 0/4] DTS updates for Marvell Armada CN913x platforms kostap
2020-12-17 7:55 ` [PATCH v2 1/4] Documentation/bindings: phy: update references to cp11x kostap
2020-12-17 7:55 ` [PATCH v2 2/4] arch/arm64/boot/dts/marvell: fix NAND partitioning scheme kostap
2020-12-17 15:36 ` Andrew Lunn
2020-12-17 7:55 ` [PATCH v2 3/4] arm64: dts: cn913x: add device trees for topology B boards kostap
2020-12-17 15:41 ` Andrew Lunn
2020-12-20 7:32 ` [EXT] " Kostya Porotchkin
2020-12-20 16:34 ` Andrew Lunn
2020-12-21 6:57 ` Kostya Porotchkin
2020-12-21 13:58 ` Andrew Lunn [this message]
2020-12-21 15:55 ` Kostya Porotchkin
2020-12-17 7:55 ` [PATCH v2 4/4] arm64: dts: add support for Marvell cn9130-crb platform kostap
2020-12-17 15:43 ` Andrew Lunn
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=20201221135806.GD3107610@lunn.ch \
--to=andrew@lunn.ch \
--cc=bpeled@marvell.com \
--cc=gregory.clement@bootlin.com \
--cc=jaz@semihalf.com \
--cc=kostap@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stefanc@marvell.com \
--cc=tmn505@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;
as well as URLs for NNTP newsgroup(s).