From: Matthias Brugger <matthias.bgg@gmail.com>
To: Tejun Heo <tj@kernel.org>, Ryder Lee <ryder.lee@mediatek.com>
Cc: devicetree@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org,
Long Cheng <long.cheng@mediatek.com>
Subject: Re: [PATCH v3 1/2] ata: mediatek: add support for MediaTek SATA controller
Date: Mon, 14 Aug 2017 13:41:13 +0200 [thread overview]
Message-ID: <b02142f2-c4be-73b2-3165-288ac10b0db3@gmail.com> (raw)
In-Reply-To: <20170813183854.GA1438922@devbig577.frc2.facebook.com>
On 08/13/2017 08:38 PM, Tejun Heo wrote:
> On Sat, Aug 12, 2017 at 09:31:03AM +0800, Ryder Lee wrote:
>> This adds support the AHCI-compliant Serial ATA controller present
>> on MediaTek SoCs.
>>
>> Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
>
> Looks good to me.
>
> Acked-by: Tejun Heo <tj@kernel.org>
>
> If others are okay with it, please let me know how the patches should
> be routed. I can push both through libata, both can be routed through
> dt tree, or we can handle them separately.
>
Please take the device tree bindings through your tree as well.
You might want to wait for a Ack from a device tree maintainer though.
Thanks,
Matthias
next prev parent reply other threads:[~2017-08-14 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 1:31 [PATCH v3 0/2] Add support for MediaTek AHCI SATA Ryder Lee
[not found] ` <cover.1502501342.git.ryder.lee-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-08-12 1:31 ` [PATCH v3 1/2] ata: mediatek: add support for MediaTek SATA controller Ryder Lee
2017-08-13 18:38 ` Tejun Heo
2017-08-14 11:41 ` Matthias Brugger [this message]
2017-08-12 1:31 ` [PATCH v3 2/2] dt-bindings: ata: add DT bindings " Ryder Lee
2017-08-17 20:29 ` Rob Herring
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=b02142f2-c4be-73b2-3165-288ac10b0db3@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=long.cheng@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).