[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <544E56DB.7020305@amd.com>
Date: Mon, 27 Oct 2014 09:29:47 -0500
From: Suravee Suthikulanit <suravee.suthikulpanit@....com>
To: Alexander Graf <agraf@...e.de>,
Andreas Färber <afaerber@...e.de>
CC: "mark.rutland@....com" <mark.rutland@....com>,
Thomas Lendacky <Thomas.Lendacky@....com>,
Joel Schopp <Joel.Schopp@....com>,
"marc.zyngier@....com" <marc.zyngier@....com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"liviu.dudau@....com" <liviu.dudau@....com>,
"<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>,
"will.deacon@....com" <will.deacon@....com>,
Rob Herring <robh+dt@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: amd-seattle: Adding device tree for AMD Seattle
platform
On 10/26/2014 9:08 AM, Alexander Graf wrote:
>>> This option doesn't exist in upstream kernels, does it? Why not just
>>> >>make it dtb-y?
>> >
>> >CONFIG_ARCH_SEATTLE is being added one hunk above.:)
> Oops:).
>
> I'm not convinced we need a config option just for the sake of compiling a device tree though.
>
>
> Alex
>
Eventually, we would add other device driver selections when
CONFIG_ARCH_SEATTLE=y. At this point, those drivers are still not ready.
Suravee
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists