linux-kernel - Re: [PATCH v2] ata: add AMD Seattle platform driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160318201937.GG20028@mtj.duckdns.org>
Date:	Fri, 18 Mar 2016 16:19:37 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Brijesh Singh <brijesh.singh@....com>
Cc:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	hdegoede@...hat.com, linux-ide@...r.kernel.org,
	Graeme Gregory <graeme@...a.org.uk>
Subject: Re: [PATCH v2] ata: add AMD Seattle platform driver

Hello,

On Fri, Mar 18, 2016 at 01:36:40PM -0500, Brijesh Singh wrote:
> > It's your call in the end. My main objection is to the fact that
> > I have suggested a clean implementation for the normal DT based
> > path that also fixes existing platforms that used to work in the
> > past and were broken by the (long-ago) move from drivers/ide to
> > drivers/ata, Brijesh has not implemented that but has instead
> > continued pushing the hack for the ACPI mode that is still
> > experimental on ARM64.
> 
> I am helping a customer who want EM support in a distro (using ACPI
> mode). Since its difficult to update the bios hence can I request to
> pull this driver. The driver solves the ACPI usecases.
>
> As per DT is concerned, will look into driver/ide and led framework
> but since I am not very familiar with driver/ide and led framework
> hence it will take sometime to design and implement the DT cases.

Alright, will route it through for-4.6-fixes after the merge window
but please do look into the issue that Arnd raised.

Thanks.

-- 
tejun