From: Tejun Heo <tj@kernel.org>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, hdegoede@redhat.com,
linux-ide@vger.kernel.org, Graeme Gregory <graeme@xora.org.uk>
Subject: Re: [PATCH v2] ata: add AMD Seattle platform driver
Date: Fri, 18 Mar 2016 16:19:37 -0400 [thread overview]
Message-ID: <20160318201937.GG20028@mtj.duckdns.org> (raw)
In-Reply-To: <56EC4AB8.7040901@amd.com>
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
next prev parent reply other threads:[~2016-03-18 20:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 16:31 Brijesh Singh
2016-01-20 21:24 ` Brijesh Singh
2016-01-25 20:43 ` Tejun Heo
2016-01-26 9:36 ` Hans de Goede
2016-03-16 20:12 ` Brijesh Singh
2016-01-26 12:17 ` Arnd Bergmann
2016-01-26 16:56 ` Brijesh Singh
2016-01-29 21:22 ` Arnd Bergmann
2016-01-29 21:31 ` One Thousand Gnomes
2016-02-01 18:56 ` Brijesh Singh
2016-02-01 20:14 ` Arnd Bergmann
2016-02-01 22:15 ` Brijesh Singh
2016-02-02 14:08 ` Arnd Bergmann
2016-02-02 18:37 ` Brijesh Singh
2016-02-05 14:50 ` Arnd Bergmann
2016-02-05 17:23 ` Brijesh Singh
2016-02-08 18:12 ` Brijesh Singh
2016-03-16 21:07 ` Tejun Heo
2016-03-17 17:36 ` Arnd Bergmann
2016-03-18 18:36 ` Brijesh Singh
2016-03-18 20:19 ` Tejun Heo [this message]
2016-04-14 9:08 ` Matthias Brugger
2016-04-14 22:14 ` Brijesh Singh
2016-04-13 19:15 ` Tejun Heo
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=20160318201937.GG20028@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=arnd@arndb.de \
--cc=brijesh.singh@amd.com \
--cc=graeme@xora.org.uk \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome